divadiow Posted January 13, 2014 Posted January 13, 2014 don't see if too often, but is anyone else getting a Windows crash report error come up when trying to run SIMS.net after having installed .net 4.5.1 framework update? can't any other posts or Capita KBs... 1
EJWill Posted January 13, 2014 Posted January 13, 2014 (edited) Yep, Apparently it's a known a problem when we rang Captia up. They're looking at solutions with no time frame. Right now the only way we've fixed it, is to run the .NET Framework clean up tool and remove 4.5.1 and then reinstalling 4.5. If you get your windows updates via WSUS or automatically, you will need to disable it trying to update itself again. We share your frustrations. Edit: Here is the link to the cleanup tool. .NET Framework Cleanup Tool User's Guide - Aaron Stebner's WebLog - Site Home - MSDN Blogs I hope this helps. Edited January 13, 2014 by EJWill 2
Cache Posted January 13, 2014 Posted January 13, 2014 Strange.... I've had it installed 2 weeks and, touch wood, not had any problems to date. Does reinstalling SIMS help the issue?
Michael Posted January 13, 2014 Posted January 13, 2014 I'm surprised as .NET 4.5.1 is just .NET 4.5 and post updates rolled into one. If you install .NET 4.5 these updates would get installed anyway... 1
EJWill Posted January 13, 2014 Posted January 13, 2014 (edited) It gets even stranger when you know some computers running 4.5.1 still allow SIMS to run. The error logs indicate it a .NET Framework error too on those that fail. We have around 500 computers and we seem to have this error on 8 of them. Maybe a hardware combination, or something more obscene, like a Microsoft issue. Reinstalling SIMS does not seem to resolve the issue for the ones erroring. Edited January 13, 2014 by EJWill
divadiow Posted January 13, 2014 Author Posted January 13, 2014 indeed. re-installing SIMS doesn't have an effect. I haven't really done much more than ascertain .net 4.5(.1) is to blame. annoyingly our Centrastage policy does have installation of 4.5+ .1 blocked.
vikpaw Posted January 14, 2014 Posted January 14, 2014 Will it not even let you log into SIMS? If it works for some machines. Does doing a clean install of 4.5.1 after a cleanup work?
FragglePete Posted January 14, 2014 Posted January 14, 2014 Not noticed this breaking anything here; we have to have 4.5.1 installed for the CSE System to even run here and not noticed any issues with SIMS. Pete
Greg Posted January 16, 2014 Posted January 16, 2014 In the Minimum System Requirements (Updated May 2013), Capita still states .Net 4 is required for SIMS Looks like 4.5.1 changes the existing 4 install From Installing the .NET Framework 4.5, 4.5.1 •The .NET Framework 4.5 and .NET Framework 4.5.1 replace the .NET Framework 4. When you install these versions on a system that has the .NET Framework 4 installed, the assemblies are replaced •Uninstalling the .NET Framework 4.5 also removes pre-existing .NET Framework 4 files. If you want to go back to the .NET Framework 4, you must reinstall it and any updates to it. (See Installing the .NET Framework 4.)
waltflanagan Posted April 23, 2014 Posted April 23, 2014 We've installed the Spring Update and Net Framework 4.5.1 still stops SIMS from Running.
divadiow Posted April 23, 2014 Author Posted April 23, 2014 We've installed the Spring Update and Net Framework 4.5.1 still stops SIMS from Running. Well that's just BRILLIANT. ffs
waltflanagan Posted April 24, 2014 Posted April 24, 2014 Capita and testing, in the same sentence...... NEVER.
Michael Posted April 24, 2014 Posted April 24, 2014 I've had SIMS running on .NET 4.5 for quite some time now. Not sure if WSUS dishes out the 4.5.1 update as yet as standard.
3s-gtech Posted April 24, 2014 Posted April 24, 2014 I can confirm that we have 4.5.1 site-wide and SIMS is working fine. It does sound like there is a common issue though, which Capita need to look at.
PhilNeal Posted April 25, 2014 Posted April 25, 2014 We have a very small number of cases raised on this issue but cannot reproduce the issue which makes it very difficult to resolve. There seems to be a security addition in 4.5.1 that affects certain sites.
PhilNeal Posted April 25, 2014 Posted April 25, 2014 A little more detail from the service desk: What we can confirm is that basic .Net Framework 4.5.1 with no updates works with SIMS, however, a security update released by Microsoft causes a conflict As we don’t know which security update is causing the issue we can’t confirm anything in terms of dates compared to our testing etc (one of the comments on the post was regarding us not testing, we wanted to know if the update came out after the release which would mean that no amount of testing would have found it). The only other thing to say is SIMS is intended to work with .Net framework 4, and we see no need to upgrade to 4.5.1 so all our testing would be done using .Net framework 4… although other things on the same server might need it, and we don’t explicitly not support 4.5.1 The issue relating to .net framework 4.5.1 has been seen by the Service Desk and we have created a KB (KB404647) to allow us to keep everyone informed of the latest information and provide a basic workaround. This problem is very intermittent in its nature and has only occurs after an upgrade to .net 4.5.1 which we believe may be caused by a security update. To help us identify which update, and ultimately resolve the issue, can I please ask that you log incidents on the Service Desk ([email protected]) which will allow us to isolate where the issue is and then produce a permanent fix. At present we only have a few examples to work on, so the more information that we are provided with the quicker we can resolve it.
vikpaw Posted April 25, 2014 Posted April 25, 2014 As it's not a blanket issue affecting all machines on a given site, i'd suspect it's a problem with the install or some conflict with other software that may be at fault. I don't think it's on my server, but the desktop clients have 4.5.1 and we've not had an issue. I'd want to see what happens when the affected machines are totally reinstalled, and set up the same way as other machines that do work.
waltflanagan Posted May 1, 2014 Posted May 1, 2014 We've been told that the only solution is to remove .Net 4.5.1 and install v4.5. We've installed the following reg key to stop the 4.5.1 update: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\WU] "BlockNetFramework451"=dword:00000001
eejit Posted May 7, 2014 Posted May 7, 2014 Hi guys, I see that 4.5.2 is out this morning. Anyone in a position to test that with SIMS? I don't have a machine that definitely doesn't work with 4.5.1 or I'd give it a go myself.
timbo343 Posted May 7, 2014 Posted May 7, 2014 Whoop!!!! SIMS is now working again on my machine with 4.5.2 installed!!! Dont have to keep logging onto the server just to use SIMS anymore. 1
PhilNeal Posted May 9, 2014 Posted May 9, 2014 Microsoft had said this was caused by a conflict with network stack components injected by 3rd Party applications (most commonly Antivirus or Firewall products). The Microsoft KB article suggested that they viewed this as a bug in the 3rd Party software, not in the framework, and were not intending to fix it. Based on this the guidance the service desk directed customers with the issue to the KB article, which provided a process for determined the likely source of the faulty component. It appears that 4.5.2 fixes the issue, so perhaps Microsoft have revised their stance. We’ll see what we can find out.
matt40k Posted May 9, 2014 Posted May 9, 2014 The Microsoft KB article suggested that they viewed this as a bug in the 3rd Party software, not in the framework ...and the KB is....
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