Did you enable Distributed Transaction Coordinator (DTC) on both MPS01 and MPSSQL01? I suppose it is enabled during setting up the cluster.
Tolga.
This posting is provided "AS IS" with no warranties, and confers no rights. Use of any included script or code samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm"
I have seen a couple of different causes for this problem.
Network DTC has not been installed and configured on MPS and SQL servers per the documentation
Image cloning (Ghost, NewSID, or just copying virtual server images) is being used. The problem with cloning is that the DTC needs to have a unique ID in order to participate in DCOM - but when you clone, all cloned images get the same ID.
If you have cloned images, you need to reinstall DTC on each image from the command line. Remove the DTC service in a command window by typing "msdtc -uninstall".
Then type msdtc -install
Then follow the HMC documentation to reconfigure DTC security settings.
Thanks you put me on the correct track to fix the issue. I had to do a few extra steps that I will add to this post but the deployment did finish.
The steps below were done because the msdtc -install then caused Com+ errors.
msdtc reinstall:
The solution was to uninstall and re-install DTC. The steps for this are:
Use Add Windows Components, and remove hte Network DTC from the Application Services.
Run MSDTC -uninstall
Go into the registry and remove the MSDTC keys in HKLM/Software/Microsoft/MSDTC and
HKLM/System/CurrentControlSet/Services/MSDTC
Reboot
Run MSDTC -install
Run Windows Add Components and add Network DTC back in.
Do this on both the MPS01 server and the MPSSQL01 server
Note: Make sure you restart the msdtc on the sql server and set it to auto start or you will get the same error as before. I thought this could have been the cause of my error but I had checked all the SQL services prior to going through all the steps.
I hit this error also and the cause was that MPSSQL02 was hosting the resources in the cluster. Once I failed back to MPSSQL01 then it went through successfully.
Thanks for posting the solution! I used cloning to make a development system and couldnt deploy MPS very well.
I didnt have to uninstall MSDTC from both machines, I just did it from MPS and reinstalled and it worked. Both MPS & SQL were from same clone that already had Network DTC and MSDTC ready and configured.
Thanks for posting the solution! I used cloning to make a development system and couldnt deploy MPS very well.
I didnt have to uninstall MSDTC from both machines, I just did it from MPS and reinstalled and it worked. Both MPS & SQL were from same clone that already had Network DTC and MSDTC ready and configured.
Hello,
If you are cloning images, such as copying vhd files with Virtual server for lab deployment, just make sure you run sysprep before shutting down your OS master (with minimum installation), and then you have a vhd template you can duplicate. When running
the copy of the vhd template, it will ask you the server name, licence key etc. and generate new SIDs...,
Regards,
Samuel
PS: If helpful, please mark this post as answered
--
Samuel Dupas
Planet Technologies EMEA -- http://www.go-planet.com
I have been struggling with this error for days, how frustrating. I am using vmware virtual servers, but all servers were using generic clones with service pack 2 installed and sysprep was applied.
I have re-installed this from scratch 3 times. I have uninstalled, re-installed msdtc and rebooted several times. I have mpssql01 and mpssql02 in a cluster. Still encountering the same error at the same point in the mps deployment tool. Is there anyway to
troubleshoot this in detail or is there at least a definite work around, such as uninstall mpssql cluster and install single sql server.
According to this forums, everything seems to point to DTC, but if someone could point me in the right direction in confirming that DTC is in fact the problem. I don't see any errors in the event logs for mpssql01, mpssql02, mps01, or mps02. If I knew definitively
what the problem was, such a communication or security problem, I could theoretically fix it, but this mps stuff seems to be an enigma wrapped in a question.
Pthunder
Member
15 Points
3 Posts
Initialize plans database error
Feb 05, 2006 11:56 PM|LINK
Lab test configuration: currently 3 virtual servers AD01, MPSSQL01, AND MPS01 no cluster.
I am at the last step of DWSPV.21 and it errors out on the initialize plans database
the only other error was on the configure MPS cluster admin since we are not using one.
here is the error : Failure details:
Exception: Microsoft.Provisioning.DeploymentTool.Engine.NamedProcedureException
Message: <errorContext description="New transaction cannot enlist in the specified transaction coordinator." code="0x8004d00a" executeSeqNo="9"><errorSource namespace="Error Provider" procedure="SetError" /><errorSource namespace="Managed Active Directory" procedure="ReThrowError_" /><errorSource namespace="Managed Helpers" procedure="CreateEventTypeRecord_" /><errorSource namespace="Managed Helpers" procedure="InitializePlanDatabase" /></errorContext>
Stack Trace:
at Microsoft.Provisioning.DeploymentTool.Engine.ExecuteNamedProcDeploymentAction.CheckForFinished()
at Microsoft.Provisioning.DeploymentTool.Engine.DeploymentAction.Update()
I have gone over the entire install plus wiped all virtual servers and started clean with the same issue.
Any help on this would be great. Thanks,
Paul
tkilicli
Member
20 Points
4 Posts
Re: Initialize plans database error
Feb 08, 2006 07:15 PM|LINK
Hello,
Did you enable Distributed Transaction Coordinator (DTC) on both MPS01 and MPSSQL01? I suppose it is enabled during setting up the cluster.
Tolga.
v-vladm
Member
247 Points
51 Posts
Re: Initialize plans database error
Feb 08, 2006 07:51 PM|LINK
I have seen a couple of different causes for this problem.
If you have cloned images, you need to reinstall DTC on each image from the command line. Remove the DTC service in a command window by typing "msdtc -uninstall".
Then type msdtc -install
Then follow the HMC documentation to reconfigure DTC security settings.
-Vlad
implement.com
Pthunder
Member
15 Points
3 Posts
Re: Initialize plans database error
Feb 08, 2006 09:50 PM|LINK
the settings I have on both mps01 and mpssql01 for dtc are"
checked: network dtc access
client and administration:
checked: allow remote client checked: allow remote administrations
Transaction manaher communication
checked: allow inbound checked: allow outbound
checked: Mutual authentication required
Checked Enable XA transactions
DTC logon account nt authority\networkservice
still unable to get past the error.
Pthunder
Member
15 Points
3 Posts
Re: Initialize plans database error
Feb 09, 2006 12:43 AM|LINK
Vlad,
Thanks you put me on the correct track to fix the issue. I had to do a few extra steps that I will add to this post but the deployment did finish.
The steps below were done because the msdtc -install then caused Com+ errors.
msdtc reinstall:
The solution was to uninstall and re-install DTC. The steps for this are:
Use Add Windows Components, and remove hte Network DTC from the Application Services.
Run MSDTC -uninstall
Go into the registry and remove the MSDTC keys in HKLM/Software/Microsoft/MSDTC and
HKLM/System/CurrentControlSet/Services/MSDTC
Reboot
Run MSDTC -install
Run Windows Add Components and add Network DTC back in.
Do this on both the MPS01 server and the MPSSQL01 server
Note: Make sure you restart the msdtc on the sql server and set it to auto start or you will get the same error as before. I thought this could have been the cause of my error but I had checked all the SQL services prior to going through all the steps.
v-vladm
Member
247 Points
51 Posts
Re: Initialize plans database error
Feb 09, 2006 07:08 PM|LINK
Glad to see you were able to sort it out. I'll add what you discovered to my notes.
Regards,
Vlad
Rumple
Member
4 Points
2 Posts
Re: Initialize plans database error
May 24, 2007 03:06 AM|LINK
I hit this error also and the cause was that MPSSQL02 was hosting the resources in the cluster. Once I failed back to MPSSQL01 then it went through successfully.
paulsilverst...
Member
101 Points
96 Posts
Re: Initialize plans database error
Sep 04, 2007 10:39 PM|LINK
Thanks for posting the solution! I used cloning to make a development system and couldnt deploy MPS very well.
I didnt have to uninstall MSDTC from both machines, I just did it from MPS and reinstalled and it worked. Both MPS & SQL were from same clone that already had Network DTC and MSDTC ready and configured.
sdupas
Member
487 Points
142 Posts
Re: Initialize plans database error
Sep 05, 2007 06:05 AM|LINK
Hello,
If you are cloning images, such as copying vhd files with Virtual server for lab deployment, just make sure you run sysprep before shutting down your OS master (with minimum installation), and then you have a vhd template you can duplicate. When running the copy of the vhd template, it will ask you the server name, licence key etc. and generate new SIDs...,
Regards,
Samuel
--
Samuel Dupas
Planet Technologies EMEA -- http://www.go-planet.com
charles@cblc...
Member
2 Points
1 Post
Re: Initialize plans database error
Feb 24, 2008 05:17 PM|LINK
I have been struggling with this error for days, how frustrating. I am using vmware virtual servers, but all servers were using generic clones with service pack 2 installed and sysprep was applied.
I have re-installed this from scratch 3 times. I have uninstalled, re-installed msdtc and rebooted several times. I have mpssql01 and mpssql02 in a cluster. Still encountering the same error at the same point in the mps deployment tool. Is there anyway to troubleshoot this in detail or is there at least a definite work around, such as uninstall mpssql cluster and install single sql server.
According to this forums, everything seems to point to DTC, but if someone could point me in the right direction in confirming that DTC is in fact the problem. I don't see any errors in the event logs for mpssql01, mpssql02, mps01, or mps02. If I knew definitively what the problem was, such a communication or security problem, I could theoretically fix it, but this mps stuff seems to be an enigma wrapped in a question.
HMC 4.0 initialize managed pland database