Asked by:
Error - System.ServiceModel 4.0.0.0 - Performance Counter ----in the Event Viewer

General discussion
-
I have whs2011 up and running just fine, access to the internet etc.
The Client win7/Pro is connected just fine.
However, in BOTH the Client and the Server's "Event Viewer", I have the error message:
----------------------
Log Name: Application
Source: System.ServiceModel 4.0.0.0
Date: 6/28/2011 4:56:50 PM
Event ID: 10
Task Category: Performance Counter
Level: Error
Keywords: Classic
User: LOCAL SERVICE
Computer: vidbox990
Description:
A performance counter was not loaded.
Category Name: SMSvcHost 4.0.0.0
Counter Name: Protocol Failures over net.pipe
Exception:System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
at System.Diagnostics.PerformanceCounter.InitializeImpl()
at System.Diagnostics.PerformanceCounter.get_RawValue()
at System.ServiceModel.Diagnostics.PerformanceCounters.GetPerformanceCounterInternal(String categoryName, String perfCounterName, String instanceName, PerformanceCounterInstanceLifetime instanceLifetime)
Process Name: SMSvcHost
Process ID: 2164
---------------------------
****Obviously there is a lot more to this but you get the basic info.
****There is about 14 of them and the counter errors are, from top to bottom so in reverse chronological order:
---------------------------------------------
Protocol Failures over net.pipe
Protocol Failures over net.tcp
Connections Accepted over net.pipe
Connections Accepted over net.tcp
Registrations Active for net.pipe
Registrations Active for net.tcp
Uris Unregistered for net.pipe
Uris Unregistered for net.tcp
Uris Registered for net.pipe
Uris Registered for net.tcp
Dispatch failures over net.pipe
Dispatch failures over net.tcp
Connections dispatched over net.pipe
Connections dispatched over net.tcp
-----------------------------------------
Ok, now if things seem to be running fine is this one of those "don't stare at the event viewer log too much as it will drive you nuts", or is this something that should be fixed?
The WHS had these error logs since it was installed and only does it on startup/reboot.
The client only started getting these errors after installing the connection software and does it on each bootup also.
Again, only these 14 messages, and that's it, everything else seems "normal".
Thanks!!
Wednesday, June 29, 2011 1:42 AM
All replies
-
Exactly the same issue here after starting to use WHS2011.Sunday, July 3, 2011 8:33 PM
-
Same thing here. I have two WHS installs and one doesn't have these errors though. Also one of my PCs with the connector software doesn't either but the rest do.Sunday, July 3, 2011 10:10 PM
-
Exactly the same issue here too.
//H
Sunday, July 10, 2011 7:48 AM -
Just as a followup, I have it on both whs, one a rebuild of ex495 and Asus P8H67-m Pro. Both with Realtech PCIe GBE Family Controllers. All 7 of my win7 PC clients also have the messages. The router/modem is Netgear WNDR3700v2 with updated firmware.
Nothing else seems to be wrong, so no issues other than above.
djb
Sunday, July 10, 2011 8:57 PM -
I finally fixed it by repairing the .Net 4.0 installation. it appears that the associated registry entry was incomplete or missing. seems that WHS install missed a step.Monday, July 11, 2011 2:41 AM
-
For the record, repairing the .Net 4.0 components did fix this. No error messages the past two days. I found same error on two Windows 7 machines and applied the same fix.
Thursday, July 14, 2011 2:36 PM -
I'll bite, how'd you fix it?
Thanks!
Friday, July 15, 2011 2:44 AM -
I'll bite, how'd you fix it?
Thanks!
Probably by going to Control Panel/Programs/Programs and Feature/Uninstall/Change - Selecting Repair
Or search for "Uninstall a program" in the start/search window - select Microsoft .NET Framework 4 - when you launch it to Uninstall it offers a repair option.
I have two Microsoft .NET Framework 4 entries (Client Profile & Extended) I repaired them both.
Hopefully it will correct the spurious errors I am seeing.
Edit: This did correct the problem.
- Edited by Phil Usher Wednesday, July 27, 2011 5:18 PM Confirming that fix worked.
Friday, July 15, 2011 7:14 PM -
I finally fixed it by repairing the .Net 4.0 installation. it appears that the associated registry entry was incomplete or missing. seems that WHS install missed a step.
This worked perfectly for me. Many thanks :)Thursday, August 4, 2011 3:48 AM -
Exactly the same issue here after starting to use WHS2011.
Repairing Microsoft .NET Framework 4 worked for me also....
Sunday, August 7, 2011 10:11 PM