SSIS collapses in a screaming heap

I am having lots of fun tonight :) It's one of those nights when everything I touch breaks.

I started a brand new SSIS project and tried to add a new connection and got the following error:

The connection manager 'OLEDB' is not properly installed on this computer

Now, I am not using my laptop much during the day for SSIS development, but I know it was working a couple of weeks ago and I was pretty sure that I had not done anthing to much up my machine. I tried added any sort of task to the control flow and was met with similar errors about various things not being “properly installed on this computer“.

A few queries on google turned up the following post on the forums
http://forums.microsoft.com/MSDN/ShowPost.aspx?PageIndex=2&SiteID=1&PostID=179707&PageID=1

If you get the same sort of error I have put a compiled version of the code from the forum here

I order to run this utility you need to be running as a non-admin user. I created a user specially for this test to make sure that they did not have any other permissions.

When I ran the code I got the following output:

found 7668 keys
error while reading key {1171A62F-05D2-11D1-83FC-00A0C9089C5A}: Requested registry access is not allowed.
error while reading key {D27CDB6E-AE6D-11cf-96B8-444553540000}: Requested registry access is not allowed.
error while reading key {D27CDB70-AE6D-11cf-96B8-444553540000}: Requested registry access is not allowed.

The common thread here is that these registry keys all relate to the IE flash plugin, it appears that the flash plugin has updated itself and has omitted some permissions from some of the registry keys it created/altered. For some reason this throws SSIS for a loop. It seems a few other people had noted that Flash was one of the applications causing this issue, but it was not the only cause.

What I had to do then was to go into regedit and find these GUIDs under HKEY_CLASSES_ROOT\CLSID, right click on them and add read permissions to the Users group. There was also mention that the NETWORK SERVICE user might need to be granted read permission too, but that was not case on my PC.

After this has been done, reboot your PC and everything should be sweet again.

Print | posted on Wednesday, April 26, 2006 8:40 PM

Comments on this post

comments powered by Disqus