Data Transformation Services (DTS)

"Could not create component categories manager" Or "Could not create an instance of the DTS package"

This can happen after some additional software has been installed, and DLLs required by DTS have been overwritten. The main culprit is Comcat.dll (winnt\system32). Version 4.71 is required for DTS to function correctly. For a quick fix copy Comcat.dll from your SQL 7 CD-ROM, and register it as described below. If this does not work then start working your way through the suggestions below.

• (Re-)Apply SP1 or SP2
• (Re-)Install Internet Explorer 5
• Copy Comcat.dll from the SQL 7 CD-ROM to \winnt\system32, replacing the existing version.
• Re-register comcat.dll [Regsvr32 \winnt\system32\comcat.dll]
• Re-register the DTS DLLs
  • Regsvr32 \mssql7\binn\axscphst.dll
  • Regsvr32 \mssql7\binn\dtsffile.dll
  • Regsvr32 \mssql7\binn\dtspkg.dll
  • Regsvr32 \mssql7\binn\dtspump.dll
  • Regsvr32 \mssql7\binn\dtsui.dll

"DTS WIZARD ERROR: CoCreateInstance - Class not Registered"

This is another case of DLLs having been overwritten. Quick fix is to try re-registering DTSPkg.dll first.

• (Re-)Apply SP1 or SP2
• (Re-)Install Internet Explorer 5
• Re-Register DTSPkg.dll [Regsvr32 \mssql7\binn\dtspkg.dll]

"The parameter is incorrect" Or "Invalid class string" Or "The system cannot find the file specified"

This is caused by incompatibilities between the DTS Package format of SQL Server 7 RTM or SQL Server 7 Service Pack 1 and SQL Server 7 Service Pack 2 or SQL Server 2000.

You cannot edit or run a package on a pre-SP2 machine once a SP2 or SQL 2000 machine has saved it, unless you use a package password. The standard format used to save packages has been changed after SP1. The encrypted package format however, is the same, so using a package password will bypass the issue. Alternatively open a version of the package prior to the SP2/2000 edit, and only save changes using RTM or SP1 tools.

The "The system cannot find the file specified" message is specific to SQL 2000, for which the standard format has changed again from that of SQL 7.0 SP2. The use of a package password will overcome this issue as well.

A quick summary of compatibility for reading and executing packages is outlined below:

In summary, ensure all SQL 7.0 Servers/Clients have SP2 applied, and use package passwords if you have SQL 2000 mixed in as well.

"Invalid class string" is not strictly a SQL Server error in DTS. Essentially it means in cannot find the CLSID for a required object when reading the package. This error can also occur when loading a package that contains a CustomTask which has not been registered on the current machine.

"The license for the installation of Microsoft SQL Server on your source and destination connections does not permit the use DTS to transform data. Please refer to your license agreement for more information."

This message will appear when trying to transfer data between SQL Server Desktop and a Standard, Enterprise or SBS Server. From SQL Server Books Online, "SQL Server Editions" :