Geeks With Blogs
Shape Without Form He who has a why to live for can bear almost any how

or how Flash broke SQL

A few weeks ago, my SQL Server 2005 installation  lost the flat file data source option and could not import or export no matter the format.

An error was thrown up.

The connection manager could not be created from one or more data sources. (Microsoft Visual Studio)

The connection type "OLEDB" specified for connection manager "{F3C4B394-E196-4AFD-A2F6-37AD9AFCA94D}" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.


After local admins reinstalled, and uninstalled and reinstalled sql server 2005 again to no avail.

I fiinaly came across a thread on MSDN: listed below:

After compiling and running the code below.  I identified 3 keys that as a lowly user, I could not access.

After gaining admin access I set the 3 keys to read for everyone, rebooted and was good to go.

Get this the keys belonged to Flash. 

And sure enough, I recall that while having the admin here install the active X control needed for MS virtual labs,

(as a lowley user, I could not install it by myself.) the virtual labs  prompted for flash to be installed and it was.

How flash can break it I am not sure, for most people it appears to be a Lexmark driver that does this.

from the post

Regarding the access to registry key: it is explained in;en-us;300491. To enumerate connection managers, we are using standard COM API EnumClassesOfCategories (connection managers register under specific category) and the incorrect permissions of that printer driver (or AppCenter in KB) break this API.

From the post, link at end:

There might be other programs causing this. One way to identify registy keys with incorrect permissions is to compile the program below and run it under low priveleged user account (create a temporary user account, add it only to Users group, run the program). The permissions of the keys identified by the program should be changed to grant Users read access.

Compile in C# console app and run under lowest security setting.

using System;

using Microsoft.Win32;

namespace CheckClsidPerm


class Program


static void Main(string[] args)


RegistryKey clsid = Registry.LocalMachine.OpenSubKey(@"Software\Classes\CLSID");

string[] clsids = clsid.GetSubKeyNames();

Console.WriteLine("found {0} keys", clsids.Length);

foreach (string s in clsids)




using (RegistryKey clsidKey = clsid.OpenSubKey(s))


using (RegistryKey ic = clsidKey.OpenSubKey("Implemented Categories"))





catch (Exception e)


Console.WriteLine("error while reading key {0}: {1}", s, e.Message);






} see the post at

24 Dec 2005, 3:58 AM UTC 24 Dec 2005, 3:58 AM UTC

Posted on Friday, April 14, 2006 8:45 AM | Back to top

Comments on this post: SQL Server 2005 Unable to import or export - a fix!

# re: SQL Server 2005 Unable to import or export - a fix!
Requesting Gravatar...
it's gr8, thanks a lot for your post ,It works finally
Left by Senthil on Jul 12, 2006 4:01 AM

# re: SQL Server 2005 Unable to import or export - a fix!
Requesting Gravatar...
i found this key 7B8E9164-324D-4A2E-A46D-0165FB2000EC after giving read access to every one and restarting system it again showing the message "the connection type "oledb" specified for connection manager"DestinationConnectionOledb" is not recognised as a valid connection manager..

tell me what to do ..its urgent
Left by Varinder Singh on Oct 30, 2010 12:35 PM

Your comment:
 (will show your gravatar)

Copyright © [C.B.W] | Powered by: