This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1BFBB.874A0810
Content-Type: text/plain;
	charset="iso-8859-1"

there are a couple things I can think of right of the top of my head.  Mind
you I am not famialiar with TSQL, but these are the first things I try
anytime I have a problem after an upgrade of the OS.
 
1.  Check to ensure the Computer name has not changed, if it has and can not
be changd back to the original name then check the software on both the
Local machine and the server to ensure it is not defaulted anywhere to the
old name, if not update it.
 
2.  Search the registery for the old computer name?  You should not find any
instance of it, if you do that might be your problem.
 
3.  Check to ensure the software is not defualted using an old IP address.
If you don't know your old IP address then just ensure the software is not
using IP addresses and if it is, then ensure it is using the current IP
address of the machine.
 
4.  If you know the DLL, OCX or EXE name that can not be found, then search
in the registry for the name of the file.  Locate it on disk.  From time to
time you'll notice that you had an drive mapping to another server and the
program was installed or using components off that server.  Re-map the
server if this is the case.
 
5.  Reinstall the software ensrung you are connected to all required
servers.
 
6.  check with the software manufacture for upgrades and patches or contact
thier support and ask about compatiblity with the new OS.
 
As a last resort you could find a replacement software.  I realize this is
scarey and can result in some major overhead, however it can also have the
reward of have more tools, features and better user interfaces which in the
end can simplify the process or speed up the end result as well.  This is a
last resort however.  
 
I hope this helps, or at least points you in the right direction.
 
Thanks
 
Crane
 
 

-----Original Message-----
From: Francis Kioko [mailto:kioko@s...]
Sent: Tuesday, February 26, 2002 3:39 PM
Subject: TSQL Debugger


Hi Guys
 
I have recently upgraded my development machine to Win2k Server from WinNT4
Server (after a clean install) but now I have a problem running TSQL
Debugger a tool I have become heavily dependent on for debugging Stored
procedures the error message it returns is 
 
"The query could not be debugged due to a problem coordinating events with
the server. Check the server and client log to find the exact cause, fix the
problem and try again"
 
When I go to the event log of the development machine the error there is 
 
Event Type: Error
Event Source: MSSQLServer
Event Category: Server 
Event ID: 17055
Date:  27/02/2002
Time:  12:33:10 AM
User:  DAM\ndehi
Computer: MAINSERVER
Description:
17750 :
Cannot load the DLL SDI, or one of the DLLs it references. Reason: 126(The
specified module could not be found.).
 
Data:
0000: 56 45 00 00 00 00 00 00   VE......
0008: 0b 00 00 00 4d 00 41 00   ....M.A.
0010: 49 00 4e 00 53 00 45 00   I.N.S.E.
0018: 52 00 56 00 45 00 52 00   R.V.E.R.
0020: 00 00 0c 00 00 00 42 00   ......B.
0028: 69 00 6d 00 61 00 73 00   i.m.a.s.
0030: 4d 00 61 00 73 00 74 00   M.a.s.t.
0038: 65 00 72 00 00 00         e.r...  
 
At this point I get stuck. 
 
The development machine is running on a NT 4 domain and the SQL Server is on
a the development machine.
 
Can someone please help
 
Regards
 
Kioko