FIX: "Category Not Found" Error Message When You Run a New Visual Studio .NET Application in a Side-by-Side Environment

Article translations Article translations
Article ID: 813350 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all


A side-by-side computer is one where both the .NET Framework version 1.0 (installed with Visual Studio .NET) and the .NET Framework version 1.1 (Everett) are installed.


  1. On a side-by-side computer, create a Performance Monitor counter.
  2. Use the Performance Monitor counter in a class when you use the .NET Framework version 1.0 to design an application.
  3. Run the application that uses the class (runtime).
In this scenario, the application may fail and you may receive the following Exception error message:
Category not found
You may also receive the following error message:
Exception Type: System.InvalidOperationException 
Message: Cannot create file mapping. 
StackTrace Information 
 at System.Diagnostics.FileMapping.Initialize() 
 at System.Diagnostics.FileMapping..ctor() 
 at System.Diagnostics.SharedPerformanceCounter.get_FileView() 
 at System.Diagnostics.SharedPerformanceCounter.ResolveOffset(Int32 offset) 
 at System.Diagnostics.SharedPerformanceCounter.GetCounter(String categoryName, 
    String counterName, String instanceName) 
 at System.Diagnostics.SharedPerformanceCounter..ctor(String categoryName, 
    String counterName, String instanceName) 
 at System.Diagnostics.PerformanceCounter.Initialize() 
 at System.Diagnostics.PerformanceCounter..ctor(String categoryName, 
    String counterName, String instanceName, Boolean readOnly) 
 at ... [application call stack here]


A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next .NET Framework service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version       Size       File name
   24-Jan-2003  18:40  1.0.3705.398    311,296  System.Runtime.Remoting.dll
   24-Jan-2003  18:40  1.0.3705.398  1,171,456  System.dll
   24-Jan-2003  18:43  1.0.3705.398    503,808  System.Web.Services.dll


Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.


Article ID: 813350 - Last Review: October 26, 2013 - Revision: 2.4
  • Microsoft .NET Framework 1.0
kbnosurvey kbarchive kberrmsg kbbug kbfix kbqfe kbnetframe100presp3fix kbhotfixserver KB813350

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from