error with ssis package in azure Failed get parameter info of parameter sql password

Al Levy 0 Reputation points
2025-02-19T17:33:28.59+00:00

There is an SSIS package running on a schedule in Azure.

The SQL database is also in Azure.

The SSIS package moves data from SQL to D365.

I am getting this error when the package starts to run:

error with ssis package in azure Failed get parameter info of parameter sql password.

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
11,271 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Chandra Boorla 8,795 Reputation points Microsoft Vendor
    2025-02-20T06:10:14.9433333+00:00

    Hi @Al Levy

    Thank you for posting your query!

    The error message you're seeing, "Failed get parameter info of parameter sql password," typically indicates an issue related to how SSIS (SQL Server Integration Services) is handling a parameter, specifically the SQL password, in your SSIS package. This could happen when SSIS is unable to retrieve or interpret the parameter used to connect to the SQL database.

    Here are some considerations that might help you:

    Parameter Configuration - Ensure that the SQL password parameter is correctly defined in your SSIS package, especially in the connection manager. Double-check that it's being passed properly throughout the package.

    Azure SSIS Runtime Configuration - Since the package is running in Azure, verify that your Azure-SSIS Integration Runtime has proper access to your SQL database. Sometimes, packages running in Azure may need different configurations for parameter passing or credential management compared to on-premises setups.

    Secure Password Handling - If the password is encrypted, ensure that it is being decrypted correctly within the package. If you're using sensitive data like passwords, consider leveraging Azure Key Vault to securely manage and retrieve the password during execution.

    Package Configuration - Check the parameters and variables used within your SSIS package to ensure everything is defined and passed correctly. This could help resolve any issues with parameter access.

    Reconfigure the Execute SSIS Package Activity - If the pipeline still fails: Delete and recreate the Execute SSIS Package activity to force a fresh pull of parameter metadata. Avoid manual overrides unless necessary.

    Logging - Review the SSIS logs for any additional details that may pinpoint where the failure occurs. This could help narrow down whether the issue is related to permissions, network access, or something else.

    By checking these aspects, you should be able to identify and resolve the problem.

    For more details, please refer the following links for useful insights:

    Disclaimer: This response contains a reference to a third-party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.

    I hope this information helps. Please do let us know if you have any further queries.


    If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.