AnsweredAssumed Answered

IWP pages crash

Question asked by KarthikKannan on Sep 29, 2014
Latest reply on Sep 30, 2014 by philmodjunk

Like • Show 0 Likes0
Comment • 1

Title

IWP pages crash

Post

Hi Everyone,

I am a FileMaker developer for around 4+ years. I have encountered an issue now.

The issue is we have developed a FM database and shared the layouts via IWP. When the users access via IWP there is a crash happening in the Web server and stops/restarts the web publishing engine. We have hosted this DB in FileMaker shared hosting only. Now the Hosting company has stopped our IWP access as it affects the other users web access also.

I have checked my FM database and layouts.

Please find attached error logs from the hosting.

Can anyone please help me to sort this issue?

Thanks in advance

philmodjunk Sep 30, 2014 10:07 AM

Correct Answer

Any time you get a crash, file damage is something to check on. File damage (corruption) can cause crashes and crashes can corrupt a file.

Take a recent back up copy of the file and run a recover on it to see what recover reports.

Things to keep in mind about Recover:

While Recover almost always detects and fully corrects any problems with your file...

The recovered copy may behave differently even if recover reports "no problems found".
Recover does not detect all problems
Recover doesn't always fix all problems correctly
Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.

And here's a knowledgebase article that you may find useful: What to do when your file is corrupt (KB5421).

See the reply in context

No one else had this question

Outcomes

1 Reply

philmodjunk Sep 30, 2014 10:07 AM
Unmark Correct
Correct Answer
Any time you get a crash, file damage is something to check on. File damage (corruption) can cause crashes and crashes can corrupt a file.

Take a recent back up copy of the file and run a recover on it to see what recover reports.

Things to keep in mind about Recover:

While Recover almost always detects and fully corrects any problems with your file...
1. The recovered copy may behave differently even if recover reports "no problems found".
2. Recover does not detect all problems
3. Recover doesn't always fix all problems correctly
4. Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.
And here's a knowledgebase article that you may find useful: What to do when your file is corrupt (KB5421).
Like • Show 0 Likes0
Actions

IWP pages crash

Title

Post

Outcomes

Related Content

Recommended Content