Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

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

Recommended Posts

  • Newbies
Posted

Filemaker pro 6 on windows unexpectedly quitting when database is accessesed through the web.

We tried updating the patches and updates of the filemaker and web-companion but still it quits every so often without any sign or error telling what went wrong.

Can you please advice on what is needed to be done and what is causing this.

Pls help me!!!!

Posted

Which version of Windows?

Is this a new issue or has it always happened with your current configuration?

What do you mean FileMaker "quits?" You mean it freezes? Closes?

Posted

It's been a while since I've heard this on the Windows side, but it seems to be common enough on the Mac side, and there has been no universal solution yet, AFAIK... different things help different situations (reboots, corrupted db's, etc.). I think Mariano Peterson posted that on his Windows set up, he determined it was a web user cancellation of a request before the server could respond since it was busy doing another task (backup?) when the user initiated the request and then got impatient and went on to something else. When the server finally processed the request, there was no one to give the response to and it dumped. I can't remember exacty and I may be confusing it w/someone else's posts, but you can search the posts and find several threads about this... mostly in the FileMaker Pro Unlimited forum.

--ST

  • Newbies
Posted

Before we didnt have any problems but I dont know what happened and the problem arised. I have 45 dbs running on the filemaker. Sometimes when i request throught the web. the filemaker just closes unexpectedly. I tried it on windowsxp and windows2K and it still the same.

Posted

It appears you are saying you have tried hosting the files on both a Windows XP and Windows 2000 PC. Since it doesn't appear to be OS dependent and the solution used to work fine then maybe -

*something has changed on your network

* a database(s) could have a corruption problem

* something has changed on the client side - browser settings etc.

This topic is 7441 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.