The configuration information of the performance library "C:\WINDOWS\system32\netfxperf.dll" for the "TFS WorkItem Tracking" service... Part II

by Gabriel Lozano-Moran 17. January 2008 13:09

The problem

A while ago I posted this:

The configuration information of the performance library "C:\WINDOWS\system32\netfxperf.dll" for the "TFS WorkItem Tracking" service...

But for some reason the problem has returned.

image

In my previous post I used the /T command-line argument of the lodctr command to set the performance counter service as trusted. Today I have tried a somehow different approach to solve this problem and only time will tell whether this approach helped or not. This is based on the information found in Microsoft KB267831.

In our situation we are talking about the configuration information of the performance library for 4 different services:

The configuration information of the performance library "C:\WINDOWS\system32\netfxperf.dll" for the "TFS WorkItem Tracking" service does not match the trusted performance library information stored in the registry. The functions in this library will not be treated as trusted.

The configuration information of the performance library "C:\WINDOWS\system32\netfxperf.dll" for the "TFS Version Control" service does not match the trusted performance library information stored in the registry. The functions in this library will not be treated as trusted.

The configuration information of the performance library "C:\WINDOWS\system32\netfxperf.dll" for the "TFS Services" service does not match the trusted performance library information stored in the registry. The functions in this library will not be treated as trusted.

The configuration information of the performance library "C:\WINDOWS\system32\aspperf.dll" for the "ASP" service does not match the trusted performance library information stored in the registry. The functions in this library will not be treated as trusted.

Unload the performance dynamic-link libraries

I opened a command prompt and run the following commands:

C:\>unlodctr "TFS WorkItem Tracking"

Removing counter names and explain text for TFS WorkItem Tracking
Updating text for language 009
C:\>unlodctr "TFS Version Control"

Removing counter names and explain text for TFS Version Control
Updating text for language 009
C:\>unlodctr "TFS Services"

Removing counter names and explain text for TFS Services
Updating text for language 009
C:\>unlodctr "ASP"

Removing counter names and explain text for ASP
Updating text for language 009

Locate the initialization files

Next thing you need to do is locate the initialization files (.ini) for each of the services.

TFS WorkItem Tracking: %programfiles%\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\WorkItemTracking\bin\WITPerf.ini

TFS Version Control: %programfiles%\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\VersionControl\bin\VCPerf.ini

TFS Services: %programfiles%\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\Services\bin\TFPerf.ini

ASP: %windir%\System32\axperf.ini

Update registry values related to performance counters

Run the following commands:

C:\>lodctr "%programfiles%\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\WorkItemTracking\bin\WITPerf.ini"
C:\>lodctr "%programfiles%\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\VersionControl\bin\VCPerf.ini"
C:\>lodctr "%programfiles%\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\Services\bin\TFPerf.ini"
C:\>lodctr "%windir%\System32\axperf.ini"

Now let's hope that this solved the problem!

Tags: ,

Team Foundation

Comments

2/28/2008 11:16:09 PM #

Joe

Perhaps you could update this page and indicate whether this solution worked for you.

I'd also expect you to post the version of Windows that this works for.

Thanks for the post, but for being a claimed aficionado, I'm disappointed in the thoroughness of the posting.

Joe | Reply

2/29/2008 2:34:23 AM #

Gabriel Lozano-Moran

Hello Joe

Whether this worked or not I am no longer able to tell. Because our TFS box crashed I had to perform a restoration-based move to a new machine and on this machine we no longer have these problems. Furthermore I am a .NET aficionado and this post is not really .NET related therefore I apologize for my lack of deeper knowledge of the topic.

Regards

Gabriel

Gabriel Lozano-Moran | Reply

Add comment




  Country flag


  • Comment
  • Preview
Loading