by ebarcza
2/25/2010 9:20:00 AM
When trying to debug a sproc using SQL Server debugging I received this error:
SQL Debugging: Unable to start T-SQL Debugging. Could not attach to SQL Server process
Executing the following solved the problem
sp_addsrvrolemember 'Domain\Name', 'sysadmin'.
If you're not part of a domain then the insert the machine name for domain; ServerName\username
by rbellantoni
2/24/2010 4:43:00 AM
If you have ever run into this problem you understand how frustrating it can be, one of the fixes is to go and download this SP and install it to fix it.
http://www.microsoft.com/downloads/details.aspx?familyid=8a166cac-758d-45c8-b637-dd7726e61367&displaylang=en
Another one we tried was to go to SQL Server pull down the rsclientprint.cab files and install them on the local machines (located in: Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer\bin) and delete the old RLL and dll files
Then we also tried to uninstall a few windows updates that installed killbits ActiveX Killbits (KB956391)
If anyone else has tried anything that worked let us know!
by ebarcza
2/3/2010 5:42:00 AM
32767
259f679e-00f3-4813-8d31-db74425fcd60|1|5.0
Tags: