Jump to content
Salesforce and other SMB Solutions are coming soon. ×

HELP!


patso23

Recommended Posts

Hi,

 

I have only been working with filemaker for about 9 months, but I have a pretty good idea of what I'm doing. So here's my problem. My office runs FileMaker server ver 5.5 on a mac running 10.2.6. And most everyone in the office accesses it using Filemaker pro5 for os9.

 

Earlier today, everyone got kicked off the server only in regard to one file (ie. "All orgs"). I went to the server to check the log and this is the error message for when it kicked everyone off the file:

 

May 10 13:05:57 Harold INFO: File "All orgs" read error on block 5445. (-39)

May 10 13:05:57 Harold INFO: User "Maude" [] forced to close connection.

May 10 13:05:57 Harold INFO: User "Elsa" [] forced to close connection.

May 10 13:05:57 Harold INFO: User "Thom" [] forced to close connection.

May 10 13:05:57 Harold INFO: Closing file "All orgs" due to serious error. (10198)

 

 

So after seeing this I went to use the recover function of filemaker and saved the "All orgs Recovered." When I backed up and then replaced the error-laden file with the supposed recovered file...I still receive an error when launching my filemaker startup script. Something like "All Orgs can not be found and is required to complete function" or something similar. Also, after the error it prompts me to find the file manually, which I did....and the file opens fine! What is going on here?

 

Has anyone ever had a similar experience? Does anyone know what I need to do to get this back? This is part of a very mission critical relational database that I need up and running as soon as possible. Any help anyone gives would be GREATLY appreciated.

 

Patrick

Link to comment
Share on other sites

take a look at the file ref in the startup script, you probably have to point it at the recovered file, the script still looks at the old one.

 

kjoe

Link to comment
Share on other sites

I admit it's poke around and see what happens, but nevertheless, i'd open up the startup script.

 

otherwise, you can try deleting the prefs file for server 5.5 (park it in a safe place and test before deleting) and / or restarting server 5.5 or the entire host machine.

 

kjoe

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.



×
×
  • Create New...

Important Information

Terms of Use