MIS Systems Thread, Help needed with FMS since Capita can't resolve an issue with there own software. in Technical; SQL Native Client error Common link Failure with FMS 6.138.
I have a school that have Server 2003 & windows ...
Help needed with FMS since Capita can't resolve an issue with there own software.
SQL Native Client error Common link Failure with FMS 6.138.
I have a school that have Server 2003 & windows 7 laptops. They are getting intermittent issue where it sates "You have altered your system clock. It strongly recommended that you re-start module in order to ensure client/server system date/time integrity."
Both the server & workstation time are same. Regional settings are all set correctly. Even reset the faults on the windows 7 laptops. There is no time syncs going on the network.
Still no resolved. Logged call with Capita and this was given the following rubbish response:-
Activity Date: 20/07/2011 10:31:22 Communication Type: E-mail
Activity by: Bradley Cotton
I have spoken to a colleague regarding this issue. Unfortunately there is nothing that can be done with this issue as it is an intermittent issue. The same issues occur when running FMS over a virtual machine. Apologies for any inconvenience caused.
Your first replay. Already done the "regional settings". I found a slightly quicker way, Go into Region and Language, then "Administrative" tab and click "Copy settings", then at the bottom put a tick in "Welcome screen and system account" + "New Users". The ping test is fine both on wired and wireless. I have had one laptop running on wired and the other on wireless. When the problem occurs it happens on both machines at the same time which is pointing to me as if a server/network issue not workstation.
Your second replay. Yes I had found that KB on Microsoft website and have already applied. The Server is fully serviced packed and all updates applied.
I have looked at just about every think I can thinks from changing windows update times to sophos AV scans. The main problem is there is no patter to it. Can happen one time one day and then go few days no issue. Then another day it can happen 10 times. I also run network diag and left them running so see if I could capture an issue. Apart from this issue the schools network runs sweet.
Any other suggestions would be useful. My next step if nobody can help is to upgrade them to 6.140 and see what happens. I am also going to upgrade there spare windows xp laptop and run that side by side with windows 7 machines.
I support a piece of software that gives a "communication link failure" from time to time, and to be fair the problem is between the SQL DB and the SQL client, outside of the control of the application itself. What it does do is trigger a sequence of increasingly hysterical error messages, but the problem there is poor error trapping in the app, the issue is still the link failure.
And that's exactly what it means for us. Always found it to be a network problem of some kind, whether it be a drop out (good call on the wireless question) or a dodgy NIC (is it always one client? Does it affect multiple machines at once?).
I've also read of people having problems where servers are starved of resource, but never come across that one myself.
@theriver It is happening to multiple machines. What is so strange is that this has been a great network with nothing much changing except upgrading to 6.138 and getting the issues. Even though the server is 2003 it is still well spec Dell.
@teejay: Yes migrated to SQL2008 last December. I have also detached the database and reattached database using SQL2008 Migration tool in advanced mode to make sure no issues. The original migration was done via automatic deployment script.
Could it be the nic in the server which is intermittently losing the connection?
Would it take much to change it?
Funny was about to say, last time removing KB91222 or disabling the TCP Chimney Offload feature didn't work, swapping the NIC fix it. Even disabling the onboard dual gigabit and putting in a intel pro 100+ fix it.