Debug in QA Quit after SP2

Three development team members connect to SQL server 2000 on a 2003 server
within a windows domain. Used QA to debug stored procedures for several
months. Two of the three have installed XP SP2 on local machine. Now,
debug stops working on all three and receive the following message.
************************************************** *******
Server: Msg 504, Level 16, State 1, Procedure sp_sdidebug, Line 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger
on CSTSMAIN (Error = 0x80070005). Ensure that client-side components, such
as SQLDBREG.EXE, are installed and registered on CJAD502KR41. Debugging
disabled for connection 67.
************************************************** **********
Regards,
Michael Mach
no fix but check below
http://support.microsoft.com/default.aspx?kbid=839280
Andy.
"Michael Mach" <Michael.Mach@.cmaaccess.com> wrote in message
news:e8pTgahiEHA.1652@.TK2MSFTNGP09.phx.gbl...
> Three development team members connect to SQL server 2000 on a 2003 server
> within a windows domain. Used QA to debug stored procedures for several
> months. Two of the three have installed XP SP2 on local machine. Now,
> debug stops working on all three and receive the following message.
> ************************************************** *******
> Server: Msg 504, Level 16, State 1, Procedure sp_sdidebug, Line 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to
debugger
> on CSTSMAIN (Error = 0x80070005). Ensure that client-side components, such
> as SQLDBREG.EXE, are installed and registered on CJAD502KR41. Debugging
> disabled for connection 67.
> ************************************************** **********
>
> Regards,
> Michael Mach
>
|||This is a known issue with WinXP SP2. A fix for this has shipped in hotfix
944 on 6/2/04. It shipped in 32-bit only originally. Any later hotfix for
32-bit or 64-bit also includes this due to the cumulative nature of our
hotfixes.
We will be updating the following KB to reflect this:
BUG: SQL debugging does not work in Visual Studio .NET after you install
ID: 839280
To get a hotfix you need to contact PSS.
-Euan
Please reply only to the newsgroup so that others can benefit. When posting,
please state the version of SQL Server being used and the error number/exact
error message text received, if any.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael Mach" <Michael.Mach@.cmaaccess.com> wrote in message
news:e8pTgahiEHA.1652@.TK2MSFTNGP09.phx.gbl...
> Three development team members connect to SQL server 2000 on a 2003 server
> within a windows domain. Used QA to debug stored procedures for several
> months. Two of the three have installed XP SP2 on local machine. Now,
> debug stops working on all three and receive the following message.
> ************************************************** *******
> Server: Msg 504, Level 16, State 1, Procedure sp_sdidebug, Line 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to
debugger
> on CSTSMAIN (Error = 0x80070005). Ensure that client-side components, such
> as SQLDBREG.EXE, are installed and registered on CJAD502KR41. Debugging
> disabled for connection 67.
> ************************************************** **********
>
> Regards,
> Michael Mach
>
|||Euan,
I plead ignorant. How does one contact PSS?
--Scott
slbrook at hotmail.com
"Euan Garden[MS]" <euang@.online.microsoft.com> wrote in message
news:%23vw%230L8jEHA.704@.TK2MSFTNGP12.phx.gbl...
> This is a known issue with WinXP SP2. A fix for this has shipped in hotfix
> 944 on 6/2/04. It shipped in 32-bit only originally. Any later hotfix for
> 32-bit or 64-bit also includes this due to the cumulative nature of our
> hotfixes.
> We will be updating the following KB to reflect this:
> BUG: SQL debugging does not work in Visual Studio .NET after you install
> ID: 839280
> To get a hotfix you need to contact PSS.
> --
> -Euan
> Please reply only to the newsgroup so that others can benefit. When
> posting,
> please state the version of SQL Server being used and the error
> number/exact
> error message text received, if any.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Michael Mach" <Michael.Mach@.cmaaccess.com> wrote in message
> news:e8pTgahiEHA.1652@.TK2MSFTNGP09.phx.gbl...
> debugger
>
|||Nevermind.
I found it.
Thanks for the tip.
--scott
"Scott Brookhart" <slbrook@.hotmail.com> wrote in message
news:uJcqlPSkEHA.2848@.TK2MSFTNGP15.phx.gbl...
> Euan,
> I plead ignorant. How does one contact PSS?
> --Scott
> slbrook at hotmail.com
> "Euan Garden[MS]" <euang@.online.microsoft.com> wrote in message
> news:%23vw%230L8jEHA.704@.TK2MSFTNGP12.phx.gbl...
>