Bug #14264 Error Log: Performance Data
Submitted: 24 Oct 2005 16:37 Modified: 29 May 2013 11:23
Reporter: Richard de Courtney Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Severity:S3 (Non-critical)
Version:3.51.12 & 5.0.15 OS:Microsoft Windows (Windows 2003)
Assigned to: Bogdan Degtyariov CPU Architecture:Any

[24 Oct 2005 16:37] Richard de Courtney
Description:
Possibly due to overly tight security on our Windows 2003 server box, there are 3 errors that are logged in the Event log for the Windows MySQL ODBC driver.

ERROR MESSAGE 1
The description for Event ID ( 0 ) in Source ( ODBC ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Error in d:\srvrtm\enduser\databaseaccess\src\mdac\odbc\core\dm\perf.c(506), Access is denied.
: Failed to open HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ODBC\Performance.

ERROR MESSAGE 2
The Open Procedure for service "ODBC" in DLL "C:\WINDOWS\system32\ODBC32.DLL" failed. Performance data for this service will not be available. The Status code returned is the first DWORD in the attached data.

ERROR MESSAGE 3
The Open Procedure for service "WMServer" in DLL "C:\WINDOWS\system32\WMSPerf.dll" failed. Performance data for this service will not be available. The Status code returned is the first DWORD in the attached data.

All 3 errors occur at exactly the same second (and therefore are more than likely related). MySQL is the only ODBC connected app that is being used.

How to repeat:
Normal use
[24 Oct 2005 21:10] Peter Harvey
This does not appear to be a problem rooted in c/odbc (MyODBC) but rather something in your environment related to ODBC in general.
[29 May 2013 11:23] Bogdan Degtyariov
I'm closing this bug because I can not continue without feedback from the reporter. If you have new info, please reopen the report.