December 2, 2005 at 5:24 am
Hi All,
When I tried to migrate my existing SQL Server 2000 DTS packages using Migration Wizard, I ran into the following error message.
Index was out of range.Must be non-negative and less than the size of the collection.
Parameter name: index[mscorlib]
Please help!
Thanks,
KP
December 5, 2005 at 8:00 am
This was removed by the editor as SPAM
December 9, 2005 at 11:34 am
Oh boy. Isn't DTS fun in SQL 2005? I'm getting the same error along with sporadic errors when I try to edit certain packages ("The DTS host failed to load or save the package properly"). Yes, I installed integration services and the DTS 2000 Designer components feature. Yet it will let me open and edit more complicated packages with the exact same type of components, connections, and logins.
So I'm stuck. I don't have a fail-safe way to edit the packages in SQL 2005, I can't open even the most basic package after importing it to SQL 2005 (yes, there are matching schema and logins in the 2005 DB). And, lastly, the migration wizard fails with the aforementioned error.
I wouldn't hold my breath for solutions. It sounds like DTS was an afterthought for SQL 2005. This will delay our implementation of SQL 2005.
December 17, 2005 at 6:07 am
In my case the problem was leading/trailing spaces in the DTS package name. Once I removed the leading/trailing spaces the migration worked fine.
January 25, 2006 at 1:47 pm
I have the exact same issue. Anyone come up with the solution yet? I had a thought that maybe its some sort of version issue, that if we open and save all the packages before upgrading it might help. The packages that I have noticed failing all seem to be older ones.
FisherDad
January 26, 2006 at 10:45 am
In addition to the above, I have also gotten the error "Cannot load MAPI interface layer for DTS. Please make sure that semmap90.dll is installed." Have worked through other solutions (see http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=189016&SiteID=1) to no avail.
However --- I have discovered that if you rename the DTS package (you can then immediately rename it back to what it was before) you can then successfully open it. The zoom setting is different and the contents are rearranged. I am not sure if this gets the package back to the point where it is functionally correct.
FisherDad
July 1, 2008 at 2:44 pm
Check the Product called DTS xChange ... its an advanced DTS to SSIS Migration wizard
The best feature of this wizard ... This wizard will Discover, Convert and Moniter your SSIS packages.
Homepage
http://www.dtsxchange.com/[/url]
Comparison with MS Wizard
http://dtsxchange.com/DTSxChange-vs-MSWizard.asp
Screenshots
July 1, 2008 at 8:45 pm
Have you run the Upgrade Advisor against your packages?
A worked around is by saving the packing to a file with a new name.
Also Check for Package Name with SPecial Characters.
Also a "_" in the Package Name can cause this...
Maninder
www.dbanation.com
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply