July 30, 2009 at 6:58 am
I am encountering this error when I attempt to use the VS2005 debugger for CLR code...
I did search this forum for my error text with no results, so I figured I woould post this up.
Environment:
1. "Visual Studio" Workstation (WinXP SP3, VS 2005 8.0.50727.42)
2. SQL Server named cmesqltest1 (Win Server 2003 SP1, MS Sql Server 2005 Developer Edition SP1)
I tried this on SQL 2K5 Enterprise Edition (64-bit) Service Pack 2 with the same results
No firewalls running on either machine
1. Firewall disabled on VS Workstation
2. Win Firewall not running on SQL Server because ICS Service is not running
Test Function:
I have a function called fnInternalSelect(), which is a C# object that returns a single field value from a simple select statement.
DataAccess = DataAccessKind.Read. It is deployed to SQL Server
Error:
(A). Unable to start T-SQL Debugging. Could not attach to SQL Server process on 'cmesqltest1'. Remote calls are not allowed for this process
The Tests...I generate this error when:
1. Trying to run test.sql (which calls fnInternalSelect()) in debug mode (F5). It executes properly if I Start without Debugging (Cntl-F5)
2. Right click on fnInternalSelect under data connections in Server Explorer
When trying to Debug | Attach to Process:
Transport = Default, Qualifier=browse to domain\sqlservertest generates:
(B). Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named 'cmesqltest1'.
The Visual Studio 2005 Remote Debugger service is unable to connnect to this computer. Please see help for assistance.
I have tried the above tests with msvsmon.exe running and not running on the SQL Server machine.
DOes not seem to alter the error message (A) at all.
I have two RPC services running on my SQL Server box.
Remote Procedure Call (RPC) and Remote Procedure Call (RPC) Locator. Both are running as NT AUTHORITY\NetworkService
As per msdn, I have my domain login account registered with SQL Server as a sysadmin via:
sp_addsrvrolemember 'domain\myusername', 'sysadmin'
Been scouring the internet for any ideas.
Not sure if this is a permissions thing.
Any thoughts would be appreciated.
thanks in advance, Scott
July 30, 2009 at 7:52 am
ohhh, my VS workstation logon is part of the domain administrators group
July 31, 2009 at 5:20 am
Anyone? :doze:
I have seen posts on other message boards regarding this error....unfortunately no resolution so far....
Any feedback is appreciated...
thanks, scott
July 31, 2009 at 7:44 pm
Sorry, Scott... I've got nothing for you on this. My response will serve to "bump" your question again and your question gives me yet another reason to avoid CLR's.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 3, 2009 at 5:36 am
Jeff Moden (7/31/2009)
Sorry, Scott... I've got nothing for you on this. My response will serve to "bump" your question again and your question gives me yet another reason to avoid CLR's.
Thanks for the response/bump Jeff...
CLR avoidance seems like an interesting concept!
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy