Re: Remote Debugging Problems w/ VS.net 2005 SP1

Thanks for the information. I will definitely look at this product and would
appreciate a copy of the documentation for review.

With this product, can stored procedures be interactiely debugged?


"The DBA" wrote:

Hi Parch,

I suggest you try the tool SQL Ultimate Debugger:
http://lakesidesql.com/downloads/PFD/1_0_2007_809/PFDebugger_Setup_08-09-2007.zip.
This tool is a post factum debugger and allows you to trace and
debug obejcts (SP's Triggers, FN's, etc.) that had been executed. It's
waaaay better than the T-SQL debugger in VS. Also, since this software has
not yet been officially realeased, I would not recommend (YET) to use it in
a production environment.

You can learn more about it here:
http://208.75.249.50/products/sql-ultimate-debugger/screenshots.html. If you
want a copy of its documentation. shoot me an email and i can send it to
you.

I hope that helps.





"parchk" <parchk@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F5E08E79-2BC6-4991-904A-A87465073520@xxxxxxxxxxxxxxxx
I have done through all the MSDN documentation and Googled everything I
could
on the errors I am receiving about installing and configuring remote
debugging. I believe it is communications related. This is the scenario:

The Visual Studio 2005 Remote Debugger service is started on the remote
database server that I want to debug SQL code on as Local System. I am a
member of the local administrators group on that server and a member of
the
sa role in SQL Server. I configured all the DCOM settings on both the
remote
server and my local workstation, which is running XP SP2, and opened the
firewall exceptions on my workstation.

When I attempt to step into a procedure, the message " Unable to start
T-SQL
Debugging. Could not attach to SQL Server process on 'daysqltest02'.
Remote
calls are not allowed for this process." displays. If I manually run the
Visual Studio Remote Debugging Monitor interactively on the remote server,
when I attempt to step into a procedure, an entry is displayed in the
monitor
that a connection from my workstation has been made and the following
message
is displayed "Unable to start T-SQL Debugging. Could not connect to
computer
'daysqltest02'. The Microsoft Visual Studio Remote Debugging Monitor on
the
remote computer does not have permission to connect to this computer.
Please
see Help for assistance."

Other people in my office on the same network or other networks can
successfully debug and there is not firewall between my workstation and
the
remote server so I know it is something with my security or communications
configuration. Any assistance would be much appreciated. Thanks in
advance.

Ken


.

Relevant Pages

  • Re: Remote Web Workplace Issue
    ... I had to "rebuild" my server. ... I could use RWW to a remote desktop on the ... I also am running a new workstation with Vista Ultimate that was never ... on that computer either but can use the remote desktop connection. ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Web Workplace Issue
    ... RWW and Remote Desktop ... I had to "rebuild" my server. ... I also am running a new workstation with Vista Ultimate that was never ... on that computer either but can use the remote desktop connection. ...
    (microsoft.public.windows.server.sbs)
  • *****UNABLE TO MAP THE DEBUG START PAGE URL TO A MACHINE NAME - HELL ON EARTH - PLEASE HELP!
    ... ASP.Net debugging through a firewall. ... Terminal Services to log into the remote server and debug locally. ... "Were the proper setup programs run to install ASP.NET or ATL Server ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Home Office wants a Remote Workstation to access resources
    ... > be remote controlled by the Location A workstation (via VPN/Remote Desktop ... >> to the Win2000 SBS server but it's not working out for us. ... >> domain (OLETANET) that is located at another home/residence. ...
    (microsoft.public.backoffice.smallbiz)
  • Re: Port Forward
    ... And no I don't want to remote into both at the same time. ... remote into one of the computer workstations OR the Server. ... I don't log into my server with my user account. ... Right now my client Remotes into a workstation with default port ...
    (microsoft.public.windows.server.sbs)