Wednesday, January 19, 2022

The connection type "AzureStorage" specified for connection manager "SSIS Connection Manager for Azure Storage" is not recognized as a valid connection manager type

 I was trying to upload CSV files to Azure using SSIS blob upload task 

received many errors


1. The connection type "AzureStorage" specified for connection manager "SSIS Connection Manager for Azure Storage" is not recognized as a valid connection manager type


2.Executed as user: FPSSI\sa_SQLSvcAdmin. Microsoft (R) SQL Server Execute Package Utility  Version 13.0.5026.0 for 64-bit  Copyright (C) 2016 Microsoft. All rights reserved.    Started:  1:34:04 PM  Error: 2022-01-19 13:34:05.29     Code: 0xC0016016     Source: Copy2Azure      Description: Failed to decrypt protected XML node "AccountKey" 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.  End Error  Error: 2022-01-19 13:34:05.37     Code: 0x00000000     Source: Copy2Azure Connection manager "SSIS Connection Manager for Azure Storage" (SSIS Connection Manager for Azure Storage)     Description: Property "AccountKey" is not specified.  End Error  Error: 2022-01-19 13:34:05.37     Code: 0xC001401D     Source: Copy2Azure      Description: Connection "SSIS Connection Manager for Azure Storage" failed validation.  End Error  Error: 2022-01-19 13:34:05.39     Code: 0x00000000     Source: Copy2Azure Connection manager "SSIS Connection Manager for Azure Storage" (SSIS Connection Manager for Azure Storage)     Description: Property "AccountKey" is not specified.  End Error  Error: 2022-01-19 13:34:05.39     Code: 0x00000000     Source: Copy2Azure Connection manager "SSIS Connection Manager for Azure Storage" (SSIS Connection Manager for Azure Storage)     Description: Property "AccountKey" is not specified.  End Error  DTExec: The package execution returned DTSER_FAILURE (1).  Started:  1:34:04 PM  Finished: 1:34:05 PM  Elapsed:  0.5 seconds.  The package execution failed.  The step failed.

issue was:

  • SQL SERVER 2016
  • VS is 2017  
  • Installed Azure SSIS Feature pack 2017 

solution was:

  • SQL SERVER 2016
  • VS is 2017 but saved package as SSDT 2016 and modified the package with password
  • Azure SSIS Feature pack 2016 we have both 64 and 32 bit on dev server (uninstall 2017)


put password in command line
script out and see if its there or not, GUI not visible 

Option "OFF" is not valid. The command line parameters are invalid.The step failed SQL Agent job error while running package with password

 Option "Off" is not valid. The command-line parameters are invalid.The step failed

SQL Agent job error while running package with password 


make sure you did not remove any space while adding /DECRYPT Password

at edit command line manually.


I removed some space and got the error, but got fixed after re doing it with out any space 

Monday, January 3, 2022

failed to start project exception deserializing the package "The process cannot access the file because it is being used by another process."

Exception deserializing the package 

 "The process cannot access the file because it is being used by another process."

 

TITLE: Microsoft Visual Studio

------------------------------

Failed to start project

------------------------------

 

While running SSIS package i got the error “The process cannot access the file ‘*.ispac’ because it is being used by another process”.

 

The solution?/Fix:

1. Go to Task Manager

2. Details Tab.

3. Locate the process “DtsDebugHost.exe“.

4. Kill this process. There might be multiple instances of this process. Kill all of them.

5. Reexecute SSIS package

https://blog.sqlauthority.com/2009/06/27/sql-server-fix-error-17892-logon-failed-for-login-due-to-trigger-execution-changed-database-context...