Home Dashboard Directory Help
Search

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


Status: 

Active


2
0
Sign in
to vote
Type: Bug
ID: 773678
Opened: 12/6/2012 8:11:14 AM
Access Restriction: Public
1
Workaround(s)
view
1
User(s) can reproduce this bug

Description

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
{FDC3723D-1588-4BA3-92D4-42C430735D7D}
and APPID
{83B33982-693D-4824-B42E-7196AE61BB05}
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.
Details
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???).
Sign in to post a workaround.
Posted by Janos Berke on 12/6/2012 at 8:14 AM
Do not install VS2012 and SSDT side by side or install VS2010 shell before VS2012.