Exception: Microsoft.Provisioning.DeploymentTool.Engine.DeploymentExceptionDeploymentFailed
HResult: -2146233088
Message: Deployment interrupted because of a failure. See inner exception.
Stack Trace:
at Microsoft.Provisioning.DeploymentTool.Engine.Deployment.DoDeploymentWork()
at Microsoft.Provisioning.DeploymentTool.MainForm.ExecuteDeploymentSlice()
--------------------
Inner Exception (1): Microsoft.Provisioning.DeploymentTool.Engine.NamedProcedureException
HResult: -2146233088
Message: <errorContext description="The network path was not found" code="0x80070035" executeSeqNo="27"><errorSource namespace="Computer Management Provider" procedure="Group IsMember" /><errorSource namespace="Deployment Automation" procedure="TryLocalGroupAdd_" /><errorSource namespace="Deployment Automation" procedure="AddMPFConfigAdmin_" /><errorSource namespace="Deployment Automation" procedure="ConfigureMPFServiceAccounts" /></errorContext>
Stack Trace:
at Microsoft.Provisioning.DeploymentTool.Engine.ExecuteNamedProcDeploymentAction.CheckForFinished()
at Microsoft.Provisioning.DeploymentTool.Engine.DeploymentAction.Update()
Part of the process to configure the MPF Service Account is to read registry key HKLM\Software\Microsoft\Provisioning value "Configuration Server" and attempt to connect to the server listed there to add the MPFServiceAcct to the local administrators. However, since you used a named instance, that key is not the servername, it is the servername\instancename.
So we will need to configure the MPFServiceAcct manually doing the following:
1. Add MPFServiceAccts group to the local Administrators group on your MPS server and all of the nodes of your MPS SQL server.
2. Add MPFServiceAccts group to the "Windows-based Hosting Service Accounts" group in Active Directory.
3. In the MPS Deployment Tool, right-click "Configure MPF Service Account" and choose "Force State." Choose the VerifiedGood state and click OK.
You should then be able to continue with your deployment.

pOweRK6,
I did everything you said, but I'm still getting the exact same error. Is there any other fix for this that you know?
Thanks, R.
Ruben,
Can you tell me your MPS/HMC version and your environment details like OS/SQL editions?
The workaround here is a bypass way to force the state as Good and Verified.
Regards,
PowerK6 (Randy Zhong)
Randy,
Thanks for your reply.
The HMC version I'm working with is 4.5.228.0. All the servers are virtualized in Citrix XenCenter, running on Windows Server 2003. The SQL version is 2005 with SP2.
Furthermore, I followed everything like described in the Deployment Guide except for one thing: the cluster instance name is not the standard "MPSSQLCLUSTER", but "MPSSQLCLUSTER1". This is because I had a cluster running before, but that one became corrupt. I believe this has something to do with it too, but I don't know how to change the path to the correct cluster instance (which is (after some thinking) necessary in my opinion).
Thanks in advance,
Ruben
Ruben,
On which MPS deployment step your encountered this error?
And I think the MPS SQL Cluster name can be specified as any names. That's may not the root cause.
-R