Please help someone from MSFT!I've just finished installing the Sep CTP on my laptop. I previously had the April CTP and June CTP. I followed the instructions for removing a previous installation of SQL 2005.Now, when I try to create an SSIS package, I get a message that says:TITLE: Microsoft Visual Studio------------------------------ The new connection manager could not be created. ------------------------------ADDITIONAL INFORMATION: The connection manager 'OLEDB' is not properly installed on this computer. (Microsoft.DataTransformationServices.Design) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.24&EvtSrc=Microsoft.DataTransformationServices.Design.SR&EvtID=ConnectionManagerNotInstalled&LinkId=20476 ------------------------------BUTTONS: OK------------------------------I had this issue when I installed the June CTP and could not resolve it, so I abandoned the installation and did development on my server. I thought it would get resolved the next time I installed a new version, but no luck.Any ideas?Thanks!

Hello Jason...I am expiriencing the same error. Have you found any solutions yet? Thanks,Error: TITLE: Microsoft Visual Studio------------------------------ The new connection manager could not be created. ------------------------------ADDITIONAL INFORMATION: The connection manager 'OLEDB' is not properly installed on this computer. (Microsoft.DataTransformationServices.Design) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.26&EvtSrc=Microsoft.DataTransformationServices.Design.SR&EvtID=ConnectionManagerNotInstalled&LinkId=20476 ------------------------------BUTTONS: OK------------------------------

This does look like a registration issue due to installation on a dirty machine. In the few instances we've seen this it has been easier to reset the OS on the box as harsh as that sounds. You can instead try to uninstall manually by machine sure the registry keys and directories left around by VS and SQL are cleaned up. I'm not aware of any comprehensive list that you could use for this, though... perhaps ask on the SQL and VS setup aliases. regards,ash

I have just discovered this while trying to create an OLEDB connection in BI Studio. I have deinstalled and reinstalled SSIS and client tools serveral times. I also wrote a simple test in vbscript to ensure that MDAC 2.81 was installed.What particular registeries are u talking about? To reset the OS would be drastic.

You can try to run:regsvr32 dtsconn.dll, for the start.

I'm having this error too and this machine (XP + latest updates) has only seen the RTM version of SQL 2005 (not good for RTM) ....Any ideas for a solution please?Reinstalling the OS is not a solution.

Did you try the suggestion?regsvr32 dtsconn.dllK

yes and it had not effect :(still looking for a solution.

Hey All, I am learning to create packages using SSIS for school. I tried to create a new OLEDB connection, but when I type in my usual login id and password for my local SQL Server and want to 'Test Connection' in the OLEDB connection manager, I get a message 'Test Connection failed because of an error in initializing provider. Could not load file or assembly 'System.EnterpriseServices.Wrapper.dll' or one of its dependencies. The system cannot find the file specified. ' Looks like the connection information provided by me is not being recognized, as the available DBs are also not being listed in the Connection Manager, to enable me to chose the one I want to connect to. I have no clue as to what I need to do??!!! I'd appreciate if someone can help me asap!! Thanks ahead!

I tried the above suggestion and it did not work. Over the weekend, I deinstalled SSIS and client components. Went to regedit and deleted all references to Visual Studio. Reinstalled and still the same problem.I can create and test a data source that is using the native client. When I try to create a connection in Studio using the data source, it fails again with the following error.===================================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. (a1)Any workaround would be welcome.My install experience--------------------I had to install Windows XP Professional SP2 prior to installing the CTP. I also had to deinstall OWC11 as it did not like the upgrade. The machine had SQL Server 2000 SP3a and Analysis Services 2000 SP3a.I upgraded a SQL2000 database and imported its dts packages that run in compatibility mode. Analysis Services 2000 could not be upgraded and I had to deinstall prior to installing Analysis Services 2005.

Another wild guess - please reboot the machine ;)If you still have the problem, could you please contact me via e-mail, I'll try to diagnose the problem. Remove "online." from the address in my user properties to get real address.It would be great if you could send me logs from C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Filesand content of HKEY_CLASSES_ROOT registry (I know it is big :) - but should compress well too).Also - what is your locale in Windows' Regional and Language Option?

Michael,Rebooted many times :(I have sent you the requested information.

Michael,I'm still having this problem as well. I've uninstalled all previous versions of SQL 2005, .NET Framework 2.0 and Visual Studio 2005. I then installed VS 2005 and SQL Server 2005. But this did not solve the problem. Is there a solution?

Jason,I'm still having problems .. I contacted Michale@microsoft but still no solution. It might be a good idea for you to email him like he sugests...If enough of us have this problem then they may look into the problem in more depth ...

I sent Michael the details he requested yesterday. I tried twice this morning with the RTM with no success. I have given my laptop to our IT guy who is clearing the hard disk and doing a fresh install of Win XP Pro SP2 plus base s/w.Fortunately, I have a desktop and can continue other work. I will still have to add all my dev tools to the laptop. Will keep you posted on progress.

I'm also getting this same problem (no matter what type of connection I try to add in the SSIS project).I was trying to follow the tutorial and create a Flat File connection, but none of the others seem to work either. I've uninstalled and re-installed all of SQL 2005 with no luck.

I don't have an answer from Microsoft so bug Michael @ microsoft

I eventually got my machine's hard disk wiped and installed with Win XP PRO SP2 and Office Pro 2003.When trying to install SQL 2005, it complained about OWC11. Uninstall OWC11 (that was installed with Office Pro) and then start full SQL Server 2005 RTM install. It was successful.I can now create OLEDB connections and have tested ETL of over 3 million rows from SQL Server 2000 table to SQL 2005 table. It was painful to have to clean your machine out over two days. I have now to install all my dev tools on the laptop.The short answer is, this is the way to go to get started if you have the above problem, unless someone knows better.Nilesh

I get a same message: 'Test Connection failed because of an error in initializing provider. Could not load file or assembly 'System.EnterpriseServices.Wrapper.dll' or one of its dependencies. The system cannot find the file specified. ' in Server Explorer of VS2005 RTM when I tried to create a new OLEDB connection.I use a small tool called Filemon (www.sysinternals.com) to capture the activity on my system.I found that the file "System.EnterpriseServices.Wrapper.dll" is missing in "c:\WINDOWS\WinSxS\x86_System.EnterpriseServices_b03f5f7f11d50a3a_2.0.0.0_x-ww_7d5f3790\" . Then I copy the '' from "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727" to "c:\WINDOWS\WinSxS\x86_System.EnterpriseServices_b03f5f7f11d50a3a_2.0.0.0_x-ww_7d5f3790\" and everything is ok But I don't know when and why the file "System.EnterpriseServices.Wrapper.dll" is missing ...

This worked for me..thanks!

This really sucks....Microsoft better come up with a better fix than this. I can't waste a day or two reinstalling...get real...

It seems like this problem could be caused by applications incorrectly setting up registry key permissions. I've found one such application documented in this KB: http://support.microsoft.com/default.aspx?scid=kb;en-us;300491 If you have Application Center, be sure to apply SP1. There could be other applications doing this though.

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. 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) { try { 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); } } } } }

Michael, Sure enough you had it right. I used the code you posted and located a problem key. It was a key for a Lexmark printer driver that was the problem. I granted read access to the key to Network Service, enabled and started the SSIS service and everything works fine now. I appreciate all your help. Thanks Jamin

Michael's solution also worked for me. In my registry the offending key was HKLM\Software\Classes\CLCSID\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{0cd637c0-0892-11d4-892f-00008364d903} Which also happened to be related to LEXDRVX.DLL (Lexmark printer driver?) Thanks again to Michael for solving this issue.

I ran Michael's code and got the same class - a lexmark printer driver. Now SSIS works after recycling the service. - ed

This resolved the problem on my rogue machine. The error key was{0cd637c0-0892-11d4-892f-00008364d903}, LEXDRVX.DLL, Lexmark driver.

Good post, however when I ran this program and there were no keys identified as problem on my machine, ie no exception message. I still get the "The connection manager could not be created" error as before for OLEDB, FLATFILE, ADO.NET, and so on.... any other suggestion would be greatly appriecated!

Minh H wrote: Good post, however when I ran this program and there were no keys identified as problem on my machine, ie no exception message. I still get the "The connection manager could not be created" error as before for OLEDB, FLATFILE, ADO.NET, and so on.... any other suggestion would be greatly appriecated! Make sure you run the program under new non-administrative account. Your regular user account usually has enough permissions to access these keys.

Yep, that did it. Key identified was the 'LEXDRV Shell Extension Handler'. The problem went away after granting read access to 'Users' group. Thank you much!

I get the same problem . I run the C# program, but no registry keys are found with no read permissions. There must be something else in my case. If you have any suggestions please let us know. Thanks a lot.

Sorry if you've already read it, but it looks like people sometimes miss this important part: Make sure you run the program under new non-administrative account. Your regular user account usually has enough permissions to access these keys.

Thank you again. You were right. I followed your advice as following : - I removed the account I executed the program from local administrators group. - I executedthe program again in the context of a non priviledged account. The program found one registry key , where the accound did not have read permissions. - I logged of, logged on with a local adminstrator account and gave read permissions to 'normal' local and domain users for that key. - I can now use Connection manager in creating all type of connections ( ole db , flat file, osv.) regardless the account I log on / launch Business Inteligence Studio. We may conclude that : Each attempt to make a connection by connection manager in thepreviously discussed scenariois not made in the context account of the logged user (with local admin. rigths or not ) and requires read access to all registry keys. I do not understand thelast part of it ( Why is it necessary to have read access to reg. key standingfor a prinder driver or the like ?)

Each attempt to make a connection by connection manager in thepreviously discussed scenariois not made in the context account of the logged user (with local admin. rigths or not ) and requires read access to all registry keys. I do not understand thelast part of it ( Why is it necessary to have read access to reg. key standingfor a prinder driver or the like ?) Actually, the connections are made under account of logged user. We enumerate which connection manager typesare installed under the account of SSIS Service - and it runs as low prileged Network Service account.Regarding the access to registry key: it is explained in http://support.microsoft.com/default.aspx?scid=kb;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.

I have also uninstalled SQL 2005 and other components installed. I then installed SQL 2005 but the problem remains. Solution is urgently needed. Oke

Extra wrote: I have also uninstalled SQL 2005 and other components installed. I then installed SQL 2005 but the problem remains. Solution is urgently needed. Oke Please read this thread - the problem is not caused by SQL Server installation, so reinstalling SQL Server would not help. The problem is causedby third party software (Lexmark printer driver for most users) that setups incorrect permissions on registry keys under HKEY_CLASSES_ROOT\CLSID. My posts above describe how one can find and fix the keys with incorrect permissions. Hope this helps,Michael.

I have the same problem, ran the c# code in a new account with no admin rights and got no registry keys. I am developing in a 32bit environment but deploying to a 64bits. Wonder if that makes a difference? suppose so... Complete details: I am building SSIS packages using BI Development Studio in a 32bits environment. After I finish the package I copy it and the manifest, using the filesystem, to a 64bit environment (Itanium 2, Windows 2003 Server Enterprise Edition SP1, SQL Server 2005 Enterprise Edition). When I try to load it to SQL Server or execute it on the 64bits server I receive the following error, I am signed in as Administrator: TITLE: SSIS Execution Properties ------------------------------ The package failed to load due to error 0xC0010014 "One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors.". This occurs when CPackage::LoadFromXML fails. There is little information around on the Internet, I found a c# code @ microsft.com (http://support.microsoft.com/default.aspx?scid=kb;en-us;913817) refering to some registry keys I may lack permissions on (and something about a lexmark printer driver!). I already compiled and executed the command line app, but found no "wrong" registry keys. Any ideas? Has anyone seen this before? Thanks in advance!

Piloto - It might be a completely different issue, depending on those "errors preceding", they usually explain what exactly went wrong.

Thanks for your reply Michael, unfortunately the error preceding is the same error :$ I tried deploying to a 32 bit server (my workstation, Win2003 Standard Edition SP1, SQL Server 2005 Developer Edition), the exact same package. And I was able to do it smoothly. Any ideas? Is there something I am doing wrong during the deployment or is that an issue in 32bits-64bits environment. One more thing, the packages where originally SQL Server 2K DTS, I imported them in BI Studio because we are doing a migration, then I adjusted the text files and OLEDB connections. Finally I tried to deploy them, and that's when the error appeared. Things I haven't done: rebooting. I haven't been able to do it, other people working on it.

A possible issue: during DTS 2000 -> SSIS migration, the migration wizard tries to replace all tasks with SSIS equivalent tasks. For some tasks, it can't do this(e.g. there is no corresponding task)so it uses 'Execute DTS 2000 Task' task to run old task from SSIS package. If this is the case, the package uses DTS 2000 runtime and since it is 32-bit only, it can only be runas 32-bit: either on 32-bit machine or on 64-bit machine using 32-bit DTEXEC in c:\Program Files (x86)\Microsoft Sql Server\... folder.

Michael, Thanks again for your reply. I am sorry, butI don't thinkthat may be the cause.The most 'sophisticated'task in all the set of DTSs is "Execute ActiveX Script". Most tasks are simple bulk inserts or Execute TSQL. And all the ActiveX Scripts are just creating FileSystemObject to rename and/or move files. I even created a new package from scratch. A simple TSQL query (select * from sys.objects). That's it. I copied it to the new server, tried to register it and got the same error. This is really frustrating! :)

After running the DTEXECUI.exe at the 64bit server i received the following error: TITLE: SSIS Execution Properties------------------------------ Error: 2006-03-07 14:14:26.90 Code: 0xC0010018 Source: Description: Error loading value "<DTS:Property xmlns:DTS="www.microsoft.com/SqlServer/Dts" DTS:Name="CreationDate" DTS:DataType="7">2006.03.06 17:23:00</DTS:Property>" from node "DTS:Property".End ErrorCould not load package "C:\BxI\SSIS\Package1.dtsx" because of error 0xC0010014.Description: The package failed to load due to error 0xC0010014 "One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors.". This occurs when CPackage::LoadFromXML fails.Source: i looked for the error code in google and msdn and only got this: http://msdn2.microsoft.com/en-us/library(d=robot)/ms345164.aspx 0xC0010018 DTS_E_PERSISTENCEERROR Error loading value "__" from node "__".

i can't believe the piece of crap ssis is!! apparently the error was caused because in the development environment (my workstation) my date regional settings are yyyy.mm.dd. the deployment server has settings like dd-mm-yyyy, i switched them to match my own settings and the package ran. I will make further tests, and if i am wrong i will gladly take back my first comment :) EDIT: It is official. You have to have the same regional settings on both servers. Why? Shouldn't there be a standard way for Windows to read/write XML values? Should something like the "creation date" key stop you from executing a package? I'm really confused.

Michael: I am having the same problem as others. I've built your code and run it as a non-administrative user. However, the only results I get are on opening keys"ProgId" and "Programmable". I can't open those reg keys in regedit either and cannot open permission on them. Get an "Error opening key". Could these be the culprits? Thanks,David Martin

Hi, actually there were quite a lot of various post in this thread that havelittle to do with original 'The connection manager 'OLEDB' is not properly installed on this computer' error that started the thread. So it would be better if you specify what error do you get and when.The keys look suspicious, the program enumerates keys underHKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSIDand the keys directly under this oneare usually GUIDs {nnn-...-nn},not strings like ProgID and Programmable directly under the CLSID.

Hi, I also faced the same problem.The troubling keys in my case were of Flash player 8. This is for information of others who might face the same problem

I just ran into this, two weeks after rebuilding my PC. The missing permissions werefor three registry keys for Macromedia Flash Player 8, whichhad recently loaded an automatic update.

I built then executed the above program after logging in as a user with a very low privileges(Not admin or power user). I found three keys. I provided the permissions. Now I dont have any keys being listed by the code you provided. I still get the error. Please help. Thanks. Naman Patel ( naman.patel@gmail.com)

Naman Patel wrote: I built then executed the above program after logging in as a user with a very low privileges(Not admin or power user). I found three keys. I provided the permissions. Now I dont have any keys being listed by the code you provided. I still get the error. Please help. Thanks. Naman Patel ( naman.patel@gmail.com) Have you restarted the computer after doing this? Also, make sure that Network Service account has access to these keys.

I did restart the computer. I added read permissions for the Network service to all the registry entries that were listed by that code snippet that you provided. After that Irebooted the laptop.But I still cant add a connection using any connection manager not even ADO.Net, OLE DB or any other type... I dont get what is the problem. Please let me know if you need any more information. Naman Patel ( naman.patel@gmail.com)

Michael Thanks very much for the code and solution it has worked on my machine as well as the others. Saved me from pulling my hair out again by assuming I had done something wrong when installing the products. Thanks again Chris

Thanks Michael, It was indeed the permission problem. For me it was Flash and Shockwave (running on a Media Center pc). Greetz, Gette

I solve reading this threadhttp://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=363237&SiteID=1&mode=1 HTH M.rkino

M.rkino wrote: I solve reading this threadhttp://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=363237&SiteID=1&mode=1 HTH M.rkino Well, uninstalling SSIS or disabling the SSIS service causes SSISobject modelto enumerate installed components itself (usually this is responsibility of the service, which caches this information to speed up package load). If you are running as admin user, this enumerationmay succeed, even when enumeration done by service fails (service runs as Network Service by default - non-admin). I would still recommend to find and eliminate the root cause of this problem, see my post above with a small program that may help you to find the key with bad security settings.

What do I use to compile this code? How do I know whether the keys have the correct permissions? I Built a package to copy data from a data source using an oledb connection, it worked for a while, then stopped with this error, I can't even open the package to edit/change it.

jeffnichuk wrote: What do I use to compile this code? How do I know whether the keys have the correct permissions? Use Visual Studio, or CSC.EXE (should be in C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 on any machine with SQL Server 2005). The keys that have the problem will be reported when you run this program using non-administrative account.This code is also included in KB article:http://support.microsoft.com/default.aspx?scid=kb;en-us;913817

very good !!!!!!!! thanks.

Solved the problem by installing the SQL05 sp1 from http://www.microsoft.com/downloads/details.aspx?familyid=cb6c71ea-d649-47ff-9176-e7cac58fd4bc&displaylang=en HTH

Hi Michael, I am also getting the error "Could not load file or assembly 'System.EnterpriseServices.Wrapper.dll' or one of its dependencies. The system cannot find the file specified.". I ran your code with a low privilege account and could not find any keys. The error occurs when my following code is executed: string sConnectionInfo = "File Name = \\My Documents\\information.udl"; OleDbConnection oldbCnInfo = new OleDbConnection(sConnectionInfo); oldbCnInfo.Open(); This piece of code worked fine for two years on multiple computers, but suddenly stopped working on an XP Pro machine. It is still working on other computers. The connection file "information.udl" works fine if open it and test the connection. Another problem that is probably related to this is that I cannot uninstallthe program that was installed from a place on network. I get the error " The feature you are trying to use is on a network resource that is unavailable". When I try to install a new version of this program, I get the same error. I updated this program more than 100 times by installing new versions without any problem untill yesterday. Any hint would be greatly appreciated. h

I am also getting the error "Could not load file or assembly 'System.EnterpriseServices.Wrapper.dll' or one of its dependencies. The system cannot find the file specified.". This error has nothing to do with the error that started this thread. Please don't reuse threads for discussing new unrelated issues. The most probable cause of your error is corrupted .NET framework installation, reinstall .NET 2.0.

Hi all,this is for Hipswich. I was also getting the error "Could not load file or assembly 'System.EnterpriseServices.Wrapper.dll' or one of its dependencies. The system cannot find the file specified.". I did find a solution that did work form me.It turned out, I think to be a corrupt Framework 2.0 file. How it became corrupt is beyond me but after a number of registry cleanings & Reinstalling windows and then finally doing a VS 2005 repair from the install disk the problem went away. Yeah!!! After doing the repair the files in the x86_System.EnterpriseServices_b03f5f7f11d50a3a_2.0.0.0_x-ww_7d5f3790 folder were updated and all seems fine now.I believe that one of the recent IE7 Updates or other updates are the cause of this problem. After getting the IE7 up date the tool bar in IE7 disappeared and I had to use Firefox. After the VS 2005 repair I am now using IE6 and all seems to work fine. It maybe that the one of updates I received was somehow corrupt. It would be nice to know if other have had this happen after updates as well. Hope that helps -GW

hi guys i did what you said in the previous posts and got back this registry {3DC0F2B5-CDD4-A326-9F26-BD835749B4CD} how do i find it on my machine now and set the permission on it cheers!

The key is HKEY_CLASSES_ROOT\CLSID\<guid-you-have-found>. Use menu Edit\Permissions, then Advanced, Check two boxes at the bottom of Permissions page: Include inheritable permissions and Replace ... on all descendands. Click OK, OK

I am also facing the same problem if I try to create anynew connection from connection manager. Plz Help.

I am also facing the same problem if I try to create anynew connection from connection manager. Have u found out any solution for this? Plz Help.

Somehow in my SQL 2005 setupsit often is unable to findSystem.EnterpriseServices.Wrapper.dll My work around is this: stop the MSDTC service. run the .net2 install. use the repair option. Rerun sql 2005 setup. Doing this has worked everytime. I have been able to reduce this problem greatly by doing the belowin my setups: stop the MSDTC service Install .net2 run sql 2005 setup.

Doesthis issue get fixed? What is solution if you do not mind sharing here?

worked like a charm. thanks michael. 1) logged in as testUser ran the prg. got the key. 2) logged back in to my acct. gave full access to the registry key. 3) restarted the ssis service 4) up and running SSIS

thanks alot microzt ..... it really help me .

Michael Entin - MSFT wrote: It seems like this problem could be caused by applications incorrectly setting up registry key permissions. I've found one such application documented in this KB: http://support.microsoft.com/default.aspx?scid=kb;en-us;300491 If you have Application Center, be sure to apply SP1. There could be other applications doing this though. Thanks Michael. I was also stucked up in the same problem.

I resolve this problem. Assign full permission to all key in registry. Regards. Isidro Santana.

For developers that are using OLEDB connections, try to add "OLE DB Services = -1" in your connection string. That works for me.

Quick fix that worked for me - Try changing you SQL Server Integration Services to log on as a Local Systems Account. Remember to stop the service first, change the account, then restart.

I too am stuck in this age old problem and i tried out the registry solution proposed. I have given the read permission to every possible user to the extent that the code you've given does not detect any access errors. However, i am still plagued with the initial state of been unable to establish either an OLEDB connection nor a Flatfile connection.

hi, i get the same error: Could not load file or assembly 'System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. I work on this computer with an account having administrative privileges and when i run your code it doesn't detect any 'bad' keys This is windows XP machine and i cannot create any new account (non-administrative) as this belongs to a domain Is there any way to run this code as non-administrator even though logged in with administrator account? I also tried copying the dll file to c:\WINDOWS\WinSxS\x86_System.EnterpriseServices_b03f5f7f11d50a3a_2.0.0.0_x-ww_7d5f3790\ as suggested by 'microzt' but this didn't work either ------- My fix: Even after installing .net Framework 2.0 SDK and 3.5 SDK i couldn't find mscorcfg.msc in the %Systemroot%\Microsoft.NET\Framework\ versionNumber\ But i found here (I am using Win XP with SP3) C:\WINDOWS\sp3\i386 C:\Program Files\Microsoft.NET\SDK\v2.0\Bin If i use the msc from the first one (sp3 folder) i get the error: MMC could not create the snap-in So i used the one from 2.0 SDk On opening the '.NET Framework 2.0 Configuration' console select 'My computer'on the left pane select 'Manage the Assembly Cache' in the right pane select 'Add an Assembly to the Assembly Cache' Browse to C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 and add System.EnterpriseServices.dll For me the assembly was added successfully but for my colleagues it failed with message: Cannot Add Assembly Unable to add the selected assembly. The assembly must have a strong name (name, version and public key). Close the '.NET Framework 2.0 Configuration' console If the assembly was added successfully then, you should see the following two files in the location C:\WINDOWS\WinSxS\x86_System.EnterpriseServices_b03f5f7f11d50a3a_2.0.0.0_x-ww_7d5f3790 System.EnterpriseServices.dll System.EnterpriseServices.Wrapper.dll Close the tool/program that was causing the issue and open again, it should work this time Thanks, -srinivas y.

Same issue (0xC0010014) for me except for my error being a FLATFILE connection manager issue - Almost immediately after installing some stupid Flash update. 2 days reinstalled everything - nothing worked ran the permissions code mentioned above and located a flash related key with insufficient permissions - gave it the users group permissions as stated but still could not load or run package stopped SSIS service - changed log on to "Local System" restarted and it worked. Maybe in concert with the permissions registry change. Thanks for the tips - where would we be without forums! Man what a pain!