1 Reply Latest reply on Apr 28, 2011 1:50 PM by philmodjunk

    Filemaker Pro 11.02 General Protection error on database login

    GaryWilson

      Summary

      Filemaker Pro 11.02 General Protection error on database login

      Product

      FileMaker Pro

      Version

      11.02

      Operating system version

      Windows XP SP3

      Description of the issue

      After installing Filemaker Pro version 11

      When entering username and password details for Filemaker Pro 11.02, the general protection error message appears prompting to send an error report.

      This problem occurs at random, can take upto 9 attempts before successful login to database

      This problem does not occur with version 8 all other conditions being the same.

      Steps to reproduce the problem

      Login to database with user credentials

      Expected result

      Successful Login to database on server

      Actual result

      Genereal protection error message on login

      Exact text of any error message(s) that appear

      General Protection fault send error report

      Configuration information

      Appname Filemakerpro.exe Appver 11.0.2.220 Modname ntdll.dll
      ModVer: 5.1.2600.6055 0004487f

      Workaround

      No work around found, after retrying will eventually login to database. However can take up to 9 attempts before successful login.

      Filemakererror.JPG

        • 1. Re: Filemaker Pro 11.02 General Protection error on database login
          philmodjunk

          To rule out possible problems with your file, you might try running a recover on it to see what is reported and so you can test the reocvered copy and see if it has the same problem.

          To rule out possible problems with your computer, you might try moving this file to a different computer and testing on it.

          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.