You receive an "Error loading" error message when you try to run an SQL Server 2005 Integration Services package in SQL Server 2005 (904800)
The information in this article applies to:
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Express Edition
- Microsoft SQL Server 2005 Standard Edition
SYMPTOMSIn
Microsoft SQL Server 2005, when you try to run an SQL Server 2005
Integration Services (SSIS) package from inside Microsoft SQL Server 2005
Business Intelligence Studio or by using the SQL Server 2005 Execute Package
Utility (Dtexec.exe) command-line tool, you receive the following error
message: Error loading PackageName: Failed to decrypt
protected XML node "PackagePassword" with error 0x8009000B "Key not valid for
use in specified state." You may not be authorized to access this
information. This error occurs when there is a cryptographic error. Verify that
the correct key is available. Note The PackageName placeholder is a placeholder for the name of the SSIS package that you are trying to run. This
behavior occurs when you try to run the SSIS package by using a different computer or a different user account than the computer and user account that were used to create the SSIS package. CAUSEThis
behavior occurs if the value of the ProtectionLevel property in the SSIS package is set to provide the maximum amount of protection for the Password property in the SSIS package. By default, the value of the ProtectionLevel property is set to EncryptSensitiveWithUserKey. The EncryptSensitiveWithUserKey value encrypts all the properties of the SSIS package that
are considered sensitive, such as the Password property. When the same user account and the same computer that
were used to create the SSIS package are used to run the SSIS package, the
SSIS package automatically decrypts, and no error message is generated.
However, when a different user account or a different computer is used to run
the SSIS package, the EncryptSensitiveWithUserKey value of the ProtectionLevel property is engaged, and the Password property of the SSIS package remains encrypted. When this occurs,
an error message is generated.RESOLUTIONTo
resolve this behavior, change the value of the ProtectionLevel property in the SSIS package.REFERENCES
For more information about a similar problem, click the following article number to view the article in the Microsoft Knowledge Base:
918760
An SSIS package does not run when you call the SSIS package from a SQL Server Agent job step
Modification Type: | Minor | Last Reviewed: | 5/10/2006 |
---|
Keywords: | kbtshoot kbprb KB904800 kbAudITPRO |
---|
|