ISSUE: Build may incorrectly indicate FAILURE in certain conditions

[tfabraham]

After trying to figure it out today i found that deployment of bam will mess up the deployment we have a custom targets where some of the bam steps are modified but the exec task still has the Continue OnError property set to TRUE

So indeed in the logging we see the error converted to a warning: Deploying BAM security... Deploying BAM security...(commandline) "C:\Program Files (x86)\Microsoft BizTalk Server 2013\Tracking\bm.exe" add-account -View:"vw_xxxxxxx" -AccountName:"BUILTIN\Administrators" Microsoft (R) Business Activity Monitoring Utility Version 3.10.229.0 Copyright (C) Microsoft Corporation. All rights reserved.

        Using 'BAMPrimaryImport' BAM Primary Import database on server 'BTS2013DEV'...

        ERROR: Security management of the BAM view failed.
        The specified account is already in the view.

        MSBUILD : warning MSB3073: The command ""C:\Program Files (x86)\Microsoft BizTalk Server 2013\Tracking\bm.exe" add-account -View:"vw_xxxxxx -AccountName:"BUILTIN\Administrators"" exited with code 2.
       __ The previous error was converted to a warning because the task was called with ContinueOnError=true.__
        __Build continuing because "ContinueOnError" on the task "Exec" is set to "true".__

        Finished deploying BAM security.

So everything looks fine and the logging will never show you a build error. However the command window states there is an error..... So it look like something went wrong.

The mesage we see is: 0 Error(s)

Time Elapsed 00:00:41.71 C:\Program Files (x86)\gegevens\1.3.0\Deployment\ Framework\BizTalkDeploymentFramework.ServerExecute.targets(66,5): error MSB3073 : The command ""C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe" /p:D eployBizTalkMgmtDB=true;ENV_SETTINGS="C:\Program Files (x86)\gegevens\1.3.0\Deployment\EnvironmentSettings\LOCAL_settings.xml";C onfiguration=Server;SkipUndeploy=true /target:Deploy /l:FileLogger,Microsoft.Bu ild.Engine;logfile=....\DeployResults\DeployResults.txt "..\gegevens.Deployment.btdfproj"" exited with code -1. Copy: Copying file from "....\DeployResults\DeployResults.txt" to "....\DeployRes ults\DeployResults_BTS2013DEV_10172013_1645.txt". Press a key to continue...

* FAILED! ***

Press a key to continue...

And in the logging on disk we see :

Build succeeded.

MSBUILD : warning MSB3073: The command ""C:\Program Files (x86)\Microsoft BizTalk Server 2013\Tracking\bm.exe" add-account -View:"vw_xxxx" -AccountName:"BUILTIN\Administrators"" exited with code 2. 1 Warning(s)

0 Error(s)

Time Elapsed 00:00:40.47

So this discrepancy should be fixed because the Administrators of Biztalk are now reporting failures on installers if the BAM profile was already set up......

This work item was migrated from CodePlex

CodePlex work item ID: '10406' Assigned to: 'tfabraham' Vote count: '1'

[tfabraham]

[well0549@10/18/2013]

Found a solution myself..... Not the nicest one but it does the job :

http://bloggingabout.net/blogs/wellink/archive/2013/10/18/multiline-exec-biztalk-deployment-btdf-or-a-gotcha-in-msbuild-don-t-know-but-there-is-a-workaround.aspx

[tfabraham]

[well0549@10/21/2013] I think this is caused by a build calling a build. So the build that shows the message "Press Any key to continue" fails. this one looks at the output of the build that does the actual work. and sees an error and then decides that the previous buildtyask has failed. But this was not true because the error was converted to a warning.

[tfabraham]

[tfabraham@2/6/2014] Did you find this in v5.1 Beta 2 or a different release?

[tfabraham]

[well0549@2/7/2014] 5.1 how can i see which beta it is ?

[tfabraham]

[UnknownUser@2/7/2014]

[tfabraham]

[tfabraham@2/7/2014] Good news -- finally reproduced it. It's because of MSBuild parsing command output searching for error and warning text with a regular expression. I have a fix for it.

[tfabraham]

[UnknownUser@2/7/2014] Resolved with changeset 74521: Fix issue that could cause a deployment process to incorrectly indicate failure (#10406)