I where trying to Configure EDI/AS2 using BizTalk 2020 Configure wizard, I faced below error while configuring so:
TITLE: Microsoft BizTalk Server Configuration Wizard
Failed to deploy BAM activity definitions. Please make sure that all BAM related Data Transformation Services (DTS) packages are removed along with the BAM databases. (Microsoft.BizTalk.Configuration.EDIAS2.Utility)
For help, click: http://go.microsoft.com/fwlink/events.asp?ProdName=Microsoft+BizTalk+Server&ProdVer=3.13.717.0&EvtSrc=Microsoft.BizTalk.Configuration.EDIAS2.Utility&EvtID=StrFailedToDeployBAMActivity
ADDITIONAL INFORMATION:
Failed to execute process: C:\Program Files (x86)\Microsoft BizTalk Server\Tracking\bm.exe. (Microsoft.BizTalk.Configuration.EDIAS2.Utility)
For help, click: http://go.microsoft.com/fwlink/events.asp?ProdName=Microsoft+BizTalk+Server&ProdVer=3.13.717.0&EvtSrc=Microsoft.BizTalk.Configuration.EDIAS2.Utility&EvtID=StrFailedToExecuteProcess
Microsoft (R) Business Activity Monitoring Utility Version 3.13.717.0
Copyright (C) Microsoft Corporation. All rights reserved.
Using ‘BAMPrimaryImport’ BAM Primary Import database on server ‘SERVER-NAME’…
Deploying Activity… ERROR: The BAM deployment failed.
A .NET Framework error occurred during execution of user-defined routine or aggregate ‘deploy_project_internal’:
System.ComponentModel.Win32Exception: A required privilege is not held by the client
System.ComponentModel.Win32Exception:
at Microsoft.SqlServer.IntegrationServices.Server.ISServerProcess.StartProcess(Boolean bSuspendThread)
at Microsoft.SqlServer.IntegrationServices.Server.ServerApi.DeployProjectInternal(SqlInt64 deployId, SqlInt64 versionId, SqlInt64 projectId, SqlString projectName)
.
(Microsoft.BizTalk.Configuration.EDIAS2.Utility)
For help, click: http://go.microsoft.com/fwlink/events.asp?ProdName=Microsoft+BizTalk+Server&ProdVer=3.13.717.0&EvtSrc=Microsoft.BizTalk.Configuration.EDIAS2.Utility&EvtID=StrFailedToExecuteProcess
BUTTONS:
OK
Solution:
Finally after searching online after couple of hour I found reason behind is USER do not have sufficient privilege’s which can be fixed by SQL-Server-Repair works is because SQL Server Setup grants certain permissions during setup.
These permissions can be found here https://msdn.microsoft.com/en-us/library/ms143504(v=sql.110).aspx#Windows
Hope This Helps!
