8 Replies Latest reply on Nov 14, 2014 1:11 AM by AviK

    FMPro 13 Crashes on XPAL.dll Error

    Millennium

      Title

      FMPro 13 Crashes on XPAL.dll Error

      Post

           We have FMPro 13 installed on a Windows 8 Pro PC with 8GB of RAM and 800GB free disk.  It is running a looping script which simply imports data every 3 minutes.  With seeming randomness FMPro crashes leaving no signs of having been running (no error message, no recent files listed, etc.).  This can happen after an hour or three days and every time in complete randomness.  This computer does nothing else including all automatic updates and downloads being turned off.  The event log shows the following error information:

           Faulting application name: FileMaker Pro.exe, version: 13.0.3.231, time stamp: 0x53502a0d
           Faulting module name: XPAL.dll, version: 13.0.3.231, time stamp: 0x535028ac
           Exception code: 0xc0000005
           Fault offset: 0x00041c2d
           Faulting process id: 0x450
           Faulting application start time: 0x01cfaa616efe5fa5
           Faulting application path: C:\Program Files (x86)\FileMaker\FileMaker Pro 13\FileMaker Pro.exe
           Faulting module path: C:\Program Files (x86)\FileMaker\FileMaker Pro 13\XPAL.dll
           Report Id: 2c0fb0e5-1721-11e4-be73-00188b3254b1
           Faulting package full name: 
           Faulting package-relative application ID: 

        • 1. Re: FMPro 13 Crashes on XPAL.dll Error
          philmodjunk

               Figuring out why FileMaker is crashing can require some sleuthing to rule out possible issues.

               Basic diagnostic tests to perform when you get frequent crashes or “hangs”:

               Does the crash only occur with a specific file?
               Test by creating a small sample file and see if opening it and working with it also generates a crash. If it crashes too, the problem likely lies with the computer or it's installation of FileMaker. If it does not crash, it becomes more likely that there is a problem with the file.

               To check for possible problems on a specific computer, you may want to run a utility to check out the hard drive and also to check out the user accounts on that computer for possible problems.

               To rule out some other issues with your specific computer on Windows systems,

               Select Run from the start menu and type in:

               msconfig

               Then, under the Services tab, you can stop all non-Microsoft services. If this solves the issue, then you need to look at what services you stopped and see which is one is the culprit.

               What is reported when you recover the file?
               The file could be damaged. Not only can file damage cause crashes, but the crashes (or forced quits after a "hang") can damage your file. You may need to test a recovered copy to see if it works without crashing.

               Things to keep in mind about Recover:

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


               Does it always crash when you are doing the same thing with your file?
               That may point to a specific layout, script, operation that interacts with your Operating system or other applications...
                

          • 2. Re: FMPro 13 Crashes on XPAL.dll Error
            Millennium

                 Anyone else have a more specific idea related to this particular DLL?  The randomness and duration between errors and relative simplicity of the script being run make recreating the error condition almost impossible without expending dozens of hours = not worth it.  However, if someone has seen this error and has a suggestion about what might be the cause, we are interested in your insight.

                 We have removed and reinstalled FMPro on this computer.  Aside from a clean installation of Windows 8 Pro, there is no other software installed on the computer.

            • 3. Re: FMPro 13 Crashes on XPAL.dll Error
              philmodjunk

                   Have you checked your file for damage? Damage to the file can crash your computer and a crash can damage your file.

              • 4. Re: FMPro 13 Crashes on XPAL.dll Error
                Millennium

                     The file is being served and has hundreds of users on it throughout the day without crashes.  The server runs a consistency check every hour.

                • 5. Re: FMPro 13 Crashes on XPAL.dll Error
                  philmodjunk

                       Nevertheless, just to be absolutely sure. Take your most recent back up and run a recover on it. It may uncover an issue not encountered except when this file runs this script and it may be an issue that passes the consistency check.

                  • 6. Re: FMPro 13 Crashes on XPAL.dll Error
                    davidanders

                         It is Filemaker Pro, not server?

                         How do hundreds of people per day access the file, with Filemaker?

                         Where is the data imported from? Is it possible bad data is the cause?

                    • 7. Re: FMPro 13 Crashes on XPAL.dll Error
                      philmodjunk

                           @DavidAnders,

                           It seems pretty clear to me that we have a FileMaker Pro client that is crashing when performing a script in a file hosted by FileMaker Server...

                      • 8. Re: FMPro 13 Crashes on XPAL.dll Error
                        AviK

                        I have also constant crashed of FM Pro advanced 13 on windows 8.1.

                        It seems that the cause is xpal.dll.

                        Can the development team try and figure out why?