Azure DevOps deploy pipeline SSIS Catalog Configuration task fails with a missing file error

Question

Azure DevOps deploy pipeline SSIS Catalog Configuration task fails with a missing file error

Julian Hicks 20

I have built a deployment pipeline in Azure DevOps that deploys an SSIS project to a SQL Server 2019 instance using an Azure Pipelines agent running on the same server. The pipeline has two tasks:

Deploy the SSIS project using the SSIS Deploy task type
Configure the project catalog using the SSIS Catalog Configuration task type
The first step works without issue.

The second task fails when it attempts to update the first system parameter contained in the inline JSON file.

The configure SSIS Catalog task is failing with the following error:

System.IO.FileNotFoundException:

Looking on the deployment server I can see the missing dll in the tasks folder structure under the Agent service C:..._tasks\SSISCatalog...\0.5.15\ps_modules\Microsoft.SqlServer.IntegrationServices.Commands.Cmdlets\

The product version of the batch parser dll on the server is 15.0.1000.16

The version of SQL server is 15.0.4236.7

Error logs on the task show:

##[error][Parameter: [ContainerName].[ParameterName]] Failed to update the parameter '[ContainerName].[ParameterName]': Operation 'Alter' on object 'ProjectInfo[@Name='ProjectName']' failed during execution..

Any help to resolve this issue would be appreciated

Suresh Chikkam 2,135 Reputation points Microsoft External Staff Moderator

2025-03-07T09:14:27.0666667+00:00

Hello @Julian Hicks ,

Following up to see if the answer was helpful. If this answers your query, do click Accept Answer and Yes, if you have any further query do let us know.
Suresh Chikkam 2,135 Reputation points Microsoft External Staff Moderator

2025-03-10T01:36:47.1133333+00:00

Hi @Julian Hicks ,

Following up to see if the answer was helpful. If this answers your query, do click Accept Answer and Yes, if you have any further query do let us know.

1 answer

Your answer

Suresh Chikkam 2,135 Reputation points Microsoft External Staff Moderator

2025-03-07T09:14:27.0666667+00:00

Hello @Julian Hicks ,

Following up to see if the answer was helpful. If this answers your query, do click Accept Answer and Yes, if you have any further query do let us know.
Suresh Chikkam 2,135 Reputation points Microsoft External Staff Moderator

2025-03-10T01:36:47.1133333+00:00

Hi @Julian Hicks ,

Following up to see if the answer was helpful. If this answers your query, do click Accept Answer and Yes, if you have any further query do let us know.

Answer 1

Suresh Chikkam 2,135 Microsoft External Staff Moderator

Hi @Julian Hicks ,

This issue occurs due to a version mismatch between the SSIS tools and the SQL Server instance. Specifically, the missing DLL (batch parser DLL) is located in the ps_modules\Microsoft.SqlServer.IntegrationServices.Commands.Cmdlets\ folder, and its absence suggests that either the SSIS tools are not properly installed, or the required version of the SQL Server Integration Services (SSIS) components is incompatible with the current setup.

To resolve this, start by checking that both the SSIS tools on the Azure DevOps agent and the SQL Server instance you're working with are on compatible versions. you need to update the SSIS task components to match the SQL Server version you're using, such as updating to the latest version of SQL Server Data Tools (SSDT) and the associated PowerShell cmdlets. Additionally, verify the permissions of the Azure DevOps agent to ensure it has access to modify the SSIS catalog. Reinstalling or updating the SSIS PowerShell module using Install-Module -Name SqlServer can also help resolve any issues with outdated or missing cmdlets. If the problem persists, check the configuration file you're using for the SSIS catalog parameters, as incorrect parameter formatting can trigger errors during deployment.

Hope it helps!

Please do not forget to click "Accept the answer” and Yes wherever the information provided helps you, this can be beneficial to other community members.

User's image

If you have any other questions or still running into more issues, let me know in the "comments" and I would be happy to help you.

Julian Hicks 20 Reputation points

2025-03-17T14:53:35.0833333+00:00
Hi Suresh

Thanks for the answer, but the task is still failing. I have:

installed the latest version of the SqlServer Powershell module on the server hosting the agent

updated the Azure Pipelines agent to version 4.252.0

Visual Studio extension version is SQL Server Integration Services Projects 2022 v1.5 (appears to be the latest version)

All projects are set to target server version of SQL Server 2019, which is the version of SQL Server that we are running

The AzOps agent is running under an account that is a member of the sysadmin built in group and also has been explicitly granted permissions on the SSIS DB in the ssis_admin role. The first task in the pipeline successfully deploys the ispac file to the server so is unlikely to be a permissions issue

the inline configuration JSON is successfully parsed by the component

Not sure what else that I can do - to me it looks like there is a version mismatch but the SSIS Package Configuration component doesn't allow you to specify which version of SQL you are targetting.
Suresh Chikkam 2,135 Reputation points Microsoft External Staff Moderator

2025-03-18T05:45:48.34+00:00
Hi @Julian Hicks ,

Thanks for the update and for sharing the troubleshooting steps you've already performed. let's confirm which version is being loaded during execution.

Run this below command on the Azure DevOps agent machine:

(Get-Command Invoke-Sqlcmd).DLL

If this points to a different version or an unexpected path (such as PowerShell Core instead of Windows PowerShell), Force the PowerShell to Load the Correct SQL Module.

$env:PSModulePath = "C:\Program Files\Microsoft SQL Server\150\SDK\Assemblies" + ";" + $env:PSModulePath Import-Module SqlServer -Force

Try Manually install the SQL components as because the error is related to the Batch Parser DLL.
Suresh Chikkam 2,135 Reputation points Microsoft External Staff Moderator

2025-03-21T01:43:37.5266667+00:00

Hi @Julian Hicks ,

We haven’t heard from you on the last response and was just checking back to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes, if you have any further query do let us know.

Share via

Azure DevOps deploy pipeline SSIS Catalog Configuration task fails with a missing file error

1 answer

Your answer