Passing Azure pipeline parameters to SSIS package parameters

Question

Hi,

I am working on SSIS package which needs some input parameters to execute. I have placed package in Azure pipeline using "Execute SSIS package". In the portal, for package I have created SSIS parameters and for pipeline, I have created parameters and mapped both of them. But when executing, it is throwing following error :

"OperationErrorMessages": "2/12/2025 8:48:57 AM +00:00 : Parameter 'P1' cannot be found.\n",

Also attaching screenshots for better understanding.

Please suggest if I am missing any setup.

Thank You.

Package parameters.PNG

Pipeline parameter.PNG

Answer 1

Hello Learner,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you got an error "Parameter 'P1' cannot be found." while passing Azure pipeline parameters to SSIS package parameters.

For best solution to reduce an overhead:

1. Open SQL Server Data Tools (SSDT) and ensure the parameter P1 exists in the SSIS package parameters (.dtsx file). This will help to verify parameter in SSIS package.
2. Then, run the following SQL query to verify the parameter's existence in SSISDB: SELECT * FROM SSISDB.catalog.parameters WHERE name = 'P1'; If P1 does not exist, redeploy the SSIS package with the correct parameters.
3. In the ADF pipeline, navigate to the Execute SSIS Package activity, under the Settings tab, ensure that the parameter mapping is correct, and the names are identical (including case sensitivity). This will also help to check parameter mapping in ADF.
4. If the SSIS package expects parameters from an SSIS Environment, ensure the environment exists in SSISDB and is configured in the ADF activity.
5. Execute the SSIS package directly from SSMS using:

           EXEC SSISDB.catalog.execute_package  
           @folder_name = 'YourProjectFolder',  
           @project_name = 'YourProject',  
           @package_name = 'YourPackage.dtsx',  
           @reference_id = NULL,  
           @use32bitruntime = False,  
           @execution_id = NULL;  
   

   If the execution fails with the same error, the issue is likely within the SSIS package itself.

I hope this is helpful! Do not hesitate to let me know if you have any other questions.

---

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.