Welcome to EMC Consulting Blogs

Here is something related - you would need to check the folder in which that reporting element is located, by searching for Microsoft.DataWarehouse*.dll

(I think the underlying cause is something to do with .Net 3.0 install, Maybe the installation of SQL2005 SP2, or maybe the order of install between VS2005 and SSIS, but whatever the reason, there is a registry issue.  

First, do make sure your SSIS service has appropriate login rights.

Also, navigate to the folder in which the indicated element is located, which you will see when you get the search results come back.

In that folder, run this command to re-register everything in there.:

for %i in (*.dll) do RegSvr32 -s %i

I had determined this was the issue from the detailed error message provided in the dialog, where it indicated the problem was the program Microsoft.VisualBasic.Vsa.Dt.get_extensibility....  blah blah, and another message saying "interface not registered".  Putting 2 and 2 together, I did a search for that dll, and registered everything in that folder and the other one.  I recognize a COM error when I see one :).

There are a few people on forums starting to post this issue, and there don't seem to be any responses, so tell everyone you know, because I'm sure it will be a common problem among SSIS developers who use scripting.  

Repeat as necessary for other dialogs.

Hello James,

When I did a search for Microsoft.DataWarehouse*.dll. I found a lot files in the search option. How do I execute/register

for %i in (*.dll) do RegSvr32 -s %i

I registered the dll as per your above Microsoft.Dat... But I am still getting the error "Cannot open editor"..

Any help would be appreciated

I have Sql Server 2005 SP2 and .NET 3.0 Installed..

We are still having this problem on 2 developers machines, none of the above hints have worked.  They have tried removing, reinstalling with and without service packs and they still get an error upon trying to design the script in a Script Task.

I am curious about the fact of "re-registering" these DLLs, as I didn't see many COM dll's in those folders at all.  Almost none of them can really be registered (run your command without the -s silent option).

FYI, this was in regards to the issue James brought up with "Microsoft.VisualBasic.Vsa.Dt.get_extensibility.... " and "interface not registered".

Any Update??  Fix??

Forums at Microsoft say that we need to get in touch with Product support to get the hot-fix. But that is an issue for developers, as we work in a controlled environment and any hot-fix has to go through a whole big corporate process to get it approved.

Any help would be appreciated.

I hope it works.