September 25, 2003 at 8:41 am
I am unable to run the debugger from query analyzer and get the error:
ODBC: Msg 0, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot load the DLL mssdi98.dll, or one of the DLLs it references. Reason: 126(The specified module could not be found.).
I have both SQL Server 7 and SQL Server 2000 (MSDE) installed and both directories contain the DLL msidi98.dll. I am using the Query Analyzer for SQL Server 2000.
Any assistance in resolving this issue would be greatly appreciated as I am building rather complex T-SQL procedures that need to be debugged.
September 25, 2003 at 9:18 am
Check your sysetm variable 'PATH' to make sure SQL Server 2000 executiable path is in front of SQL Server 7.0 programs path.
September 25, 2003 at 12:23 pm
I checked the path and it may have been able to cause the problem, so I updated it and still got the same error. Then I logged onto a server with a clean SQL Server 2000 installation, connected to the server on the network using enterprise manager, and got exactly the same error when I tried to run the T-SQL debugger. The MS Knowledgebase doesn't seem to have any useful documentation covering this problem. Why not? If I have this problem on my only two computers, then wouldn't others have the same problem?
September 25, 2003 at 12:55 pm
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/trblsql/tr_servtools_5cfm.asp
http://support.microsoft.com/default.aspx?scid=kb;en-us;280101&Product=sql2k
Edited by - allen_cui on 09/25/2003 12:56:28 PM
September 26, 2003 at 1:36 am
there are 2 possible solutions for this problem.
1. Install SP# for SQL Server 2000.
or
2. Configure ur server using "server N/W Utility" by disableing all other protocols other than TCP/IP
hope this will solve ur problem
September 26, 2003 at 8:24 am
The problem is most likely, you are using the SQL 2000 Client tools the hit SQL 7 database. This will not work.
Curtis Smith
Application Dev. Mgr
DBA
Curtis Smith
SQL Server DBA
Well in worked in Theory ...
September 26, 2003 at 8:55 am
I've partially resolved this problem, or at least learned a little more about it. Yesterday the debugger worked when debugging a procedure on the server on my local computer. It still does not work when trying to debug procedures on a remote server. The remote systems are all SQL Server 2000 as is my Query Analyzer. I'm still working on it and will review the links Allen_Cui provided and check out service packs as recommended by pratapkrg. My copy of the Query Analyzer resides on a Windows 2000 platform which can only have MSDE or Personal SQL Server installed. I don't have permissions to disable protocols on the servers I connect.
SQL Server Connections:
1) Local (2 databases (MSDE/2000)
2) Midwest (1 large database (SQL Svr 2k on network)
3) Development Team (same office but SQL Svr 2k on network)
Steve King
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy