Package Migration Wizard error -- Index was out of range

I am unable to migrate any DTS packages, from a SQL Server 2000 package, from a structured storage file, or from a DTS package imported into SQL2005 (Developer Edition, 32 bit). Running the Package Migration Wizard, every time I get to the List Package screen, i get the error below. I haven't found any other mention of this so far. Anyone else seen this error or have suggestions
"Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index (mscorlib)

------------------------------
Program Location:

   at System.Collections.ArrayList.get_Item(Int32 index)
   at WizardUI.ListPackages.UniquePackagewithCurrentVersion(PackageInfoCollection m_pInfoCol)
   at WizardUI.ListPackages.OnEnterPage(EventArgs e)
   at Microsoft.SqlServer.Management.UI.WizardPage.RaiseEnterPage()
   at Microsoft.SqlServer.Management.UI.WizardForm.NextPage(WizardPage nextPage)
   at Microsoft.SqlServer.Management.UI.WizardForm.Next_Click(Object sender, EventArgs e)"

Answer this question

Package Migration Wizard error -- Index was out of range

ShreyaPatel
I did, and have recieved notices that many of my DTS package names contain illegal characters and many are too complex to be migrated, but the particular DTS package I am trying to migrate does not fall into either of these categories.
NHJ
Do all the DTS packages have to be completely cleaned up in order to migrate just one of them

This dosen't seem to fix the problem on my packages. I rename then to a single word, no spaces, underscores, etc and still recieve this error.
Michael Entin
Brian,

The unsupported characters in package names is a known issue, and the Upgrade Advisor cautions you about this in advance (if it is installed and run).

To troubleshoot the other problem effectively, I've been reminded that we need not just a package, but steps to reliably reproduce the problem. So you can send the package to douglasl at microsoft.com, but please include the steps that you followed in creating, modifying, importing, and/or attempting to migrate it leading up to the error, whether you were using the SQL 2000 or 2005 tools, and so forth.

Thanks!

-Doug
Christopher Hansen
I also get the error. I corrected all the package names that were identified by the Upgrade Advisor, then I reran the Upgrade Advisor to make sure it was clean, but I still get the error. I have a SQL2000 default instance and a SQL2005 instance. I downloaded and installed the SQLServer2005_DTS.msi tool. I open SMSS and connect to the default instance (Sql Server 8.0). I navigate to the Management > Legacy > Data Transformation Services folder and I see my SQL2000 DTS packages there. I right click a package and then > Migrate to start the wizard. I enter (local) as Source Location and Destination Location = the SQL2005 instance and when I click 'Next' I get the error.
dDude
Hi - ran into this problem and believe that I have found what is causing this error and a workaround.

I am using the SQL Server 2005 Developer MSDN production download and was having difficulty migrating DTS packages, receiving the exact error described above. I discovered that this was related to the name of the DTS package - it seems there are some characters (including the underscore "_") which cause the migration wizard to fail.

Rename all of your DTS packages with simple unambiguous names and I think you will get past this error.

Hope this helps!
alexxio
Yes, that was the problem, a trailing space. That fixed it for me. To find the offending name, I queried sysdtspackages for a name with a leading or trailing space.
Michael Vu
This happens regardless o fhe naming. I have renamed , saved to a different server with no underscores or ampersands in the DTS package names, etc. Same result every time.
ademar
Doug, I can supply you with a DTS package that produces this message.

Also, from what I can tell a DTS package with periods &/or understand (and perhaps other characters) in its name will produce this. I have worked around this by saving the packing to a file with a new name. However I can also produce DTS files that produce this error as well.

Just send me an email if I can be of help.
kail7
We notice that several users have reported this same error message while using the Package Migration Wizard. I am unable to reproduce the error when trying to import packages with an underscore n the package name, whether from MSDB or from structured storage files.

Can you describe for us any circumstances that reliably reproduce this error message, so that we can look into fixing anything that may need to be fixed Thanks,

-Doug
SiliconMage
Have you run the Upgrade Advisor against your packages
ive
Sir,

I don't know the answer to your question. I notice that one of the previous respondents queried sysdtspackages for any and all packages whose names had a leading or trailing space. If that doesn't help, please consider whether you would be willing to email us the package for troubleshooting purposes.

-Doug
JK302
Several forum users have reported the following error message when attempting to migrate a DTS package:

TITLE: Microsoft SQL Server
------------------------------
This wizard will close because it encountered the following error:
...
------------------------------
ADDITIONAL INFORMATION:
Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index (mscorlib)
...

One cause of this error, which can easily be reproduced, is a space before or (more likely) after the name of the package.

Unfortunately this problem is not currently detected by Upgrade Advisor when it scans package names for invalid characters.

-Doug
Robson Hermes
Note that Upgrade Advisor does not catch the "leading or trailing space" issue.

Are you trying to migrate this package individually, without migrating any others at the same time, and you still get "the index is out of range" This message has been reported in multiple threads in this forum, and the issue so far has always been one of characters in the package name.

-Doug
akberali
This issue is happening when trying to migrate a single package by itself.

I do not see any leading or trailing spaces in the package name. Do I need to verify that in all of the historical records in the sysdtspackages table for that package
Package Migration Wizard error -- Index was out of range

Answer this question