Daniel Wilson
asked on
SSIS custom task loses Expressions upon deployment
This is related to https://www.experts-exchange.com/questions/24134460/SSIS-custom-task-Property-is-not-getting-value.html
When we deploy a package using a custom task I wrote to our TEST cluster, the package loses the Expressions for that task.
We deploy with the exact same script to our DEV clusters & it works just fine.
What could cause this?
The key parts of the batch file we use to deploy are below:
When we deploy a package using a custom task I wrote to our TEST cluster, the package loses the Expressions for that task.
We deploy with the exact same script to our DEV clusters & it works just fine.
What could cause this?
The key parts of the batch file we use to deploy are below:
SET SSISServer=TestClusterSSISServer.MyDomain\ssists01
SET SQLServer=TestCluster.MyDomain\datts01
SET SSASServer=TestAnalysisServer.MyDomain\anlts01
SET XMLAScript=SalesCubeScript-TEST.XMLA
SET PackageName=CDR Load - Notifications
ECHO.
ECHO Checking for previous version of %PackageName%...
dtutil /SQL "%FolderName%/%PackageName%" /SourceServer %SSISServer% /EXISTS
IF ERRORLEVEL 1 GOTO DEPLOYFOLDER3PACKAGE3
ECHO Deleting the previous version of %PackageName%...
dtutil /SQL "%FolderName%/%PackageName%" /SourceServer %SSISServer% /DELETE
:DEPLOYFOLDER3PACKAGE3
ECHO.
ECHO Deploying new version of %PackageName%...
dtutil /FILE "%PackageName%.dtsx" /DestServer %SSISServer% /ENCRYPT SQL;"%FolderName%/%PackageName%";5 /Quiet
ASKER
Anyway ... anybody got a solution for a scripted deployment? Our bosses are not going to like this workaround ...
Thanks!
Thanks!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We need a script that we can deploy to multiple environments -- DEV, STAGE, TEST, PROD.
For the last 2 environments, we need to hand the script off to the infrastructure team ... so we need a script with minimal input required. With our script they input one thing to indicate the environment to which it's being deployed and it does the rest.
is there a better or more reliable way to do this?
Thanks!
For the last 2 environments, we need to hand the script off to the infrastructure team ... so we need a script with minimal input required. With our script they input one thing to indicate the environment to which it's being deployed and it does the rest.
is there a better or more reliable way to do this?
Thanks!
ASKER
In an hour we'll be testing without the /ENCRYPT flag ... just on a hunch. I'll let you know how that goes ... but would be very interested if you have a good idea why this would be happening -- or a better way to script the installation.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We do find that if we:
Open in new window