SSIS Script task debug does not work in SSDT - by Janos Berke

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 773678 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 12/6/2012 8:11:14 AM
Access Restriction Public


Script task debug does not work when VS2012 is installed before SSDT. I was able to repro the situation on 6 different machines.

User is a local admin, local activation of COM+ and Local Debug is enabled by default but eventlog reports problems: 

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
 and APPID 
 to the user %s SID (S-1-5-21-....) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Permission granted explicitly but the problem still persists.
Sign in to post a comment.
Posted by reefbreeze on 2/21/2013 at 5:26 PM
I have exactly the same issue - SSDT is not stopping at breakpoints in Script Tasks, and the same message is appearing in the event log. But VS2012 isn't installed, to the best of my knowledge (perhaps it is lurking there as part of Office 2013 preview installation???).