Memory Could Not Be Written Message in Filemaker

I have a client who is hosting their Filemaker solution on a Windows 2003 server. The server has less than 6gb available and on the client machines (WinXP), they're getting an error message that says:

Memory could not be "written." Click on OK to terminate the program.

It is also preceded by a line about referenced memory. See a screenshot here: http://img2.freeimagehosting.net/uploads/d022ecb97c.jpg
baadayakaziAsked:
Who is Participating?
 
lesouefConnect With a Mentor Commented:
unlikely to be the server... probably a bug on client side, v9 is still recent... does it do it under certain particular circumstances or randomly? with all databases or only one?
first unshare the file, take it locally and use file/recover with the fmaker stand alone. put it back on server, and see if any better.
0
 
baadayakaziAuthor Commented:
only on one of the databases
0
 
lesouefCommented:
wouahh, 6 month, not bad!
only on 1 file, so I confirm, recover it as specifield in the previous post
0
Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

 
zstokesCommented:
I'm actually having the same issue, although (and don't laugh) we are running FileMaker 5.5 server/client.  We do NOT get the error on a WinXP SP1 machine, but we do get it on a WinXP SP2 machine.  I'm going to add SP3 and test.  I'll post the results here.
0
 
baadayakaziAuthor Commented:
I did a recover, and it seems to be working fine.
0
 
lesouefCommented:
the original post did not spécify the version, so is it the same as yours? no idea.
I don't use fm5.5, but I still have fm6.0r4 which runs perfect under xpsp2. So I think the file is the problem, and that it should be recovered to start with. and try at least to upgrade to fm6 as fm5.5 was a intermediate version which did not last too long, so not the best for reliability.
0
 
zstokesCommented:
Well we've gotten a little further with this, but the fault domain is starting to look really specific.

It seems that with a specific in-house XP SP2 build, FMP 5.5 crashes out when Quicktime (any version going to back to 5.x) is installed.  The Dr. Watson report shows that quicktime.qts is faulting module.  When Quicktime is NOT installed, the app works perfectly.  Also, there are many other FMP 'databases' that work woth no problem at all whether Quicktime is installed or not.

If I ever get a more specific cause I'll be sure to report that here.
0
 
lesouefCommented:
the guilty one may inlcude an image which is quicktime compressed....
0
 
zstokesCommented:
That's it!  That fixed my issue.  Maybe the original thread-starter should try it too?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.