Are both the client machine and the host machines windows 8 systems? Is the file being hosted from FileMaker Pro or FileMaker Server? Does it crash on the client, or on the host?
What happens if you create a small brand new est file and host it from the same hoat computer and remotely access it from the same client?
The host is Windows 2003 Server R2 w/SPK 2 running FMServer Standard 11, other clients are Win 7, XP, they all connect fine. I tested opening another DB on the server on the machine in question and it opens fine, with that in mind, i recovered the database and rehosted the recovered version and the windows 8 machine still crashes, the other clients are fine. The fact that no error log or event is written makes it difficult to pinpoint.
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).
Thank you for your posts.
Although FileMaker Pro 11 was never tested with Windows 8 (http://help.filemaker.com/app/answers/detail/a_id/11308), a number of customers are using it successfully, remotely and locally. With that said, the issue may be related to a bad server.pem file. Try copying a server.pem file from one of your working computers to the Windows 8 computer. The server.pem file is located in the FileMaker Pro 11 application folder.
If you can repeat the crash again, install Debugging Tools for Windows and open Filemaker exe in it. Here is installation guide.http://www.sysads.co.uk/2012/05/installing-and-configuring-windbg-windows-debug-tools%E2%80%8F/
Firstly, open Windbg and go to File>Open executable ... search for Filemaker Pro Advanced.exe or Filemaker Pro.exe in your C:/Program files/Filemaker. Then you have to press F5 (Debug>Go) in Windbg until Debug>Go item is disabled. After that you can do actions in Filemaker and when the error occurs, switch to Windbg again (not closing filemaker) and look what errors are logged in window...
I tried the server.pem file, did not work.
Try sharing a file on your computer, and then have other users access the file. Does this work?
Assuming users can see your file and access it, is there anything else on your machine that may seem out of the ordinary? Have you tried reinstalling FileMaker Pro? Any other information you can provide may be helpful.
The option from "Tomas Dohnal" is excellent.