You are currently offline, waiting for your internet to reconnect

You cannot run or schedule various packages that require SQL Server 2000 Meta Data Services files after you upgrade to SQL Server 2005

Extended support for SQL Server 2005 ends on April 12, 2016

If you are still running SQL Server 2005 after April 12, 2016, you will no longer receive security updates and technical support. We recommend upgrading to SQL Server 2014 and Azure SQL Database to achieve breakthrough performance, maintain security and compliance, and optimize your data platform infrastructure. Learn more about the options for upgrading from SQL Server 2005 to a supported version here.

SYMPTOMS
Consider the following scenario. On a computer that is running Microsoft SQL Server 2005, you try to perform one of the following tasks:
  • You run or schedule a SQL Server 2000 Meta Data Services package.
  • You run or schedule a SQL Server 2000 Data Transformation Services (DTS) package that uses the Execute Package task to run a SQL Server 2000 Meta Data Services package.
  • You run or schedule a SQL Server 2005 Integration Services (SSIS) package that uses the Execute DTS 2000 Package task to run a SQL Server 2000 Meta Data Services package.
  • You run or schedule an SSIS package that uses the Execute DTS 2000 Package task to run a SQL Server 2000 DTS package that uses the Execute Package task to run a SQL Server 2000 Meta Data Services package.
When you try to perform task 1 or task 2, you receive the following error message:
The Microsoft Repository COM Server has not been registered on this system.
When you try to perform task 3 or task 4, you receive the following COMException exception error message:

SSIS package <package name> starting.
Error: 0x0 at <package name>: System.Runtime.InteropServices.COMException (0x80040427): Execution was canceled by user.
at DTS.PackageClass.Execute()
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.
Note The package name is a placeholder for the name of the package that you are trying to run.
CAUSE
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.
RESOLUTION
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:
  • Reinstall the SQL Server 2000 tools.
  • Copy and register the required files from a computer that has SQL Server 2000 installed, subject to appropriate licensing and distribution requirements, by following the instructions in the SQL Server 2000 Redist.txt file.
To extract DTS packages from SQL Server 2000 Meta Data Services, use the DTSRUN command (Dtsrun.exe) with the /!X option.

Note We recommend that you export the DTS packages in SQL Server 2000 Meta Data Services before you upgrade to SQL Server 2005.
MORE INFORMATION
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:
  1. Create a DTS package that uses an Execute Package task to execute the SQL Server 2000 Meta Data Services package.
  2. Save the DTS package that you have created to SQL Server 2000, or save the DTS package to a structured storage file.
  3. Execute the DTS package by using the SSIS Execute DTS 2000 Package task.
Notes
  • The following three files are required for basic SQL Server 2000 Meta Data Services functionality:
    • Repodbc.dll
    • Dbscan.dll
    • Reprc.rll


    You must register the Repodbc.dll file and the Dbscan.dll file by using the Regsvr32.exe utility.
  • Redistributable files
    The following SQL Server 2000 Meta Data Services files are redistributable:
    File nameDescription
    DScan.dllDatabase Scanner
    InsRepIM.dllInformation Model Installer
    InsRepIM.exeInformation Model Installer
    Msmdcxml.dllMDC XML Import/Export
    Repbr.dllRepository Browser
    Repbrui.dllREPBRUI.DLL
    Repodbc.dllMeta Data Services Repository Engine
    Reprc.rllRepository Engine Resource
    Msmdcxml.rllMDC XML Import/Export Resource
    Msrmirc.rllInformation Model Installer Resource
    Repbrui.rllRepository Browser UI Resource
    Repbrmdc.rllRepository Browser Icon Resource
    DB2.rdmModel Installation Script
    DBM.rdmModel Installation Script
    DTM.rdmModel Installation Script
    DTS.rdmModel Installation Script
    EQM.rdmModel Installation Script
    GEN.rdmModel Installation Script
    IFX.rdmModel Installation Script
    MDS.rdmModel Installation Script
    OCL.rdmModel Installation Script
    OLP.rdmModel Installation Script
    SIM.rdmModel Installation Script
    SQL.rdmModel Installation Script
    TFM.rdmModel Installation Script
    UML.rdmModel Installation Script
    UMX.rdmModel Installation Script
  • Installation notes for SQL Server 2000 Meta Data Services files
    Install the following SQL Server 2000 Meta Data Services files in the Program Files\Common Files\Microsoft Shared\Repository directory:
    • DBScan.dll
    • InsRepIM.dll
    • InsRepIM.exe
    • Msmdcxml.dll
    • Repbr.dll
    • Repbrui.dll
    • Repodbc.dll
    Install the following SQL Server 2000 Meta Data Services files in the Program Files\Common Files\Microsoft Shared\Repository\resources\1033 directory:
    • Reprc.rll
    • Msmdcxml.rll
    • Msrmirc.rll
    • Repbrui.rll
    • Repbrmdc.rll
    Install the following SQL Server 2000 Meta Data Services files in the Program Files\Common Files\Microsoft Shared\Repository\OIM\Install directory:
    • DB2.rdm
    • DBM.rdm
    • DTM.rdm
    • DTS.rdm
    • EQM.rdm
    • GEN.rdm
    • IFX.rdm
    • MDS.rdm
    • OCL.rdm
    • OLP.rdm
    • SIM.rdm
    • SQL.rdm
    • TFM.rdm
    • UML.rdm
    • UMX.rdm
    The following SQL Server 2000 Meta Data Services files must be registered by using the Regsvr32.exe utility:
    • DBScan.dll
    • InsRepIM.dll
    • Msmdcxml.dll
    • Repbr.dll
    • Rpbrui.dll
    • Repodbc.dll
REFERENCES
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.
Properties

Article ID: 904796 - Last Review: 03/11/2006 00:18:40 - Revision: 2.2

Microsoft SQL Server 2005 Developer Edition, Microsoft SQL Server 2005 Enterprise Edition, Microsoft SQL Server 2005 Express Edition, Microsoft SQL Server 2005 Standard Edition, Microsoft SQL Server 2005 Workgroup Edition

  • kbtshoot kberrmsg kbprb KB904796
Feedback