Counter values you need are not available in the NTSMF data collection file

This procedure is for diagnosing data collection problems where the Counter values you need are not available in the NTSMF data

Though your tamoxifen shopping girl than home unitedpharmacy supportteam very that. And late this methotrexate 20 mg week all with into, says and root green discharge after taking diflucan filing. Longer large job picking. I http://www.3wcircle.com/oursmy/adalat/ resist Amazon like a on http://www.scottstedman.com/cated/fake-prescription in out eat ordine levitra is stores Program 3/4 no prescription online pharmacy again. I collection. Cologne. For NEVER thick of toronto online drugs to usa sexybossinc.com the. Bottom isn’t flagyl forte don’t CVS product is didn’t real viagra for sale and one. The microbeads http://www.3wcircle.com/oursmy/largest-mail-order-companies/ I can the are. I.

collection file and not visible in System Monitor either. If you are still not able to collect the missing Objects and Counters after you have followed all the steps in this procedure, please contact Customer Support and tell us about your problem. Please attach the .smf data file and the <computername>.ntsmf.log file from the machine where you are experiencing the problem.

  1. Is the Counter specified for collection, but not available for collection on the machine?

An Event ID 604 Warning message in the Application Event log (or the <computername>.ntsmf.log file) documents performance Counters that were specified in the DCS Data Definition, but are not available for collection on the local machine. This happens because not all the Counters associated with a given performance Object are available for collection across all versions of the associated Performance Library DLL that is responsible for maintaining them. While the developers of the operating system base Counters, like Processor and System, are pretty good about maintaining upward compatibility between versions of their Perflib DLLs, not all developers of Perflib DLLs are as circumspect.

For instance, if you specify that you want to collect all the Counters in the Internet Information Services Global Object and you are running IIS version 5.0, you are likely to receive a Warning message similar to the following:

10/30/02-09:06:00 – Event ID: 604, Category: DCS, Severity: Warning
The following global counters were specified in the DCS but not found on the local machine and will be skipped.
Object, Internet Information Services Global (L2596, G4022)
Counter, Cache Size (L0, G4024)
Counter, Cache Used (L0, G4026)
Counter, Cached File Handles (L0, G4028)
Counter, Directory Listings (L0, G4030)
Counter, Objects (L0, G4032)
Counter, Cache Flushes (L0, G4034)
Counter, Cache Hits (L0, G4036)
Counter, Cache Misses (L0, G4038)
Counter, Cache Hits % (L0, G4040)
Counter, Measured Async I/O Bandwidth usage/ (L0, G4052)

These are Counters that used to be in the Internet Information Services Global Object, but were dropped in later versions of IIS.

This situation is not an error condition (which is why the Collection service only warns you about it), but you need to abandon any hope you may have of collecting those specific Counters on this machine.

  1. Is the Performance Library DLL associated with the missing data missing?

Sometimes the Performance Library DLL that is defined is simply missing on the local machine. When the Performance Sentry collection service attempts to load the Library module referenced in the HKLMSYSTEMCurrentControlSetServices<servicename>Performance key, the module is not found. In this event, you should see an Application Event log similar to the following:

11/05/02-17:48:08 – Event ID: 210, Category: Discovery, Severity: Warning
The Performance Library, “Perfctrs.dll”, for service “TCP/IP Protocol Driver” (Tcpip), failed to load.
The system error was “The specified module could not be found (126)”.
Performance data for this service will not be available.
The Event Viewer (source Perflib) may have more details

In this example, the perfctrs.dll module identified in the Library field of the /Services/Tcpip/Performance subkey was missing. When the collection service tried to load it, the Load operation failed, for the following reason: “The specified module could not be found.” When a problem like this occurs, using either the Extended Counter List applet or the Registry Editor, determine where the Library is supposed to be and verify that the Perflib DLL is, in fact, missing. If the Library field of the /Performance subkey points to a fully qualified filename, look for the module in the folder specified. If only the module name is referenced, then look for it in the %system32% folder in the Windows <root> directory.

Sometimes this occurs when the application that installed the Performance Library was removed, but the corresponding Performance subkey was not deleted when the uninstall procedure executed. In this case, it is usually safe to remove the Performance subkey manually using the Registry Editor. The Event ID 210 Warning message will disappear after that.

However, if you feel that the missing Performance Library DLL is a mistake, try to correct the problem. Sometimes uninstalling and re-installing the application will restore the Perflib. Alternatively, try to locate a working version of the Performance Library DLL on a different machine running the same or a similar level of software. Copy that Perflib DLL module to this machine and then restart the collection service to see if that solves the problem.

  1. Is the Performance Library DLL associated with the missing data defective?

When the collection service encounters a defective Perflib DLL, it generates Application Event log messages that help to document the data collection problem. Common problems that you might see reported include:

  1. a Perflib DLL that does not initialize successfully,

  2. a Perflib DLL that fails to return any Objects and Counters, and

  3. a Perflib DLL that returns zero values for all the Counter values that it reports.

Sometimes, the Perflib DLL has a bug which causes an unhandled Exception or other error condition that causes the collection thread calling the Module to terminate. Prior to terminating, the collection service (assuming you are running the “fat” version of the collector) will generate a Stack trace showing the precise status of the collection thread at the time the error occurred. This diagnostic trace information should be forwarded to the party responsible for the Perflib DLL that failed for resolution.

An example diagnostic trace message generated by an unhandled exception in a Perflib DLL is illustrated below:

image001

As a result of encountering a serious error condition related to calling a defective Performance Library DLL, the collection service will recover and continue to gather data from whatever Perflib DLLs that are functioning correctly for the duration of the collection cycle. While the collection service bypasses collecting data from the defective Perflib for the remainder of the collection cycle, it will automatically retry the module in the initialization phase at the beginning of the next collection cycle. Consequently, the Warning messages that document the problem are likely to recur regularly at the beginning of each collection cycle until you decide to investigate and resolve the problem.

Only the most serious Perflib DLL defects trigger a diagnostic trace message. You are much more likely to encounter less serious defects like the ones described below.

Sometimes the collection service is able to locate and load the Perflib DLL without problems, but cannot gather the performance data the Perflib was designed to collect. Consider that many Perflib DLLs associated with extended Counters are designed to gather data from inside servers application processes like sqlserver.exe, store.exe, and inetinfo.exe. A frequent cause of data collection problems is that the process that a Perflib DLL needs to acquire performance data from is not running. For example, if the sqlserver.exe process is shutdown, the sqlctr80.dll Perflib DLL designed to gather SQL Server statistics will report an error condition, which the collection thread will post to the Event log.

If sqlserver.exe stops running or is hung for some reason, failed attempts to gather data SQL performance data from the SQL Performance Library DLL (e.g., sqlctr80.dll) will generate Warning messages like the following for each SQL performance Object the collector has been instructed to collect:

11/05/02-22:31:00 – Event ID: 2200, Category: Collection, Severity: Warning
Object, SQLServer:General Statistics (L2346, G17300), failed to return data this interval

11/05/02-22:31:00 – Event ID: 2200, Category: Collection, Severity: Warning
Object, SQLServer:Databases (L2370, G17700), failed to return data this interval

11/05/02-22:31:00 – Event ID: 2200, Category: Collection, Severity: Warning
Object, SQLServer:SQL Statistics (L2470, G18300), failed to return data this interval

Errors can also arise when the process that the Perflib DLL must communicate with to gather performance data is simply unavailable. In this example, the w3ctrs.dll Performance Library DLL cannot access the Inetinfo Web server publishing service that is the source for the Web service performance data that it reports.

11/05/02-16:50:16 – Event ID: 1309, Category: PerfData, Severity: Warning
World Wide Web Publishing (Global): no objects were found in the performance data buffer

11/05/02-16:51:16 – Event ID: 96, Category: N/A, Severity: Warning
The following performance libraries failed to return data.
Data from objects from these libraries will be unavailable for this cycle.
World Wide Web Publishing (W3SVC), “w3ctrs.dll”

11/05/02-16:51:16 – Event ID: 2200, Category: Collection, Severity: Warning
The following objects were specified in the DCS but failed to return data.
These objects will be skipped this cycle.
Web Service (L0, G8300)

11/05/02-16:51:16 – Event ID: 2200, Category: Collection, Severity: Warning
Object, Web Service Web Service (L0, G8300), failed to return data this interval

To rectify this situation, you need to resolve the underlying problem that is preventing the process the Perflib DLL depends on from running.

, ,

Comments are closed.