Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
|Source: SQL Server ODBC driver support|
The description (0) in source (SQL Server ODBC driver support error ) cannot be found. The local computer may not have the neccesary registry information or DLL files to display messages from a remote computer. The following information is part of the event: Unable to load SQL Server ODBC driver resource DLL. The application cannot continue.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is a DLL?
In my case to solve this problem, I had to replace additional files from the MDAC package (see Ionut Marin’s comment):
\Program Files\Common Files\System\Ole DB\sqloledb.dll
\Program Files\Common Files\System\Ole DB\sqloledb.rll.
From a newsgroup post: "We have had a couple reports of this error coming after Blaster was. Here is what you need to do to correct it.
Copy over the correct “sqlsrv32.rll” and “sqloledb.rll” from your MDAC version.
- Determine the currently installed MDAC version from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DataAccess\FullInstallVer.
- Download the appropriate version of the MDAC_Type.EXE from msdn.microsoft.com/data.
- Extract the mdac_typ.exe using the following command: “mdac_typ /c /t:c:\My_Extraction_folder”.
- Extract SQLSRV32.RLL from the SQLODBC.CAB.
- Backup the current copy of the SQLSRV32.RLL in the \<System32Dir>\ folder.
- Copy the extracted SQLSRV32.RLL into the \<System32Dir>\ folder".
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated