SQL Server Performance Forum – Threads Archive
SSIS package errors
Greetings. We recently installed a new production server and converted our old production server to our development server. It retained all of the SQL Server infrastructure but the server name changed. We created the database from a backup. The server name change was done by our DBA. This is running SQL Server 2005, SP1.<br /><br />When we went on to the server to execute an SSIS package we began receiving errors that looked like they were coming out of connection managers, the first one being out of a log file connection. Part of that error is "Error loading value "<DTS:LogProvider xmlns<img src=’/community/emoticons/emotion-2.gif’ alt=’
‘ />TS="www.microsoft.com/SqlServer/Dts">". I then went to a package that I knew didn’t have logging implemented in it and the package opened fine. However, when I went to add a logging connection, I got an error "The new connection manager could not be created. (Microsoft Visual Studio)" and "Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)". Next I went to the data flow task that was already there (it had the red circle and X) and tried to open it. This error was "The designer could not be initialized. (Microsoft.DataTransformationServices.Design)". I then abandoned that package and tried to create a new one and got similar errors.<br /><br />I realized after all this that another of our DBAs had done a new installation of Analysis Services on this server. She had mistakenly implemented it with SP2 but she had to deinstall and reinstall with SP1. <br /><br />I’ve been doing research on this but the closest suggestion I’ve found is to run SSIS as a Local service, but my DBA hasn’t jumped on that idea (and admittedly, i don’t really know what that means). <br /><br />At this point, I’ve got a development server that’s useless. Anyone seen this before? Any ideas? Do we need to reinstall Integration Services? <br /><br />Thanks for any help anyone can offer.<br /><br />-Helen
What was the account used to run previously on that server? http://support.microsoft.com/kb/918633
http://support.microsoft.com/kb/918644
KBA references fyi for more information. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
It uses Network Service. Thanks!
Have you checked the KBA references above>?
Is it possible to recreate that SSIS package? Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.
I was just looking at that first link. I can’t create any new packages. Everything I try gives me connection errors. That first link references using whatever login account was used prior to the installation of SP1 but we’ve been on SP1 since it first came out. Is it possible something happened when AS was loaded with SP2 and reloaded with SP1? The logon account matches what we are running in production and that runs fine. And these are the same packages we run in production (since this was our original production server). I see that second link has a hotfix mentioned. I’ll pass that along to my DBA also. Thanks for the links!
I have the same problem and just cant seem to get it resolved. I have the update to sp2 applied and that didnt fix it as I had hoped. I didnt start having the problem until I applied SP2. However, I have many other machines with SP2 and the update and dont have any issues. Any help would be appreciated.
]]>