Database Management

Getting a Login Failed Error After Deploying a Package to a Server

Project/package protection levels can cause login or authentication errors after deployment from Visual Studio when passwords, logins, or keys are removed. The errors may seem to come from Task Factory, but they are actually from the project/package itself.

First published date

7/29/2021 4:10 PM

Last published date

2/10/2026 5:42 PM

Overview

The package execution in Visual Studio may succeed until it is deployed to a server. In the server execution results, you may see Task Factory component failures during the pre-execution phase, with Login Failed or Authentication Failure errors. This can be true for any Task Factory component that contains sensitive information, such as credentials, keys, etc.
  

Product section

Task Factory (TF)

Cause

This is usually due to the Protection Level of your Package. The DontSaveSensitive protection level prevents Visual Studio and Task Factory from saving sensitive data, including passwords. 

Resolution

Identify the Package Protection Level

  1. Left-click any empty area within the Control Flow, then press F4.
  2. F4 opens the Project Properties Tab.
  3. The ProtectionLevel property is in the Security section.
  4. If the value is DontSaveSensitive, then we have identified the problem.

1.jpg

Identify the Project Protection Level

  1. Right-click the Project Name within the Solution Explorer to open the Project Properties.
  2. Go to Common Properties >> Project.
  3. The ProtectionLevel property is in the Security section.
  4. If the value is DontSaveSensitive, then we have identified the problem.

Protection Levels

**Please note that we at SolarWinds cannot tell you what to set this property to, since this would be a Business Decision. Below are a few SSIS options. For additional details on SSIS Protection Levels, please refer to Microsoft's online documentation.

  

EncryptSensitiveWithPassword - This will allow you to create a password for the Project and package that can then be entered into the Server during the Deployment Process. This option would allow you to deploy to a server that is running jobs NOT using your profile. 

EncryptSensitiveWithUserKey - This option would work if your profile were running the deployed jobs. However, this option will not work if you are deploying to a server that uses a different profile to execute packages, because sensitive data is encrypted using your User Key or Profile.