Re: SQL2k debugging broken/problem

Interesting. Well here is what I did yesterday after my post:
Used a win2k3 (without sp1) pc and tested debugging in QA and VS.Net against
a remote sql server and both worked. Installed sp1, which was the only
change I made, and debugging no longer worked. Next I removed sp1 from my
win2k3 pc and debugging against a remote sql server worked. Reinstalled sp1
and debugging no longer worked. So your implication would be that breaking
after sp1, and working after removing sp1 is just a coincidence?

Also, thanks for the references/links on the troubling shooting. I went
through ***all*** of that (spending about two weeks with our network and dba
staff) before focusing on sp1 as the potential source of the problem.



"Sophie Guo [MSFT]" <v-sguo@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:wXnoblzZFHA.388@xxxxxxxxxxxxxxxxxxxxxxxx
> Hello,
>
> I have tested the issue on a Windows server 2003 SP1 machine which has SQL
> server 2000 SP4 installed. I can use Transact-SQL Debugger to debug the
> stored procedure both on local SQL instance and remote instance. So I am
> unable to reproduce the issue.
>
> To narrow down the issue, I suggest that you check if you can reproduce
> the
> issue on a known working Windows server 2003 SP1 machine instead of a
> virtual PC.
>
> Also, you can follow the steps in the "Troubleshooting the Transact-SQL
> Debugger" topic in SQL Books Online(BOL) to troubleshoot the issue.
>
> Please refer to the following article:
>
> 280101 INF: Transact-SQL Debugger Limitations and Troubleshooting Tips for
> SQL
> http://support.microsoft.com/?id=280101
>
> This article describes the limitations of Transact-SQL Debugger in SQL
> Server 2000. This article also provides guidelines and directions to
> troubleshoot basic problems related to Transact-SQL Debugger. However,
> this is not an exhaustive list, and some problems may be specific to your
> environment.
>
> I hope the information is helpful.
>
> Sophie Guo
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
>
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
>
>
>




.

Relevant Pages

  • Re: Fresh Install Doesnt Work...Again!
    ... I will verify the sql service account and get back. ... MVP Windows Server System - SMS ... I am attempting to install SMS 2003 SP1 in a production ...
    (microsoft.public.sms.setup)
  • Re: sbs2003 sp1 questions
    ... well, I felt sharepoint which is heavily used should not be running the sbs box, so we moved to a server2003 box and talks to the sql server box. ... Sp1 for sbs2003 looks like a nice package but i have concerns as we already have deployed some if its components and don't have a typical bloated sbs2003 box, we have member servers take load of the sbs server etc. ...
    (microsoft.public.windows.server.sbs)
  • Re: sbs2003 sp1 questions
    ... But to me that's SQL cals/another Server OS/and the SQL license. ... Sp1 for sbs2003 looks like a nice package but i have concerns as we already have deployed some if its components and don't have a typical bloated sbs2003 box, we have member servers take load of the sbs server etc. ...
    (microsoft.public.windows.server.sbs)
  • RE: SP1 Error - MSDE SP4
    ... any *.out files with dates around the date/time you were installing the SBS ... SP1. ... | I have a Compaq Server with 3.8 GB of memory and twin Xeon processors ...
    (microsoft.public.windows.server.sbs)
  • Re: SP1 Error - MSDE SP4
    ... any *.out files with dates around the date/time you were installing the SBS ... SP1. ... Microsoft Small Business Server Support ...
    (microsoft.public.windows.server.sbs)