FIX: Error message when you schedule some SQL Server 2005 Integration Services packages to run as jobs: "Package <PackageName> has been cancelled" (922527)
The information in this article applies to:
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Workgroup
- Microsoft SQL Server 2005 Standard X64 Edition
- SQL Server 2005 Standard Edition for Itanium-based Systems
- Microsoft SQL Server 2005 Enterprise X64 Edition
- Microsoft SQL Server 2005 Enterprise Edition for Itanium Based Systems
BUG #: 971 (SQL Hotfix) Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. SUMMARYThis article describes the following about this hotfix release: - The issues that are fixed by the hotfix package
- The prerequisites for installing the hotfix package
- Whether you must restart the computer after you install the hotfix package
- Whether the hotfix package is replaced by any other hotfix package
- Whether you must make any registry changes
- The files that are contained in the hotfix package
SYMPTOMSConsider the following scenario. You schedule some Microsoft SQL Server 2005 Integration Services (SSIS) packages to run as jobs. You do this by using SQL Server Agent. When the jobs are running, you log on to the console session on the computer by using Terminal Services from a remote client computer. In this scenario, some of the jobs may fail when you log off from the console session. Additionally, you receive the following error message: Package <PackageName> has been cancelled. Note In this error message, the word "cancelled" is a misspelling for the word "canceled." If you examine the job history, you find the following message:The step was cancelled (stopped) as the result of a stop job request. Note In this message, the word "cancelled" is a misspelling for the word "canceled." CAUSEThis problem occurs because the dtexec command prompt utility is canceled when you log off from the console session.RESOLUTIONHotfix informationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2005 service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. PrerequisitesThere are no prerequisites for this hotfix. Restart informationYou do not have to restart the computer after you apply this hotfix. Registry informationYou do not have to change the registry. Hotfix file informationThis hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.SQL Server 2005 database engine |
| Logread.exe | 2005.90.1551.0 | 397,088 | 19-Jul-2006 | 16:40 | x86 | | Microsoft.sqlserver.replication.dll | 2005.90.1551.0 | 1,608,480 | 19-Jul-2006 | 16:36 | x86 | | Microsoft.sqlserver.smo.dll | 9.0.1551.0 | 1,559,328 | 19-Jul-2006 | 16:36 | x86 | | Microsoft.sqlserver.sqlenum.dll | 9.0.1551.0 | 895,776 | 19-Jul-2006 | 16:36 | x86 | | Msmdlocal.dll | 9.0.1551.0 | 15,626,528 | 19-Jul-2006 | 16:37 | x86 | | Msmdredir.dll | 9.0.1551.0 | 3,929,888 | 19-Jul-2006 | 16:37 | x86 | | Osql.exe | 2005.90.1551.0 | 51,488 | 19-Jul-2006 | 16:35 | x86 | | Replrec.dll | 2005.90.1551.0 | 781,088 | 19-Jul-2006 | 16:35 | x86 | | Sqlaccess.dll | 2005.90.1551.0 | 349,472 | 19-Jul-2006 | 16:40 | x86 | | Sqldiag.exe | 2005.90.1551.0 | 960,288 | 19-Jul-2006 | 16:36 | x86 | | Sqlservr.exe | 2005.90.1551.0 | 28,791,128 | 19-Jul-2006 | 16:37 | x86 |
SQL Server 2005 Integration Services |
| Dtepkg.dll | 2005.90.1551.0 | 74,016 | 19-Jul-2006 | 16:37 | x86 | | Dts.dll | 2005.90.1551.0 | 1,094,432 | 19-Jul-2006 | 16:36 | x86 | | Dtspipeline.dll | 2005.90.1551.0 | 600,352 | 19-Jul-2006 | 16:40 | x86 | | Microsoft.sqlserver.dtstransferprovider.dll | 9.0.1551.0 | 113,440 | 19-Jul-2006 | 16:37 | x86 | | Microsoft.sqlserver.msmqtask.dll | 9.0.1551.0 | 80,672 | 19-Jul-2006 | 16:37 | x86 | | Microsoft.sqlserver.msmqtask.xml | Not Applicable | 26,172 | 15-May-2006 | 11:34 | Not Applicable | | Microsoft.sqlserver.olapenum.dll | 9.0.1551.0 | 52,000 | 19-Jul-2006 | 16:35 | x86 | | Microsoft.sqlserver.smo.dll | 9.0.1551.0 | 1,559,328 | 19-Jul-2006 | 16:36 | x86 | | Microsoft.sqlserver.sqlenum.dll | 9.0.1551.0 | 895,776 | 19-Jul-2006 | 16:36 | x86 | | Microsoft.sqlserver.tabletransfergeneratortask.dll | 9.0.1551.0 | 43,808 | 19-Jul-2006 | 16:38 | x86 | | Msmdlocal.dll | 9.0.1551.0 | 15,626,528 | 19-Jul-2006 | 16:37 | x86 | | Msmdpp.dll | 9.0.1551.0 | 3,828,000 | 19-Jul-2006 | 16:37 | x86 | | Txbestmatch.dll | 2005.90.1551.0 | 430,368 | 19-Jul-2006 | 16:40 | x86 | Note To resolve this problem, you must install both hotfixes. First, install the hotfix for the SQL Server 2005 database engine. Then, install the hotfix for SQL Server 2005 Integration Services. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
| Modification Type: | Major | Last Reviewed: | 10/5/2006 |
|---|
| Keywords: | kbExpertiseAdvanced kbsql2005ssis kbtshoot kbfix kbQFE kbhotfixserver kbpubtypekc KB922527 kbAudDeveloper kbAudITPRO |
|---|
|