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

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

Recommended Posts

Posted

A very unusual situation that I've come across. A client has Server 5.5 on a Windows 2003 server, hosting 32 files, and acessing the database with FM Pro 6.

When the database is launched, it opens 15 of said files. The others are only open on the workstation(s) when user specifically wants to. There is one file that, when opening, always gives the error 'Communication with host has been interrupted.....'. I've seen this error before, and usually indicates a slow/improper network connection (feel free to correct me if I'm stating this wrong).

Anyway, all of the other files open just fine, it's just this one file. I see through the remote administion that the file is being hosted. I replaced the file with a fresh copy - no go. I even confirmed that the file wasn't corrupted somehow by copying all of the files to a workstation and opening all of them (including this troubled one) just using Pro 6. They open and performed just fine.

The error logs on the server didn't indicate anything other than that one file was closed due to an error (didn't indicate WHAT error).

If anyone could give me some kind of insite to what else to look for, I would greatly appreciate it.

Posted

When you get the error, all the other open files on the workstation need to be closed too, right?

Strange situation. Try to narrow down where in the opening process it occurs (script running, what layouts involved,...)

Posted

you say "I even confirmed that the file wasn't corrupted by ... opening all of them (including this troubled one) just using Pro 6"

unfortunately, corruption is still possible. see my post here: http://masdevelopment.com:3455/1/57?view=print

also:

1. check for scripts set to run on open

2. try opening to a blank (or different) layout, on that one file

3. try hosting an empty "clone" of that file

Posted

Wim - I don't know if the other files *needed* to be closed, but it closed them for me (without any intervention on my part).

I'm not doubting file corruption, but I find it odd that it still does it even after I have replaced the file with a known good working copy.

I hadn't thought of using the developer debugger to see exactly where it give said error. I do notice the file DOES open initially (confirmed by seeing the file name in the upper left corner of the screen. It appears that the opening script hasn't run all the way through, but I'll determine that soon enough.

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