Supporting Windows Question
.NET RUNTIME ERROR IN WINDOWS XP PRO SP3, EVENT ID 5000
I work for an Emergency 911 association, and our 911 workstations currently use Windows XP Pro SP3. They have no internet access for security reason, and the Standard Users are locked down with only the ability to launch the 911 software which then launches a mapping program. I know this sounds complicated but bare with me....
The mapping system recently started shooting a .NET 2.0 error when the 911 software attempted to launch it while logged in as a Standard User, however when logged in as a local or Domain Admin, it runs fine without any errors.
Here is the exact error we are receiving:
EventType clr20r3, P1 geobase.exe, P2 22.214.171.124, P3 4b6728da, P4 geobase, P5 126.96.36.199, P6 4b6728da, P7 5b, P8 e9, P9 system.invalidoperationexception, P10 NIL.
This is the Event Type Information: EventType clr20r3, P1 geobase.exe, P2 188.8.131.52, P3 4b6728da, P4 geobase, P5 184.108.40.206, P6 4b6728da, P7 5b, P8 e9, P9 system.invalidoperationexception, P10 NIL.
Is there anyone who could help me troubleshoot this is? I have IT involved with the IT department that makes the geobase.exe software and the IT department that makes the 911 software, and of course I am IT as well. Ultimately I have realized I need a Microsoft person, because I think it may just be a .NET patch that is needed, but that's just a guess...
Thanks in advance:
Community Chosen Answer
Before we get trying to weed out .net lets try a couple of easy things, it acts like it cannot update some local data in the users profiles.
If you login as a new user and get a new profile does it do this?
(If it works the install could have updated default but not existing. Could be bad existing profiles or they cannot make a needed change due to lack of rights)
If you make an existing user a temp admin, let them login once, take away admin rights, then have them login does it do it?
(something needs to update each users profile and you will need to trace that down)