Ironically, we started having this issue last week. I am not sure what is the cause but the end users are having real speed issues and then they get the message and it disconnects. I was just about to post the issue myself today.
We are on Citrix as well but we are still using FMS9.
The only change in environment has been a patch update last weekend to our production servers which include both the Citrix servers and production FMS.
After looking through the list of patch fixes, the only one that I think corresponds even remotely close is:
I can not effectively pinpoint the exact cause. All I know is that this is a recent issue but critical. It hasnt taken down the server yet but when it happens I can not even go to 'Open Remote' and see the files. The files disappear from the Pro Client. If i give it a few minutes, they will come back. Again intermitant.
Kicking out the users and restarting the server fixes it until usally the next day.
BTW, if I check the server stats, the CPU and memory look okay, although the FMS process is slightly high at around 924MB memory usage. With a reboot it is around the high 600s.
From my experience, FMS likes to be around high 700s / low 800s. Whenever we have had issues in the past crashing etc. is when it was in the 900s. But I can not accurately say that is 100% true but rather just an observation.
Please list out whatever else info you can so that maybe we can find a pattern here as I can not keep kicking out the users.
Thank you for your info.
I have Windows 2008 STD server with Hyper-V. FMS 10 is installed on Win2008 STD. I have virtual win2008 (x32) on Hyper-V (Which is terminal server). I have FM Pro 10 installed on terminal server. Users were claiming that the issue when away for couple of days and came back again after we updated NIC driver. I have Trend Micro antivirus software installed on both server. I made exclusion rules for FMS and FM Pro.
I had SBS 2003 with FM 6 on that. I shout it down couple of days ago (I am thinking when I shut it down users were not facing that issue). The server was on for last one week. I shut it down today. But we are still having that issue.
Some help would be appreciated.
We are on:
Window 2003 R2 Enterprise. SP2
McAfee but exclusions to where the dbs are located
Dual NIC but 1 turned off because teaming has given FMS issues in the past
Citrix Servers on 2003 as well.
I turned on PerfMon last week after we had the issue 2 times in 3 days. Today we are having the same issues again. However, this time I did not restart the server yet.
I may run FMS in debug mode but dont think I am going to do it yet.
Could you check to see if that Windows patch has been applied and if so when?
Also are you using an ESS tables?
When I tried to apply the patch, it said patch is not applicable to your machine.
no. I am using terminal server. Users are connected to the terminal server via remote desktop.
Also, I have 2 nics on my host server.
Windows update is installed on the server.
Is the terminal server session timing out or going to sleep?
I'm having a similar problem, except on one single brand new mac running "FileMaker Pro 11v3".
The Server is "Filemaker Server 11v2", & i have a mixed environment of Terminal Server 2003, Windows XP, & Mac OS X (all but this one client computer is running, "Filemaker Pro 11v2").
To make it worse the problem happens about 2-3 time a day, only on this one computer. Always in the afternoon, just after lunch, then mid afternoon & occasionally in the mornings.
The Only thing that has change is this computer was upgrade to a brand new machine, using the same ethernet port that the old one was on, (the old one didn't have this problem).
From the timing i would say there is something else happening like a flood of data on the network occurring at these recurring times, that has priority over FMS protocols. Except that it only happens to this one computer, & it didn't happen to the old one, plugged into the same ethernet port.
The Error Read "Communications with the host was interrupted and could not be re-established. All affected windows will be closed." then the user has to reopen there filemaker databases.