Database Shared by Web Companion "Not Open"

September 28, 200322 yr

Hi Everyone,

I am using FileMaker Pro 5.0v3 on a W2K server to share 8 databases that web forms plug in to. Seven of the eight work great, but one of these databases does not work well. After being open for about a day or so, someone will go to the form online and will get the following message:

Database Not Open:

Unable to process your request because the database "staffapplication.fp5" is not open.

The problem here is that the database is open. When I go to the server it is up and runs fine. I either have to close the database and reopen it, or close the entire application and reopen all eight databases, and then the web form will work fine again - for awhile.

Of the eight databases, this one is by far the largest. It has about 150 fields. However, there are generally never more than a couple records at a time.

Does anyone have any tips toward troubleshooting this? If this could be at all helpful, here is the form I am hosting, which I hope will not give you the error:

http://fm.chipinaw.com:591/Chipinaw/FMPro?-db=StaffApplication.fp5&-format=StaffApplication.htm&-view

Many thanks,

Chris

September 28, 200322 yr

Have you bothered to search these forums for Database Not Open or Not Open?

Your question has a history on the Internet Forums.

September 28, 200322 yr

Also make sure you have the latest updaters from FMI.

September 29, 200322 yr

Hi, Chris! Well, I just tried it Sunday 9/29/2003 at 4:54pm PST and it told me it wasn't open. I tried testing to see if it was serving webpages straight up but bumped into a JS validator. For a slit second I saw a teddy bear and something about a Welcome Staff message or somthing on a purple screen but gave up after 20 seconds of trying. I also ended up at the FMP default Web Read Me page somehow.

You seem to be intercepting/redirecting pages.. could that be causing a problem? What if you try leaving records in there? Change a status flag or something if you need to separate what's been processed and what hasn't, but try to narrow things down. Are you using the Web Security Database? Are you using passwords? Ask yourself some of these things and try to eliminate some things if you can unti you can figure out what's wrong.

Good luck! --ST