SSAS 2012 Deployment Utility only works in /a (Answer) mode - by Lempster

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 814749 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 1/27/2014 2:24:54 AM
Access Restriction Public


The SSAS Deployment Utility (Microsoft.AnalysisServices.deployment.exe) for SQL Server 2012 does not work in any mode other than /a (Answer) mode which launches the Deployment Wizard and writes the user-supplied 'answers' back to the files produced by building the project.
When the utility is run in /s (Silent) or /o (Output) mode, absolutely nothing happens. It is possible to specify a logging file when using Silent mode, but the file is not created (nor overwritten if it already exists).
This behaviour is true for both 32-bit and 64-bit installs of SSAS 2012 Developer Edition running on a VM VirtualBox server.
Sign in to post a comment.
Posted by arcus4.28 on 10/14/2015 at 9:46 AM
In my opinion, the silent Switch /s works perfect. I work on SQL Server 2012 SP2 Enterprise machines.
Try and have a look to the following ps1 scriptlet: Start-Process -FilePath "C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\Microsoft.AnalysisServices.Deployment.exe" -ArgumentList "W:\DEPLOY\sheeRA_SSAS\shaer\shaer.asdatabase /s:$DeploymentScriptLog" -Wait -WindowStyle Hidden -RedirectStandardOutput "$DeploymentScriptLog" -RedirectStandardError "$DeploymentScriptLog.err"
Posted by Sammy Deprez on 12/23/2014 at 7:18 AM
Has this been fixed in 2014?
Posted by Microsoft on 2/19/2014 at 12:42 PM
We have investigated this and are unable to reproduce the problem.

Someone will contact you offline to ensure that we haven't missed something in your usage scenario.
Posted by Lempster on 1/29/2014 at 9:09 AM
Update: I have also tried using the deployment utility on a physical server to rule out the problem being down to using a VM: same result.