Thursday, March 8, 2012
Can't debug proc after Sp2 on WinXP
After installation of SP2 on my WinXP Prof I can't run debug in SQL Query
Analyzer.
Unable to connect to debugger on "SERVER" (Error = 0x800706ba). Ensure that
client-side components, such as SQLDBREG.EXE, are installed and registered on
"MYXP". Debugging disabled for connection nn.
Server is Win 2003 and SQL 2000 with Sp3
Before Sp2 everything was OK.
Thanks for the help.
ML
Make sure you have followed all the steps in the help topic
in books online: Troubleshooting the Transact-SQL Debugger
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Wed, 27 Oct 2004 05:13:03 -0700, MarekL
<MarekL@.discussions.microsoft.com> wrote:
>Hi,
>After installation of SP2 on my WinXP Prof I can't run debug in SQL Query
>Analyzer.
>Unable to connect to debugger on "SERVER" (Error = 0x800706ba). Ensure that
>client-side components, such as SQLDBREG.EXE, are installed and registered on
>"MYXP". Debugging disabled for connection nn.
>Server is Win 2003 and SQL 2000 with Sp3
>Before Sp2 everything was OK.
>Thanks for the help.
>ML
Friday, February 10, 2012
Cant connect from WMI, but witout problems wiht the management Express utility
Been I have stopped a lot of days to begin to use the SQL Server 2005 Express edition, that's installs Visual Studio prof 2005.
I tried to inspect SQL Express installation via the windowsXP WMI tool "Microsoft Management Console" and their "Servers Microsoft SQL Server" branch, on is visible the SQL express instance recently installed named "<serverName>\SQLEXPRESS". But when I try to open connect, I obtain an error about "Can't establish connection ... reason:[SQL-DMO] ... verify your registry properties on SQL Server..." (more or less it's traslation to english)
I thought that is a login problem ... I make test over this think without results... Them I install the "SQL Server management studio express" utility, and YES I can connect and use the SQL server without problems ...
GRRRRR !!!! a lot of dais stoped ... but I don't understand why can't open the server instance on the "windows management console" because I really have permisions correctly, like see on the "SQL Server management studio express" utility.
I'm ussing windows integrated security.
I'm not using WinXP but Win2003, so not sure whether you can connect to SQL Express in MMC. But on my Win2003 server I can only create snap-in to SQL Server Configuration Manager or Serivices to manage the SQL Express Service--change the log-on account, start/stop it, ect. There is no 'connect' option.Anyways we can manage SQL Express very easily from?free Management Studio Express, not only start/stop/connect, but also with many useful database features such as backup/restore, executing queries, etc. So, why not install it?