Jump to content
Server Maintenance This Week. ×

FMP10 Crash on startup


Cormack

This topic is 4726 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies

I'm wondering if anyone has experienced this before, and might have a solution for me.

We have 5 users running FileMaker Pro 10 on cross-platform machines (mostly Windows XP, one or two on MacOS X Leopard). All are working fine except for one Windows XP user. When he runs FileMaker Pro, it brings up the splash screen and then after a moment or two crashes, with the following error message:

Error Signature

AppName: filemaker pro.exe AppVer: 10.0.1.92 ModName: filemaker pro.exe

ModVer: 10.0.1.92 Offset: 00940093

I get the same error with the 10.0.2 version of the client (other than the version numbers being different).

I can't see anything obvious that would be causing this, and have tried reinstalling and repairing without success.

I'm in desparate need of a solution (other than "rebuild the PC"! ;) ) so if anyone has any ideas, please let me know.

Cheers in advance.

Link to comment
Share on other sites

  • Newbies

Nope, its SP2.

Its also not a user setting - I get the same response when logged in with a different account.

I can only think that its either some sort of corrupted registry setting, or that some other piece of software is clashing with it.

Any other ideas chaps?

Link to comment
Share on other sites

  • 1 year later...
  • Newbies

Guess it;s the best place to fit my question.

I'm working with FMP10, on WinXP SP3 [system uptime is about 3 years]

From time to time, usually after a break (2-3 days), my FMP10 crushes on splashscreen.

With regular Microsoft error message, and following information:

Error signature

AppName filemaker pro.exe

AppVer: 10.0.1.26

ModName: ntdll.dll

ModVer: 5.1.2600.6055

Offset: 0001240b

Such an error happened earlier, and I was able to "fix" it, by copying ntdll.dll from system32 folder into FMP10 folder. [shamanism, I know, but for some reason it worked] This time, playing around with ntdll.dll didn't helped.

I also saved full crash report, in case it will be needing.

Link to comment
Share on other sites

This topic is 4726 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.