Elvas Tower: .NET CRASH IN X2533 - Elvas Tower

Jump to content

  • 2 Pages +
  • 1
  • 2
  • You cannot start a new topic
  • You cannot reply to this topic

.NET CRASH IN X2533 Rate Topic: -----

#1 User is offline   dennisat 

  • Conductor
  • Group: Posts: Contributing Member
  • Posts: 474
  • Joined: 16-February 13
  • Gender:Male
  • Simulator:Open Rails & MSTS
  • Country:

Posted 30 September 2014 - 09:02 AM

I'm getting the failure that can be seen in the attached log. After looking at the code at the point of failure, I believe I've got a problem with my .NET installation, probably missing Performance Counters?

Can anyone confirm this, I'm no expert in this area.

I'm running Windows 7 64bit Professional with .NET 4.5.1 and Visual Studio 2013 Express.

The only way I can run OR after X2533 is to comment out the patch put into "HUDWindow.cs". Clearly this is not a good long term solution.

I foresee a re-install and/or a repair of .NET coming up? :D


Dennis

Attached File  OpenRailsLog.txt (8.78K)
Number of downloads: 224

#2 User is online   James Ross 

  • Open Rails Developer
  • Group: Posts: Elite Member
  • Posts: 5,510
  • Joined: 30-June 10
  • Gender:Not Telling
  • Simulator:Open Rails
  • Country:

Posted 30 September 2014 - 09:49 AM

The problem is not with .NET, but your Operating System. Performance counters are a critical part of it which programs use to see what's going on globally and within themselves.

Please try following these steps carefully and see if it resolves the issue. This applies to Windows 2000, XP and Windows 7 at least. It may also apply to Windows 8 and 8.1, but take it slowly. I'd love to know if this resolves the issue or not - if it does, we can put an appropriate error message in to Open Rails itself (and maybe downgrade it to a warning).

#3 User is offline   dennisat 

  • Conductor
  • Group: Posts: Contributing Member
  • Posts: 474
  • Joined: 16-February 13
  • Gender:Male
  • Simulator:Open Rails & MSTS
  • Country:

Posted 30 September 2014 - 09:59 AM

View PostJames Ross, on 30 September 2014 - 09:49 AM, said:

Please try following these steps carefully and see if it resolves the issue....


Thanks for that, I'll give it a go now.
I have been browsing around trying to find something that seems to match my problem but up to now, everything suggested hasn't seemed appropriate.

Dennis

#4 User is offline   dennisat 

  • Conductor
  • Group: Posts: Contributing Member
  • Posts: 474
  • Joined: 16-February 13
  • Gender:Male
  • Simulator:Open Rails & MSTS
  • Country:

Posted 01 October 2014 - 03:43 AM

View Postdennisat, on 30 September 2014 - 09:59 AM, said:

Thanks for that, I'll give it a go now....


After a late night and all this morning I've finally got the problem resolved. The article has missed out from the section "Rebuild the base performance counters" that at the end of step 5 you have to execute "lodctr [path]\corperfmonsysmbols.ini" otherwise nothing happens!! At least not in Windows 7.

I only thought about doing that when I read the help for lodctr.

Dennis

#5 User is online   James Ross 

  • Open Rails Developer
  • Group: Posts: Elite Member
  • Posts: 5,510
  • Joined: 30-June 10
  • Gender:Not Telling
  • Simulator:Open Rails
  • Country:

Posted 01 October 2014 - 05:09 AM

View Postdennisat, on 01 October 2014 - 03:43 AM, said:

After a late night and all this morning I've finally got the problem resolved. The article has missed out from the section "Rebuild the base performance counters" that at the end of step 5 you have to execute "lodctr [path]\corperfmonsysmbols.ini" otherwise nothing happens!! At least not in Windows 7.

I only thought about doing that when I read the help for lodctr.


Is that not covered by the "Re-add the extensible counters" section, which says to do "lodctr" for each .ini file in System32? Or is the corperfmonsysmbols.ini file not in System32?

#6 User is offline   dennisat 

  • Conductor
  • Group: Posts: Contributing Member
  • Posts: 474
  • Joined: 16-February 13
  • Gender:Male
  • Simulator:Open Rails & MSTS
  • Country:

Posted 01 October 2014 - 06:58 AM

View PostJames Ross, on 01 October 2014 - 05:09 AM, said:

Is that not covered by the "Re-add the extensible counters" section, which says to do "lodctr" for each .ini file in System32? Or is the corperfmonsysmbols.ini file not in System32?


They are actually in "Microsoft.Net". For some reason I had missed "corperfmonsymbols" when I did the "findstr" list. However, looking at it again just now I see it does have "drivername" in it. I obviously wasn't paying proper attention last night when I did the "findstr" list.

Note to self - Double check everything. :yahoo:

Dennis

#7 User is online   James Ross 

  • Open Rails Developer
  • Group: Posts: Elite Member
  • Posts: 5,510
  • Joined: 30-June 10
  • Gender:Not Telling
  • Simulator:Open Rails
  • Country:

Posted 01 October 2014 - 08:57 AM

View Postdennisat, on 01 October 2014 - 06:58 AM, said:

They are actually in "Microsoft.Net". For some reason I had missed "corperfmonsymbols" when I did the "findstr" list. However, looking at it again just now I see it does have "drivername" in it. I obviously wasn't paying proper attention last night when I did the "findstr" list.

Note to self - Double check everything. :sign_oops:


Cool, so that has fixed the problem with Open Rails?

#8 User is offline   dennisat 

  • Conductor
  • Group: Posts: Contributing Member
  • Posts: 474
  • Joined: 16-February 13
  • Gender:Male
  • Simulator:Open Rails & MSTS
  • Country:

Posted 01 October 2014 - 09:29 AM

View PostJames Ross, on 01 October 2014 - 08:57 AM, said:

Cool, so that has fixed the problem with Open Rails?



It's worked with everything I've tried so far, thanks. I'm watching the Event Logs for anything odd that may happen as a result of the rebuild.

Dennis

#9 User is online   James Ross 

  • Open Rails Developer
  • Group: Posts: Elite Member
  • Posts: 5,510
  • Joined: 30-June 10
  • Gender:Not Telling
  • Simulator:Open Rails
  • Country:

Posted 02 October 2014 - 11:29 AM

Great, thanks; I've added a try/catch to Open Rails with a warning getting logged pointing people to that Microsoft support page if they encounter this issue.

#10 User is offline   R H Steele 

  • Executive Vice President
  • Group: Status: R.I.P. or just Retired
  • Posts: 3,562
  • Joined: 14-March 13
  • Gender:Male
  • Location:known universe
  • Simulator:Open Rails
  • Country:

Posted 02 October 2014 - 06:11 PM

Just interested. Followed the thread. Any ideas what would cause a problem like this? What would cause problems with the performance counters in the OS? I have not seen this pop up before in any of the OR threads.

#11 User is online   James Ross 

  • Open Rails Developer
  • Group: Posts: Elite Member
  • Posts: 5,510
  • Joined: 30-June 10
  • Gender:Not Telling
  • Simulator:Open Rails
  • Country:

Posted 02 October 2014 - 11:25 PM

View PostR H Steele, on 02 October 2014 - 06:11 PM, said:

Just interested. Followed the thread. Any ideas what would cause a problem like this? What would cause problems with the performance counters in the OS? I have not seen this pop up before in any of the OR threads.


Honestly, I'm not sure. I've had it happen a couple of times over the many years I've run Windows systems. It could be as simple as an app being uninstalled that had its own performance counters (any app can register to provide new performance counters but obviously most don't) but not doing the removal correctly.

#12 User is offline   dennisat 

  • Conductor
  • Group: Posts: Contributing Member
  • Posts: 474
  • Joined: 16-February 13
  • Gender:Male
  • Simulator:Open Rails & MSTS
  • Country:

Posted 03 October 2014 - 02:59 AM

View PostJames Ross, on 02 October 2014 - 11:25 PM, said:

Honestly, I'm not sure...


I strongly suspect my problem was running the old Nvidia Performance Monitor. I still ran it in Windows 7 for no really good reason - I'd always had it and very occasionally I looked at it.
Why was it a problem? I noticed in my excessive attempts to get my .NET counters going again that the DLL specified for the base counters was "donotload_mscoree.dll". This set me off on a hunt and I discovered that it was a Microsoft suggested fix to stop V1 of .NET hanging on closedown. I therefore removed the "donotload" prefix. To my surprise, on my next reboot I found it had re-appeared. After a while I tracked down the old Nvidia Monitor as the culprit and uninstalled it. After that, and a successful re-build of the counters, everything worked properly again.

I've not bothered to re-install the Nvidia Monitor to prove whether that was the cause, I'm not sure I can muster the willpower.

Dennis

#13 User is offline   JohnS 

  • Fireman
  • Group: Posts: Active Member
  • Posts: 231
  • Joined: 03-July 12
  • Gender:Male
  • Location:Portage, IN
  • Simulator:OR, MSTS, Railworks
  • Country:

Posted 15 February 2015 - 07:06 AM

I'm in the process of rebuilding the performance counters and have came to a wall. when I run findstr drivername *.ini no list appears. So what do I do next? It seems that should be a long list of drivers that need to be installed but I show nothing. I'm running Windows 7 Ultimate x64.

#14 User is online   James Ross 

  • Open Rails Developer
  • Group: Posts: Elite Member
  • Posts: 5,510
  • Joined: 30-June 10
  • Gender:Not Telling
  • Simulator:Open Rails
  • Country:

Posted 15 February 2015 - 03:18 PM

Skip that step and continue from "To rebuild all Performance counters including extensible and third-party counters in Windows Server 2003" which also applies to Windows Vista and later. I don't believe these versions have the drivername ini files - that was a Windows XP thing.

#15 User is offline   JohnS 

  • Fireman
  • Group: Posts: Active Member
  • Posts: 231
  • Joined: 03-July 12
  • Gender:Male
  • Location:Portage, IN
  • Simulator:OR, MSTS, Railworks
  • Country:

Posted 15 February 2015 - 04:37 PM

View PostJames Ross, on 15 February 2015 - 03:18 PM, said:

Skip that step and continue from "To rebuild all Performance counters including extensible and third-party counters in Windows Server 2003" which also applies to Windows Vista and later. I don't believe these versions have the drivername ini files - that was a Windows XP thing.


that would make sense then. Thank you I will give it a shot

  • 2 Pages +
  • 1
  • 2
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users