Sometimes customers need to create their own service monitor. This usually leads them to the Windows
Anonymous
22 Jun 2011 12:26 AM
Anonymous
22 Jun 2011 12:27 AM
Sometimes customers need to create their own Windows service monitors. This usually leads them to the
Anonymous
22 Jun 2011 12:29 AM
Sometimes customers need to create their own Windows service monitors. This usually leads them to the
Anonymous
22 Jun 2011 12:30 AM
Sometimes customers need to create their own Windows service monitors. This usually leads them to the
Anonymous
22 Jun 2011 12:31 AM
Sometimes customers need to create their own Windows service monitors. This usually leads them to the
Anonymous
25 Jun 2011 5:52 PM
Shortly after posting the sample Windows service monitoring library , I realized a “short”
14 Sep 2011 5:33 PM
After CU4, you will get the following error (see BR13's post):
Error 1:
: Could not load ManagementPack [ID=Microsoft.SystemCenter.Library, Keytoken=31b
f3856ad364e35, Version=6.1.7221.61]. ManagementPack not found in the store.
Cannot find MP File "Microsoft.SystemCenter.Library.mp" in any of the search dir
ectories.
This is because the version 6.1.7221.61 is not copied to the RMS installation folder, and therefore is not in your source directory. You need to manually edit the XML MP that you want to seal, and change the reference to the Microsoft.SystemCenter.Library.
I suggest using XML Notepad to open the unsealed MP. Go to the Manifest section, then References, and select the appropriate Reference (Microsoft.SystemCenter.Library). Change the version number to 6.1.7221.0 instead of 6.1.7221.61.
23 Sep 2011 7:12 PM
You may also download the latest version of this file here: support.microsoft.com/.../2590414
Anonymous
10 Aug 2012 12:21 AM
Written by Mark Farrugia, Senior Microsoft Premier Field Engineer. In my previous post I started down
Anonymous
10 Aug 2012 12:21 AM
Written by Mark Farrugia, Senior Microsoft Premier Field Engineer. In my previous post I started down
24 May 2013 11:41 PM
I was having trouble with the second two "sn" commands crashing .NET 4.0 sn.exe on both a windows 8 and a windows 7 machine. found in another thread that I needed to copy snrc.dll into the same directory as sn.exe.
stackoverflow.com/.../getting-issue-with-sn-exe-running-outside-the-netfx-4-0-tools