9 Replies Latest reply on Nov 24, 2010 2:26 AM by lordhellfire

    Filemaker 10 Crashing on Terminal Server

    chris.demaj

      Summary

      Filemaker 10 Crashing on Terminal Server

      Description of the issue

      Hello People. My First Post. I am having some really werid issues with Filemaker 10 and Terminal Services. I will explain my setup first.  Machines Involved   Windows Server 2008 (Terminal Server) running FilemakerPro 10 Windows Sever 2003 running FilemakerPro Server 10 and stores the Database  Various clients access the Terminal Server from Vista, XP, Linux machines.We usually have around 10 people on Filemaker at any one time, sometimes it creeps up to 11 or 12. I always run Filemaker locally on my machine, not through the Terminal Server. Sometimes at random points in time Filemaker will stop responding and say "Windows has encountered an Error" The only options to this message is to close, or details. Details Below Error Message  Problem signature:  Problem Event Name:    APPCRASH  Application Name:    FileMaker Pro.exe  Application Version:    10.0.1.92  Application Timestamp:    49647518  Fault Module Name:    StackHash_f4b1  Fault Module Version:    6.0.6001.18000  Fault Module Timestamp:    4791a7a6  Exception Code:    c0000374  Exception Offset:    000b015d  OS Version:    6.0.6001.2.1.0.16.7  Locale ID:    3081  Additional Information 1:    f4b1  Additional Information 2:    91357a017353e7c4fb4d95dcc36326e0  Additional Information 3:    7808  Additional Information 4:    f429235a609775a3a38f98dd6276e36bOnce this happens the individual cannot re-open Filemaker. Just comes up with the error message again, with the same options. I noticed the error comes up when on the Filemaker 10 Splash screen is up it stops at "Intializing" at the bottom of it. Whether this has anything to do with it or not I am not sure. I have spoken to someone from FM via email, but they jsut told me Server Platforms are not supported, and suggested maybe uninstalling and reinstalling. I did that AND applied the latest update. Did nothing. Anyone have any suggestions or any ideas WHY it might be happening, it would be greatle appreciated Thanks in Advance, Chris Demaj

        • 1. Re: Filemaker 10 Crashing on Terminal Server
          mrvodka
             Did you patch your FMP/A clients to 10.0v2 ? It specifically addresses this issue.
          • 2. Re: Filemaker 10 Crashing on Terminal Server
            chris.demaj
              

            Hi,

             

            As soon as the patch came out I applied it...

             

            Should I completley uninstall and reinstall, then patch again?

             

            FM10

            • 3. Re: Filemaker 10 Crashing on Terminal Server
              chris.demaj
                

              Hello People,

               

              Sorry to have to bump my own thread, but I am really desperate for some kind of reason for why this happening.

               

              I am getting phone calls 24/7 from people in our company to fix their Filemaker, I don't even know how to fix this, the best I can do is log off the TS for a period of time then log in again. Soemtimes it fixes it.

               

              Anyone have any suggestions?

               

              Mega Thanks in Advance

              • 4. Re: Filemaker 10 Crashing on Terminal Server
                chris.demaj
                  

                Hi Guys,

                 

                I hate bumping my own stuff, but this is getting beyond a joke. No one can seem to help me, and I just want at least a reason why it may be happening. 

                 

                Here are some extracts from the event viewer of just before posting this.

                 

                Level Date and Time Source Event ID Task Category General Error 9/06/2009 11:02 Application Error 1000 -100 Faulting application FileMaker Pro.exe, version 10.0.2.201, time stamp 0x49e4d60e, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x8b002464, process id 0x1f24, application start time 0x01c9e89dea71dd10.

                 

                Error 9/06/2009 11:02 Application Error 1000 -100 Faulting application FileMaker Pro.exe, version 10.0.2.201, time stamp 0x49e4d60e, faulting module MFC80U.DLL, version 8.0.50727.762, time stamp 0x45713438, exception code 0xc0000005, fault offset 0x0002f739, process id 0x2c14, application start time 0x01c9e89de8d40b90.

                 

                Error 9/06/2009 11:01 Application Error 1000 -100 Faulting application FileMaker Pro.exe, version 10.0.2.201, time stamp 0x49e4d60e, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x8b002464, process id 0x3b98, application start time 0x01c9e89dd32beab0.

                 

                Error 9/06/2009 10:59 Application Error 1000 -100 Faulting application FileMaker Pro.exe, version 10.0.2.201, time stamp 0x49e4d60e, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x8b002464, process id 0x3920, application start time 0x01c9e89d8dd02df0.

                 

                Error 9/06/2009 10:12 Application Error 1000 -100 Faulting application FileMaker Pro.exe, version 10.0.2.201, time stamp 0x49e4d60e, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x8b002464, process id 0x2630, application start time 0x01c9e896ebabc0d0.

                 

                Error 9/06/2009 10:02 Application Error 1000 -100 Faulting application FileMaker Pro.exe, version 10.0.2.201, time stamp 0x49e4d60e, faulting module MFC80U.DLL, version 8.0.50727.762, time stamp 0x45713438, exception code 0xc0000005, fault offset 0x0002f742, process id 0x3ef0, application start time 0x01c9e89589d24600.

                 

                Error 9/06/2009 9:50 Application Error 1000 -100 Faulting application FileMaker Pro.exe, version 10.0.2.201, time stamp 0x49e4d60e, faulting module MFC80U.DLL, version 8.0.50727.762, time stamp 0x45713438, exception code 0xc0000005, fault offset 0x0002f742, process id 0x38bc, application start time 0x01c9e893da75f590.

                 

                Error 9/06/2009 9:36 Application Error 1000 -100 Faulting application FileMaker Pro.exe, version 10.0.2.201, time stamp 0x49e4d60e, faulting module MFC80U.DLL, version 8.0.50727.762, time stamp 0x45713438, exception code 0xc0000005, fault offset 0x00025aee, process id 0xc10, application start time 0x01c9e891a55b3610.

                 

                Error 9/06/2009 9:34 Application Error 1000 -100 Faulting application FileMaker Pro.exe, version 10.0.2.201, time stamp 0x49e4d60e, faulting module DBEngine.dll, version 10.0.2.561, time stamp 0x49e4d282, exception code 0xc0000005, fault offset 0x0002cd65, process id 0x1920, application start time 0x01c9e541d7959830.

                 

                Error 9/06/2009 9:26 Application Error 1000 -100 Faulting application FileMaker Pro.exe, version 10.0.2.201, time stamp 0x49e4d60e, faulting module DBEngine.dll, version 10.0.2.561, time stamp 0x49e4d282, exception code 0xc0000005, fault offset 0x001a3dfb, process id 0x3378, application start time 0x01c9e89001849d0a.

                 

                Error 9/06/2009 9:21 Application Error 1000 -100 Faulting application FileMaker Pro.exe, version 10.0.2.201, time stamp 0x49e4d60e, faulting module MFC80U.DLL, version 8.0.50727.762, time stamp 0x45713438, exception code 0xc0000005, fault offset 0x0002f739, process id 0x322c, application start time 0x01c9e88fe4c8f62a.

                 

                Error 9/06/2009 9:18 Application Error 1000 -100 Faulting application FileMaker Pro.exe, version 10.0.2.201, time stamp 0x49e4d60e, faulting module DBEngine.dll, version 10.0.2.561, time stamp 0x49e4d282, exception code 0xc0000005, fault offset 0x001a3dfb, process id 0x2be0, application start time 0x01c9e88c49c3ee8a.

                 

                Any help, anything would be greatly appreciated.

                • 5. Re: Filemaker 10 Crashing on Terminal Server
                  TSGal

                  chris.demaj:

                   

                  Thank you for your post, and I apologize for the late reply.

                   

                  I do not have access to a Terminal Server, so I cannot test this.

                   

                  When FileMaker Pro crashes on Terminal Server, does FileMaker Server continue to run?

                   

                  When one person crashes under Terminal Server, does everyone else crash?

                   

                  For everyone that uses a local copy of FileMaker Pro, do they have any difficulty connecting via Open Remote directly to the Server?

                   

                  If we remove Terminal Server from the equation, are there any problems?

                   

                  TSGal

                  FileMaker, Inc. 

                  • 6. Re: Filemaker 10 Crashing on Terminal Server
                    chris.demaj
                      

                    Hi,

                     

                    Thanks for Replying. I really appreciate it.

                     

                    Sorry for my late reply.

                     

                    Well we have numerous profiles on the TS, it is only isolated in that profile when it crashes. It will not  affect anyone else or FM Server

                     

                    I use FMPro Advanced locally via Open Remote and works fine.

                     

                    Having said that, the TS is local to the FM Server, and it connects the same way.

                     

                    Unfortunately it is not an option to remove the TS.

                     

                    Thanks for your help.

                     

                    Regards,

                     

                    Chris

                    • 7. Re: Filemaker 10 Crashing on Terminal Server
                      TSGal

                      chris.demaj:

                       

                      Sorry.  I wasn't trying to imply to permanently remove Terminal Services.  These were questions I needed to ask so I could help narrow the possible causes.

                       

                      When FileMaker Pro launches, the splash screen displays a number of messages, with the last one being "Initializing...".  At this point, it is checking memory and some defaults.  In your case, since this happens after a crash, FileMaker is having trouble loading again, and one possible cause is memory allocation on the local machine, because it isn't affecting any other user.  However, you mentioned that sometimes it fixes itself after some time, and this could be due to FileMaker Server disconnecting the client because the client has been idle for a specified time and releases that handle.  This occurs whether connected to FileMaker Server locally or through Terminal Services.  If you reboot the local machine after a crash, launch Terminal Services and FileMaker Pro, are you then able to connect to a file hosted on FileMaker Server?

                       

                      Do you know what the clients were doing just prior to the crash? 

                       

                      Unfortunately, I still don't know what is causing the crash. 

                       

                      TSGal

                      FileMaker, Inc. 

                      • 8. Re: Filemaker 10 Crashing on Terminal Server
                        lordhellfire
                          

                        Hi

                         

                        I'm pretty interested in this issue, as I'm currently installing a Terminal Server 2008 myself where several key personnel will run FileMaker clients on the TS.

                         

                        I was anticipating problems, as FileMaker is not specifically designed to run in a TS environment.

                         

                        My approach to attempt to reduce problems is to make a copy of the installed program folder for each user, so they don't share the same files when the program is running.

                         

                        I have no idea if it will reduce problems or create them. I have not tested it yet, but hope it will work :)

                         

                        Let me know if this helps you. I'll let you know how I fare, as the installation of the server progresses.

                         

                        -Peter

                        • 9. Re: Filemaker 10 Crashing on Terminal Server
                          lordhellfire

                          Hi Chris

                          It's been a little over a year now, so I assume you got your problem fixed. Just wanted to know what the solution was, so other people who might experience the same issue, can find the solution posted here ;)

                          I've been running with the Terminal Server setup for years now without any critical problems, but as I described, my users run their own copy of the entire FileMaker Pro (advanced) 10 folder to avoid any issues with program files being shared between users. Each user also has their own serial number applied in the registry, so no serial sharing either.

                          A few incidents happened where filemaker crashed under the individual user and they could not connect to the shared filemaker databases for a few minutes after that. That is however because it did not gracefully disconnect, so the server assumes the user is already connected and thus it cannot reconnect. Waiting a few minutes fixes this. :)

                          The crashes were usually caused by faulty script commands (== my own damn fault)

                          -Peter