Friday, March 9, 2012

Please verify SQL Server is running and check your SQL

Hi,
The EU is trying to connect to the SQL Server database
through EM at her desk and she gets the following error
message.
"A connection could not be established to [SERVER NAME] -
specified driver could not be loaded due to system error
126 (SQL Server).
Please verify SQL Server is running and check your SQL
Servcer registration properties (by right-clicking on the
SERVER node) and try again."
These were the steps that were taken to ensure that the
above error could be resolved but invain......
1. Uninstalled SQL SERVER Enterprise Manager on Customers
PC and
reinstalled it - This did not help. Still getting the
following error
message.
(See attached file: sql server error.jpg)
2. Based on some of the information I tried searching for
sqlsrv32.dll file
location and were it was referencing in the registry and
found that it was
referencing to a drive mapping called S:\HR750
\crwxxx\sqlsrv32.dll - This
drive was formerly a people soft mapping which the
customer was using so, I
changed the registry settings to point to the dll file
which resided in
C:\WINNT\SYSTEM32 location, but that also did not help.
3. Made sure that all her patches and MDAC were proper and
fully patched.
Updated it but neither did this help.
4. Checked to see see whether Login Timeout could be
changed from default
of 4 to 8, but was unsuccessful int getting into that
options on the EM.
5. It looks more that some dll is corrupt which is causing
this problem on
the customres PC. I tried accessing ODBC Settings and
selected SQL Server
Driver and I get the following error message
"The setup routines for the SQL Server ODBC driver should
not be loaded due
to system error code 126"
and when I click on "OK", I get the next screen which has
a title
Driver's ConfigDSN, ConfigDriver, or Config Translator
failed
"Could not load the setup or translator library"
It sounds like a corrupt MDAC installation. Reinstalling the current
version of MDAC is a tricky proposition. If you have not upgraded to MDAC
2.8 on this machine you could do that and more than likely resolve this
problem.
Rand
This posting is provided "as is" with no warranties and confers no rights.

No comments:

Post a Comment