Customization and Integration

[tconway]

I am getting this error on a DIM package that was working previously last week. Today I'm getting this error

"Could not load package [package name] because of error 0xC00160AC.  Description: No description found

Researching this appears to be related to version differneces between SQL 2005 and SQL 2008.  

But nothing I have tried is working.  

The data source is an Excel 2007 spreasheet.  

Has anyone run into this problem before

Thanks

Tim

[tconway]

This problem is now affecting all DIM  packages.  All fail and all have the same error.  

On MS Site I have found this....

http://support.microsoft.com/kb/2466166

Which lists the problem with 

Hresult: 0xC00160AC 
Integer: -1073651540 
Symbolic constant: DTS_E_CONNECTTOSERVERFAILED_NOTREGISTERED 

... and it describes the problem as this....

When you try to connect to SQL Server 2005 Integration Services (SSIS 2005) either using SQL Server Management Studio (SSMS) from SQL Server 2008 or SQL Server 2008 R2 you will experience one of the following error messages:

... and then it lists the error code I'm getting.  It is saying that we are attempting to combine SSIS 2005 with 2008.  Since the SSIS package is in reality created by Sage, is DIM possibly using 2005 components to create it the SSIS Package, and the packages are 2005, not 2008.  The package XML itself says it is 2008 (the XML above) so I'm not sure how that can be.  

Here is the XLM for the package showing it is SQL 2008

<?xml version="1.0"?><DTS:Executable xmlnsTS="www.microsoft.com/SqlServer/Dts" DTS:ExecutableType="SSIS.Package.2">

<DTSroperty DTS:Name="PackageFormatVersion">3</DTSroperty>

PackageFormatVersion 3 is SQL 2008, 2 would be 2005.  We are running 2008 and the package is 2008.  So the explanation of the error does not seem to be correct. 

.. or is it a .dll  that is incorrect, or a registry entry.  

Any ideas, my DIM is dead

Thanks

Tim 

[JohnHanrahan]

SSIS has historically had issues importing excel files.  If you switch them to CSV files it will likely work.  Of course you'll have to rebuild your imports....

J

[tconway]

True, except for one thing.  CSV Imports have a field limit of 100 char.  We found that out the hard way.  Excel doesn't have that limitation which is why we were switching.  

But what has now happened is past that, the DIM no longer works at all, CSV or Excel.  And all tailures are for the same error code which appears to be this difference between 2005 SSIS packages run in 2008 environment.  Yet, nothing seems to be 2005...

Still out of business. 

Thanks for your response, even moral support helps at this point. 

Tim

[JohnHanrahan]

Tim,

Did you switch to a named instance?  If so check this out:

http://msdn.microsoft.com/en-us/library/ms137789.aspx

John

[tconway]

No, Instance has remained the same, still looking..

T

[tconway]

I tested the config file, everything looks good.  Still not working.  

T

[tconway]

Solved at last!

Should anyone run into this problem, the resolution is to reinstall SSIS.  Not being the dba, I was not in a position to do this, but once done, all was well with DIM again.

Thanks for all the responses.  

Tim