DB crashes in Windows but is Ok on my Mac

joseph1000 · October 24, 2003

I'm at a loss. Everything works fine with my DB when I'm using it on my Mac, but as soon as I try it on Windows 2000, certain layouts will crash Filemaker with this message:

FileMaker Pro.e.exe has generated errors and will be closed by Windows. You need to restart the Program. An error log is being created.

I have multiple files files in this database and the layouts that crash FMP are all contained in one file. The weird thing is that only 2 out of the three layouts in this file will crash FMP. One of those two won't crash unless I start to scroll down the layout. Does anyone have any idea what's going on here? I'm loosing hair over this!

Joseph

EDIT: I'm running FMP 5 on Windows 2000 (VPC 6) but on my Mac I'm using FMP 6 in OS X 10.2.8.

Vaughan · October 24, 2003

It'd be a corrupted image on the layouts that's causing the problem. It's been reported here on the Forums before.

Delete the errant layouts and rebuild them. It might be a good idea to do it in Windows so you know it works there.

Paolo · October 24, 2003

Most things creashes on Windows bur are ok on Mac.

Anatoli · October 24, 2003

Not in my world Take FM server... Or Adobe GoLive.

Actually to see crash on Windows is next to impossible.

Maybe 2-3 crashes in 6 years aren

dbruggmann · October 24, 2003

The other cause for the crash could be something with the fonts used. I had a similar problem once, which solved after I changed ALL the fonts to MS Verdana.

-Queue- · October 24, 2003

2000 seems to be very sensitive compared to other OSes. It's not unlikely for FM client to crash due to printer names, fonts, corrupt layouts, or 'print all scripts' from a file with a ton of calls to scripts in other files.

Anatoli · October 25, 2003

Sensitive 2000? I don't recall crash in 2 years

ernst · October 25, 2003

Hi Joseph,

Do I understand correctly that you are using Virtual PC ?

If so, disabling networking in Filemaker's application preferences, might do the trick.

Regards,

Ernst.

joseph1000 · October 26, 2003

Thanks for all the replies folks. Vaughan had it right. I'd dragged and dropped some text from a Word document onto the layouts in question. I'm assuming FMP converted the text to a Pict or something which cause the DB to crash in Windows. I just resaved the text as .jpg and that cleared it right up.

Thanks again.

Joseph

voxelman · February 13, 2004

I am seeing this same error message on three of our Windows 2000 Professional machines running 5.5 and 6.0. The problem has started in the past week. It occurs immediately after starting FM after the Splash screen is displayed.

There are no error messages in the log after this occurs.

All machines have unique, valid licenses.

I have performed clean installs with removal of the FileMaker folder from "C:Program Files" on one of the machines of both versions 5.5 and 6.0 and the problem continues to occur.

I get the same error even if networking is turned off and the machines are physically disconnected from the network.

kenneth2k1 · February 13, 2004

Take Vaughan's advice:

"It'd be a corrupted image on the layouts that's causing the problem. It's been reported here on the Forums before.

Delete the errant layouts and rebuild them. It might be a good idea to do it in Windows so you know it works there. "

In your case it could be a corrupt image or data. How good is your backup situation? You may want to try and take it to a Mac and delete the layout that first starts up. Last resort would be to import your files into an older version of your solution. The reason why uninstalling FM and trying different versions didn't work was because the problem is in your file, not FM.

BTW, in my opinion, Win2000 is the best OS that Microsoft has put out (if that says anything ). I could say some nastly little things about how MacOS managed memory up until OS10, but I won't. OS10 is about the most innovative OS i've worked on. In any case, Win2000 is rock solid in my experience.

voxelman · February 16, 2004

Thanks for the reply kenneth2k1.

What puzzles is that the problem occurs even when starting FileMaker without a database. The error occurs right at the splash screen without having selected a database file.

Is there anything that would be left behind after doing an uninstall that could cause it to try to load a file? I thought that the startup scripts were associated with database documents. I wasn't aware that FileMaker could be configured to automatically start a database when it was run from the "Start:Programs:FileMaker Pro".

EddyB · February 16, 2004

voxelman said:
I have performed clean installs with removal of the FileMaker folder from "C:Program Files" on one of the machines of both versions 5.5 and 6.0 and the problem continues to occur.

Hi,

You should never remove programs from windows by deleting the folder from "Program Files", by doing this you are leaving reduntant files all over the place and entries in your registry that are no longer valid.

You need to uninstall programs by either using the uninstaller provided with the software, or by going to control panel -> add remove programs, and remove it that way.

This applies to all software, not just FM. Try uninstalling FM correctly and reinstalling, let us know what happens then.

Regards

Ed.

kenneth2k1 · February 16, 2004

Wait, did you say that you uninstalled FM by deleting the folder in Program Files?

Another thing you might want to try is deleting your fonts folder because there might be a corrupted font that is not allowing it to load. Don't really delete it, just move it so that FM won't reference it.

kenneth2k1 · February 16, 2004

EddyB said:

Hi,

You should never remove programs from windows by deleting the folder from "Program Files", by doing this you are leaving reduntant files all over the place and entries in your registry that are no longer valid.

You need to uninstall programs by either using the uninstaller provided with the software, or by going to control panel -> add remove programs, and remove it that way.

This applies to all software, not just FM. Try uninstalling FM correctly and reinstalling, let us know what happens then.

Regards

Ed.

Yeah, I was curious about that too.

voxelman · February 17, 2004

I'm sorry I gave incomplete information. After using "Start:Settings:Control Panel:Add/Remove Programs" to remove FileMaker, I also removed the "C:Program FilesFileMaker" directory. The only thing that I haven't done is search the registry for a cause.

EddyB · February 17, 2004

Hi, no problem! Registry not a problem if you uninstalled that way.

Have you tried Kenneth's tip about moving the fonts folder so that FM cannot find it when it starts up?

If not give this a try and get back to us.

Best regards

Ed.

voxelman · February 17, 2004

Would this be "C:WINNTFonts" that I should move?

EddyB · February 17, 2004

That's the one, don't move it too far though! Just move it out of the WINNT directory, try starting FM, see what happens, then move the fonts folder back into the WINNT directory.

Let us know what happens...

Cheers

Ed.

voxelman · February 17, 2004

Hmm, can't move or rename the "C:WINNTFonts" folder. I have administrative privileges so that shouldn't be an issue.

EddyB · February 17, 2004

Hi, sorry it seems I have given you some dodgy info! The fonts folder in WINNT is obviously a system folder so it cannot be removed/moved/deleted.

Maybe Kenneth can tell you which folder it is you need to move...

Apologies again...

Ed

kenneth2k1 · February 17, 2004

I think this is how you would do it:

Create a new file (put it on your desktop. Open the fonts window, either through the Control Panel, or C:/WINNT/Fonts. Select all fonts, move them to the new folder. There will probably be a couple of fonts that will stay in the fonts folder, but that's ok. Close everything and restart FM. When you are done, you can move the fonts back into the fonts folder. Restart Windows and you should be able to delete the new folder that you created to move the fonts to.

What version are you running? Oh, I see 5.5 and 6. Are you running VPC also?

voxelman · February 17, 2004

After moving the fonts as suggested I'm still getting the error. I haven't tried any variations. Tomorrow....

kenneth2k1 · February 17, 2004

Hmmm. Well, we can try some other stuff.

I seem to remember something about ppl having problems with the user profile, and it went away when they switched profiles. Maybe try and log in as a different user and open FM and see if you get the same error. Make sure FM is a program that is available for all users. If you have no other user profiles, you can always create one.

Sign In

DB crashes in Windows but is Ok on my Mac

Recommended Posts

Create an account or sign in to comment

Create an account

Sign in

Similar Content

Important Information