IWP unknown error 13

[JudyJack]

I have databases hosted with FileMaker Server Advanced (8). I have several databases turned on for IWP. All has been running well until about a month ago. My campus secretaries are able enter their user names and passwords, and see the databases, but when they click on this one particular database, they receive and "unknown error number 13". Their option is to click "Okay" and then the following message comes up: "Bad Request. The server could not process your request because your session has timed out, been closed, or communication with the server has been lost." My technology department has not been able to help me, and the FileMaker technical assistants have not been able to help me either (they suspected a corrupt database and had me reconstruct it to no avail). Any advice on what to check or where to start would be greatly appreciated.

[Steven H. Blackwell]

Check to see how many IWP sessions are allowed by Server. generally, Error 13 refers to a file's being in use. But it might be that the quota for IWP connections has been exceeded.

Also, check at the OS level to be sure the file isn't read only.

Steven

[JudyJack]

Is there a different place for IWP sessions or is it the same as the Web Publishing Engine sessions? Thank you for your help, and sorry for my ignorance.

[Steven H. Blackwell]

Is there a different place for IWP sessions or is it the same as the Web Publishing Engine sessions? Thank you for your help, and sorry for my ignorance.

Yes, they are the same. It's the WPE sessions settings where this is controlled.

No need for an apology. Ignorance is easily overcome by learning. That's why these Forums exist.

Steven

[JudyJack]

thank you for your help. My sessions were sitting much higher than I needed, so that was not the issues. However, since I posted this question, I found that the publishing engine was 8.0.1.27 and there was an upgrade of 8.0.4.36, so I upgraded and have gone almost 24 hours without the error - hopefully the issue is resolved. My server was 8.0v4 so maybe there was some issue between the two. Thanks again for talking to me.

[bdiehl]

I'm having the same exact problem. Did upgrading to 8.0.4.36 fix it?

Thanks,