1 Reply Latest reply on Mar 29, 2011 3:30 PM by philmodjunk

    Error Signature FileMaker Pro.exe

    SamuelMartinez

      Title

      Error Signature FileMaker Pro.exe

      Post

      User get this from their clients. Updates and reinstalls or uninstalls are not successful.  Users running Windows XP Pro SP3  FileMaker Pro V10.0.3.  See below massage. Attached is the full message dialog box.  NOt sure if this is a database issue. Works sometimes but mostly doesn't.You have to retry several time to access DB.  Possible security update?  Please advise anyone.

      FileMaker Pro.exe has encountered a problem and needs to close. We are sorry for the inconvenience.

       ModVer: 8.0.50727.4053 Offset: 00008aa0

      Error Signature: AppName: filemaker pro.exe AppVer: 10.0.3.303 ModName: msvcr80.dll

      FileMaker_Pro_Error.jpg

        • 1. Re: Error Signature FileMaker Pro.exe
          philmodjunk

          No way for me to tell from that screen shot. I can tell you that we are using 10.03 on numerous fully updated XP computers here on a daily basis without trouble. This screenshot might tell a FileMaker tech something, but there are some tests you can run to try to figure this out while you wait for a response.

          Is the file hosted from another computer? If so does that computer host it with FileMaker or FileMaker Server?

          Do you get this crash only from a specific file? If you don't know, create a small file put it on the same computer and test it to see if you get the same problem. If the test file opens without issue, then your file may be damaged. Run a recover on the file.

          1. Take it down off the server if you are hosting with FileMaker server (you can use a back up copy for this instead of taking it down off the server).
          2. Launch FileMaker without opening the file and select recover from the file menu.

           

          Things to keep in mind about Recover:

          1. Recover does not detect all problems
          2. Recover doesn't always fix all problems correctly
          3. 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.