Perflib Stop Errors in Application Event Log

Run Regedt32
Go to hkey_local_machine\system\currentcontrolset\services\netbt\performance.
Delete the key

==========================================================================

Here is some information from CITRIX and Microsoft:

On a clean WinFrame Version 1.7 install, the PRFLBMSG.DLL file is missing.

The following event errors are logged each time PERFMON is loaded if Add to Chart is selected:

Event ID 1005 Event ID 1006 Event ID 1007 Event ID 2203 - This event is generated because the SPX II driver is not started by default; you can start the driver by double-clicking on Devices in Control Panel or disable the event logging for it.

These type of event messages are old news on Windows NT 3.1 - 4.0 and WinFrame. The following gives some background information and lists solutions to the problem.

The event IDs 1005, 1006, and 1007 occur when PERFMON loads the counters, it is reading the Performance Registry keys under each service. For example, these specific events for NetBT occur because this key exists: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Performance. If this key is removed, you no longer get these error messages.

These Registry keys are created during install by the various OEM.script files.

The file, OEMNXPTC.INF creates this specific key:

CreateRegKey $(NBTServiceKey) {"Performance",$(NoTitle),GenericClass}
"" $(MAXIMUM_ALLOWED) "" PerformanceKey Ifstr $(PerformanceKey)
!= $(KeyNull) Set NewValueList = {+ {Library,$(NoTitle),$(!REG_VT_SZ),"Perfctrs.dll"},+
{Open,$(NoTitle),$(!REG_VT_SZ),"OpenNbtPerformanceData"},+ {Collect,$(NoTitle),$(!REG_VT_SZ),"CollectNbtPerformanceData"},+
{Close,$(NoTitle),$(!REG_VT_SZ),"CloseNbtPerformanceData"},+
}

This paragraph in OEMNXPTC.INF is the same in both WinFrame 1.6 and 1.7, but I do not see the problem on my WinFrame 1.6 servers, nor do I see the key created in the Registry. Maybe the changes in WinFrame 1.7 allow this part of the set up script to execute properly and create the key, or it may have to do with what protocols are selected or the order in which they are installed. If the customer needs a workaround, remove the Performance key from the Registry to eliminate the error messages.

Note: Remember that the messages do not cause any adverse effect on the operating system.

=======================================================================

You can safely delete this entry.

Disclaimer: This information is supplied as is and is intended for information purposes only. Use this information at your own risk. The internet can often contain false or misleading information. While this is generally not the case with my personal documents I have to put this text here for legal purposes.