Failed to remove package protection with error 0x80131940

▲
2
▼

I'm trying to open a password protected package in SQL Server BIDs and I keep getting the following error message each time I pu in the correct password:

Failed to remove package protection with error 0x80131940 "(null)"

This occurs in the CPaqckage::LoadFromXML method.

Any Ideas?

sql-server
visual-studio
asked on Stack Overflow Jan 9, 2009 by (unknown user) • edited Oct 29, 2012 by SchmitzIT

3 Answers

▲
5
▼

I ran into the same problem and discovered that caps-lock was on. Typing the correct password with caps-lock on gives the error message "Failed to remove package protection with error 0x80131940 "(null)", whereas typing the wrong password gives the "The password you have entered is incorrect" message. Very misleading but simple to fix.

answered on Stack Overflow Oct 15, 2012 by Andy
▲
2
▼

I believe you thought you had the right password but that you really didn't.

I recently ran into this problem. I know you posted a long time ago but I could not find an answer when I ran into the same situation. Turns out I had the wrong password when I thought I had it right (I was not the one who created the package).

I had assumed that since some wrong passwords produced a wrong password error message that I must have had the right password with the one that did not produce a wrong password message - it turns out that different wrong passwords can return different error messages when opening a password encrypted SSIS package!

Very odd. At any rate, after finally getting a hold of the original developer, and getting the correct password, I was able to open the package just fine.

For what its worth I would never recommend encrypting the whole package with password, sensitive data maybe, but not the entire package.

answered on Stack Overflow Feb 29, 2012 by Gordo • edited Oct 29, 2012 by SchmitzIT
▲
1
▼

I just received the same error. My issue was targeting SQL Server 2017 instead of SQL Server 2016 (Project > Propertied > Configuration Properties > General > Deployment Target Version > TargetServerVersion)

answered on Stack Overflow Mar 25, 2020 by Joshua Rhodes

User contributions licensed under CC BY-SA 3.0