Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
You cannot run or schedule various packages that require SQL Server 2000 Meta Data Services files after you upgrade to SQL Server 2005
Article ID: 904796 - View products that this article applies to.
Consider the following scenario. On a computer that is running Microsoft SQL Server 2005, you try to perform one of the following tasks:
When you try to perform task 3 or task 4, you receive the following COMException exception error message:
The Microsoft Repository COM Server has not been registered on this system.
Note The package name is a placeholder for the name of the package that you are trying to run.
SSIS package <package name> starting.
Error: 0x0 at <package name>: System.Runtime.InteropServices.COMException (0x80040427): Execution was canceled by user.
at Microsoft.SqlServer.Dts.Tasks.Exec80PackageTask.Exec80PackageTask.ExecuteThread() Task failed: <package name> Warning: 0x80019002
at <package name>: The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. SSIS package <package name> finished: Failure.
The error message and COMException error message that are noted in the Symptoms section occur when SQL Server 2000 Meta Data Services files are not present.
To correct this problem, you must add or restore the SQL Server 2000 Meta Data Services files that are a component of SQL Server 2000. To do this, use one of the following methods:
Note We recommend that you export the DTS packages in SQL Server 2000 Meta Data Services before you upgrade to SQL Server 2005.
The Meta Data Services component of SQL Server 2000 does not exist in SQL Server 2005. If you uninstall SQL Server 2000 or if you upgrade the computer from the most recent version of SQL Server 2000 to SQL Server 2005, the files that support access to SQL Server 2000 Meta Data Services will be removed.
DTS Designer and the DTSRUN command continue to support DTS packages that were saved to SQL Server 2000 Meta Data Services as long as the SQL Server 2000 Meta Data Services files are present.
SSIS supports SQL Server 2000 Meta Data Services in the SQL Server 2005 Upgrade Advisor program and in the SQL Server 2005 Package Migration Wizard. If the SQL Server 2000 Meta Data Services files are present, the Upgrade Advisor and the Package Migration Wizard can, respectively, scan and migrate the DTS packages that were saved to SQL Server 2000 Meta Data Services. If the SQL Server 2000 Meta Data Services files are not present, the Upgrade Advisor and the Package Migration Wizard can, respectively, scan and migrate only those DTS packages that were saved to SQL Server 2000 or to structured storage files.
The SSIS Execute DTS 2000 Package task cannot execute DTS packages that have been saved to SQL Server 2000 Meta Data Services. To work around this issue, follow these steps:
For more information about the DTSRUN command, see the "Dtsrun Utility" topic in SQL Server 2000 Books Online.
For more information about SQL Server 2000 Meta Data Services files, see the Redist.txt file in SQL Server 2000. The Redist.txt file is located in the root folder of the SQL Server 2000 installation media file.
Article ID: 904796 - Last Review: March 11, 2006 - Revision: 2.2