Hi,
Just to update everyone, we are investigating this issue internally. A number of customer have reported this issue with the use of a Designer remote to the Deployment Service (and engine) with everything in the same domain and using domain accounts.
It is a priority for our Development Services Team to track down and identify the issue. We suspect a problem with Kerberos configuration of some type and have evidence of that from internal testing.
One workaround some customers have used is to install the Deployment Service locally on the same machine as the Designer. You can then disable the Metastorm Authentication for the deployment service in "DeploymentService.exe.config".
Change:
<deploymentCoreConfiguration>
<add key="authenticationProvider" value="Engine"></add> </deploymentCoreConfiguration>
<deploymentCoreConfiguration>
<add key="authenticationProvider" value="None"></add>
</deploymentCoreConfiguration>
And re-point it to your Metastorm DB:
<connectionStrings>
<add name="Metastorm" connectionString="Data Source=<ServerName>;Initial Catalog=Metastorm;User ID=<Username>;Password=<Password>;" providerName="System.Data.SqlClient"></add>
</connectionStrings>
Now you would point your Designer to the local Deployment Service, you will be present with a Username and Password challenge but it will ignore whatever you enter and deploy to the database. You are effectively replicating the v7 Designer functionality.
We suggest this only as a workaround while we work on the issue.
)
