0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)

0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)

• vai23

  This has something to do with not being able to determine the sql server name... not sure why.
  
  Doesn't localhost work anymore
  
  I've tried creating aliases, combinations of localhost and 127.0.0.1. Checked firewall settings. I even reinstalled SQL 2005 hoping that would solve it (no luck). I'm sure I've set something up wrong, but have no idea what that could be.
  
  Very frustrating.
  
  

• kushals

  Have you allowed remote connections for TCP in the Surface Area Config tool Check the network library as well.
  
  

• John Melville

  
  Remote connections are enabled for tcp/ip, and the network library is definitely working in the surface scan config (queries to the database definitely work).
  
  I don't see a remote connection setting for Intergration services... should there be one
  
  I see Integration services under the SURFACE AREA CONFIGURATION FOR SERVICES AND CONNECTIONS, but I don't see Integration services when I click on SURFACE AREA CONFIGURATION FOR FEATURES... Is that supposed to be there
  
  I'm not a dba, and I'm a real newbie to sql2005, although I've administered several sql 7 and sql 2000 servers over the years.
  
  Anybody got any notes on registering the server, so it can see itself
  
  Maybe its a closed port Is there a specific port for Integration services
  
  Thanks
  
  
  
  
  
  
  
  
  
  
  
  
  
  

• Dans.

  This didnt work for me ;(

  I am trying to create SSIS package (Bulk Insert), when i try to set Destination Connection, it failed and gives me the same error.

  Any luck to others

  
  

• Aravinda

  I was able to get rid of this error by disconnecting my object explorer connection and reconnecting.
  

• VC_Mike

  Uninstalling and reinstalling the tools fixed it for me.
  
  

• DaveV

  I seem to be having the same problem as well. I'm supprised it's not fixed by now.
  
  
  

• MarkD84

  Hi....

  read this kb...

  http://support.microsoft.com/kb/918222/en-us

  Make sure you are installing the hotfix in the right order.

  Regards

  
  
  

• daviangel

  Here's the error message when trying to run a Maintenance plan: (all I do is right click Maintenance plan under Management, and choose 'New maintenance plan':
  
  This makes it a real pain to schedule backup jobs. I've put my workaround at the bottom.
  
  
  ===================================
  
  Exception has been thrown by the target of an invocation. (mscorlib)
  
  ------------------------------
  Program Location:
  
  at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck)
  at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache)
  at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache)
  at System.Activator.CreateInstance(Type type, Boolean nonPublic)
  at Microsoft.SqlServer.Management.DatabaseMaintenance.MaintDesignerMenuHandler.Invoke()
  
  ===================================
  
  Creating an instance of the COM component with CLSID {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} from the IClassFactory failed due to the following error: c001f011. (Microsoft.SqlServer.ManagedDTS)
  
  ------------------------------
  Program Location:
  
  at Microsoft.SqlServer.Dts.Runtime.Package..ctor()
  
  ===================================
  
  Creating an instance of the COM component with CLSID {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} from the IClassFactory failed due to the following error: c001f011. (Microsoft.SqlServer.ManagedDTS)
  
  ------------------------------
  Program Location:
  
  at Microsoft.SqlServer.Dts.Runtime.Package..ctor()
  
  ____________________________________
  
  WORKAROUND:
  
  Right click the database that you want to back up, and choose TASKS-BACKUP.
  Set up the Backup job the way you want it. Once you are ready, click the down arrow next to the script icon (scroll of paper) and choose SCRIPT ACTION TO JOB. This will bring up the new job. Set up the schedule and save. It seems to work, but if you try to click on the EDIT button in STEPS on the Job Properties, the same error as above appears.
  
  
  
  
  

• BillDude

  do i need to install this hotfix even if I am already using SP2

  
  

• nightwish

  We're running the same setup (Win03 64 / SQL 64) - only clustered. I'm seeing the same annoying error. I can't edit backup scripts. I can't even create them using SQL Mgmt Studio.

  We recently implimented a third-party backup tool and it works perfectly - which solves the above issue. It compresses and encryptes what we backup so its a better choice for us anyway. Still, we always want to tweek scripts and it would be helpful if we could do it in Mgmt Studio.

  The above fix is helpful. Using SCRIPT ACTION TO JOB, we're able to make necessary edits. Still, I'd love to see a fix vs a workaround.

  
  

• Antonio Galvan

  I figured out a work-around for the export to flat file problem.
  
  First register your sql server in SQL 2000, it won't let you put it in the EM, but you can register the server alias.
  
  From the SQL 2000 EM, right click any database, and choose export.
  
  If you click on the down arrow on server, you should be able to choose your SQL2005 box you registered, and make sure to connect as OLE DB PROVIDER FOR SQL SERVER.
  
  Set the login info, then next choose the export output like normal.
  
  The only thing left is to make sure to save the DTS job on the local server (the 2000sql box, not the 2005sql box).
  
  The question is why can sql 2000 see the sql 2005 box, but sql 2005 can't see itself....
  
  
  
  
  
  
  
  
  
  
  
• 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)