Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Debugger failing after installing SP4 on server

Status
Not open for further replies.

gcoast

Programmer
Dec 17, 2003
39
US
Receiving the following message after installing SS2000 SP4 on one of my servers and trying to step thru the debugger in Query Analyzer from my PC. I can step thru the sp's if I logon to the server directly leading me to think the problem exists on my PC.

I can still step thru stored procedures on all other SS2000 SP3a servers from my PC.

Have already run - sp_sdidebug 'legacy_on' with no luck.

PC is running XP SP1
Server in running WIn 2003, SS2000 SP4 std edition.

I don't have SQLLE.DLL on my PC which could be the problem but I'm not sure where to get it or why SP4 would need it.


Any ideas? Thanks in advance.

GC


Unable to connect to debugger on <server name> (Error = 0x800401f3). Ensure that client-side components, such as SQLLE.DLL, are installed and registered on <client name>. Debugging disabled for connection 56.
 
As far as I know, SQLLE.DLL is used by Visual Studio. All files relevant for client-side debugging should be located in:

\Program Files\Common Files\Microsoft Shared\SQL Debugging

------
"There's a man... He's bald and wears a short-sleeved shirt, and somehow he's very important to me. I think his name is Homer."
(Jack O'Neill, Stargate)
[banghead]
 
I don't use Visual Studio so I'm not sure why I'm getting this message.

I have sqldbg.dll and sqldbreg.exe in the \Program Files\Common Files\Microsoft Shared\SQL Debugging directory already and they are both registered.

As I said in my original post, the SQL Debugger works fine on all other SQL Servers just not the one with SP4 installed?

GC
 
Anybody else got any ideas??

Thanks in advance,

GC
 
Nasty as this sounds, it could be a bug with the service pack itself. It has happened many many times before that MS breaks something in an SP that worked before the SP.

Go to the following WebSite:
I'm thinking SQL Server General is the newsgroup to check out, but this page will give you the list of the most current. Do a search on the threads. If you don't find anything, post it on MS's website. A member of their Dev Team sometimes watches the sites and they may be able to answer you.

Sorry, haven't installed SP4 myself yet.



Catadmin - MCDBA, MCSA
"If a person is Microsoft Certified, does that mean that Microsoft pays the bills for the funny white jackets that tie in the back???
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top