Kineas Posted February 25, 2015 Posted February 25, 2015 I'm getting this error quite a lot on all computers on the network. Users can log into SIMS fine, but every now and again a message appears in the bottom left of the screen saying "Failing Network Request; retrying..." I've spoken to the SIMS team with the local authority who have remoted onto the server and said "everything looks fine, check your network switches". The switches look fine, no loops (which would have brought down the entire network). When this error occurs, I can still ping the SIMS server and browse it's shared folders and everything fine. The computers all seem to show this error at different times as well. I've tried re-installing and it still happens. I'm getting similar issues on FMS but no error messages on that, it seems to be a lot more sensitive to network outages (or whatever this is) and just crashes, whereas SIMS just keeps trying to reconnect until it can. The SIMS server firewall is off. I'm at a bit of a loss with this!
Dkeen94 Posted February 25, 2015 Posted February 25, 2015 Can you get a solid ping between the server and the clients for a consistent amount of time? Are you sure the switches arent dropping packets every now and then?
Kineas Posted February 25, 2015 Author Posted February 25, 2015 Doing a constant ping to the SIMS server over about 10 minutes, I dropped about 2 packets in that whole time but I am currently connecting via wireless. When those packets dropped, the error in SIMS didn't appear. When the error did appear in SIMS, I was getting consistent successful pings.
vikpaw Posted February 25, 2015 Posted February 25, 2015 Can you post a pic of the error with sims screen? Never seen that and interested to see it. Can you check the server when the error happens? Is it possible it or the SQL process is busy? Do you have full SQL, if not it might be being throttled. The SIMS homepage widgets keep and maintain a regular connection to the server so could create random moments of peak usage. It would explain why FMS is also affected, but generally server is pingable. FMS is sensitive as it holds things open and locked, so a break in connection will cause it to crash out.
Kineas Posted February 25, 2015 Author Posted February 25, 2015 How do I check whether the database is full?
vikpaw Posted February 25, 2015 Posted February 25, 2015 Sorry, i meant the version of SQL server, there is the full edition or the free one, which has limitations. Even with Full, some versions have a limited user / connection count, though mostly people have it installed on a per CPU license which means unlimited users. Might not be the issue, but a straw worth clutching at and checking. You should be able to tell from SQL Management studio, or by looking on the server at what is installed.
splattthecat Posted February 25, 2015 Posted February 25, 2015 Interesting... we have started getting this at a couple of our larger secondary schools. SQL Server version is full. We now advise ensuring any power saving features on the network adapter is switched off, as this can cause issues, particularly with FMS.
mdrabble Posted February 25, 2015 Posted February 25, 2015 Very interesting..... this was reported to me couple of weeks ago, couldn't find any reason for it other than putting it down to old switches. Seems to come and go randomly. Not had chance to investigate further yet as not in school this week.
vikpaw Posted February 25, 2015 Posted February 25, 2015 Interesting... we have started getting this at a couple of our larger secondary schools. SQL Server version is full. We now advise ensuring any power saving features on the network adapter is switched off, as this can cause issues, particularly with FMS. Very interesting..... this was reported to me couple of weeks ago, couldn't find any reason for it other than putting it down to old switches. Seems to come and go randomly. Not had chance to investigate further yet as not in school this week. Uh oh! So it might be a new "feature"... I don't suppose it's SQL 14 - i saw people are having to put it into compatibility mode. Is SIMS unusable while this message is appearing?
MrMat Posted February 25, 2015 Posted February 25, 2015 Pretty sure it's InTouch. I'm assuming you use InTouch? Test your InTouch Service Setup and see if it fails.
Tefters Posted February 25, 2015 Posted February 25, 2015 Jumping on this too as I have had a user saying she has noticed this error for a few weeks now but does not impact performance or usage. She has only just got around to sending me a screenshot of it today and its exactly the same as Kineas. I'm running full SQL 2012 on Server 2008 R2 with a good 10 other DB's and never had this issue up until now, not that its really an issue. I noticed on Kineas picture he's running Windows 7 (or even Vista) on the client, i'm Windows 8.1, also I know it cannot be our network as we would exhibit bigger problems than this.
splattthecat Posted February 25, 2015 Posted February 25, 2015 Not SQL2014 here, one school is still on SQL2008, but soon to be upgraded to SQL2012, the other is SQL2012. The school with the most issues are using InTouch, the other school has only reported issued with FMS, which I suspect might be locking issues.
mdrabble Posted February 25, 2015 Posted February 25, 2015 I need to check which version of sql as not really touch the sims since I started 2 and a bit months ago
vikpaw Posted February 25, 2015 Posted February 25, 2015 Has INTouch moved to the System Service Manager thing?
mdrabble Posted February 26, 2015 Posted February 26, 2015 (edited) Just checked and running SQL2012 Full, with Intouch. Person who does the cover first noticed it, mainly when she tried to save staffing changes, it would mention the failure, she would try resaving where SIMS would then crash but strangely SIMS does save before crashing. Anyone with these messages also running Discover? Wonder if it reporting this to Capita if several people are getting this. Edited February 26, 2015 by mdrabble
vikpaw Posted February 26, 2015 Posted February 26, 2015 Definitely get everything logged with support companies as there doesn't seem to be any evidence of this on SupportNet and they need to know.
superfletch Posted February 27, 2015 Posted February 27, 2015 I see this now and again in SIMS although I see no obvious performance problems or issues when it occurs and SIMS daves fine. No intouch here, unfortunately we're not in a position to do any network related work or investigation. Think sending something to Capita seems worthwhile.
Damon Posted June 11, 2015 Posted June 11, 2015 I've not come across this before but could it be related to a timeout? Might be worth adding the old CommandTimeout line at the bottom of your connect ini. The following is a good place to start: CommandTimeout=100000
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now