I have an Integration Services Project in Visual Studio 2017 with SSDT 15.5.1 that targets SQL Server 2012 that will not deploy due to out of memory errors despite having plenty of available memory. These errors occur on either the Changing protection level action as below:

Or on the next action of Deploying project

When I have encountered this error before I have used the 64-bit version of ISDeploymentWizard which is currently available in the folder C:\Program Files\Microsoft SQL Server0\DTS\Binn

Unfortunately this isn’t working as after hours of letting the deployment wizard run it remains on the Changing protection level action, task manager is reporting 30% CPU and 200-600MB memory throughout.

I have currently tried to deploy the .ispac via SSMS 17.3, SSDT 2015, SSMS 2012 (11.0.6607.3) on the target server along with deploying to a new project instead of existing where I have the same results.

I have been able to successfully deploy my project using SSDT provided with SQL Server 2012 on the server and with the 64-bit ISDeploymentWizard on the server but the packages now fail to execute with the error:

DFT SROrganisationBranch Bulk:Error: System.IO.FileNotFoundException: Could not load file or assembly ‘Microsoft.SqlServer.PipelineHost, Version=14.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91’ or one of its dependencies. The system cannot find the file specified. File name: ‘Microsoft.SqlServer.PipelineHost, Version=14.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91’ at System.Reflection.RuntimeAssembly.GetExportedTypes(RuntimeAssembly assembly, ObjectHandleOnStack retTypes) at System.Reflection.RuntimeAssembly.GetExportedTypes() at Microsoft.SqlServer.Dts.Pipeline.VSTAComponentScriptingEngine.CreateScriptObjectHelper(Assembly scriptAssembly) at Microsoft.SqlServer.Dts.Pipeline.VSTAComponentScriptingEngine.GetScriptEntryPoint(String versionGuid) at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.CreateUserScriptInstance()

WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

At the moment I’m stuck with a project that will not deploy and the deployed version fails to execute on the server. What other options do I have available to deploy my project?