AnsweredAssumed Answered

Filemaker 10 Crashing on Terminal Server

Question asked by chris.demaj on May 18, 2009
Latest reply on Nov 24, 2010 by lordhellfire

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

Outcomes