Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 378
  • Last Modified:

SSIS deployment validation

I asked a question in July because I was getting deployment errors. "Error: Failed to decrypt an encrypted XML node because the password was not specified or not correct. Package will attempt to load without the encrypted information." The package in the previous question ran fine after this error, because I learned later the package wasn't even using the connection string generating the error.

http://www.experts-exchange.com/Database/MS-SQL-Server/Q_28477521.html

Now I have another package that is using the connection strings in Connection Manager. This one generates the same error and will not work on the server.

If I uncheck the box "Validate package after installation", I can deploy to the server fine and everything seems to run fine. InsallationWizard.jpg
My question is: what exactly is this validating in the package and can I safely uncheck it during deployment. All of my searches show me how to use it, but I can't seem to find out why.

Thanks,
Jerry
0
Jerry Miller
Asked:
Jerry Miller
  • 2
1 Solution
 
ValentinoVBI ConsultantCommented:
The following page contains some info on that validation option: Step 2: Running the Package Installation Wizard

As you can read in 18, the checkbox causes the Package Validation page to appear.  On that page you'll get warnings about possible configuration issues.

For your error, what is the ProtectionLevel property set to?  That's a property on package level.  Best is to set this to DontSaveSensitive and then use package configuration to configure things like configuration strings.

Some reading material:
Understanding Integration Services Package Configurations
Package Configurations
0
 
Jerry MillerAuthor Commented:
I have the package set to EncryptSensitiveWithPassword as I do not have access on the SQL Server to save configuration files. It is difficult enough to get the DBA to allow SSIS, trying to get additional access is next to impossible.

If the checkbox only checks for possible configuration issues, I should be able to leave that checkbox unchecked as the package is validated during the build. I am simply unclear on what is being checked during validation and have not found any good documentation on the subject.

My best guess on why I get the error is that Visual Studio is encrypting with a different cipher strength or type than the SQL Server is using to decrypt during deployment. Which is odd because the package works fine once deployed.
0
 
Jerry MillerAuthor Commented:
Since the package is being validated on build I know that the connection manager information is valid, so I am leaving the validation turned off during deployment. The main concern with leaving this feature off is that I would miss a true issue before I move it to the server. Hopefully the build validation catches the same issues. I would love to use the configuration file approach, but it is not possible in my current environment.
0

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now