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()
Stack Trace:
at Microsoft.Provisioning.DeploymentTool.Engine.ExecuteNamedProcDeploymentAction.CheckForFinished()
at Microsoft.Provisioning.DeploymentTool.Engine.DeploymentAction.Update()
it seems that SQL Server is generating this error. i have double checked MS DTC, i even tried it with "No Authentication Required" option. still no donuts.
it was the DNS problem in the end. MPS01's IP was given wrong in DNS of AD machine. i corrected it and installation process ran smooth.
generally this problem occurs when Database server can not access (ping) the other server which is accessing Database in a Distributed environment or otherwise, The acccessing server can not ping (NetBios access) Database server.
in my scenario, MPS01 was accessing DB server MPSSQL01, where they both were part of a domain. On the AD machine, IP of MPS01 was configured wrong in its DNS so it was not accessible from domain. With the correction of IP, the problem is fixed. Figuring
it out took my whole day though.
I am having the same issue here. All DNS configuration are correct anyway. What could be the reason of this problem here ?
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()
Stack Trace:
at Microsoft.Provisioning.DeploymentTool.Engine.ExecuteNamedProcDeploymentAction.CheckForFinished()
at Microsoft.Provisioning.DeploymentTool.Engine.DeploymentAction.Update()
did u try pinging from MPS01 to MPSSQL01 and vice versa ...?
if its alright, it may be the problem with SQL Server 2005. it may not be configured to use network protocol (tcp/ip) (by default it is not configured to use tcp/ip)
use surface area configuration tool of SQL server to allow TCP/IP usage like this:
on surface area configuration window, click on surface area configuration for services and connections
select Database Engine -> Remote Connections and from right hand side pan select
Local and Remote Connections -> Use both TCP/IP and named Pipes
then try again this procedure, this should fix the problem.
Here is detail error log.
This error occured in Hosting Platform --> Hosted Plan Database --> Initialize Managed Plans Database.
I already checked DTS property inbound and outbound checked.
Could you please give me any hint?
Exception: Microsoft.Provisioning.DeploymentTool.Engine.DeploymentExceptionDeploymentFailed
Message: Deployment interrupted because of a failure. See inner exception.
... and here's my error; none of the solutions seem to have worked for me. I've opened a case with support and will post my results. I'm running in a partially consolidated environment with no clustering (lab environment)
-----
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()
Stack Trace:
at Microsoft.Provisioning.DeploymentTool.Engine.ExecuteNamedProcDeploymentAction.CheckForFinished()
at Microsoft.Provisioning.DeploymentTool.Engine.DeploymentAction.Update()
Make sure that MS DTC is running on both servers: MPS01 and MPSSQL01. You probably have to reinstall it. See instructions here -
http://support.microsoft.com/kb/279786
My MPS01 is an ESX VM and have been cloned from another Windows VM, which produced the following error the applicationlog.
--------------------------------
Event Type:Error
Event Source:MSDTC
Event Category:CM
Event ID:4101
Date:1/25/2008
Time:10:36:27 AM
User:N/A
Computer:MPS01
Description:
The local MS DTC detected that the MS DTC on SQL01 has the same unique identity as the local MS DTC. This means that the two MS DTC will not be able to communicate with each other. This problem typically occurs if one of the systems were cloned using unsupported
cloning tools. MS DTC requires that the systems be cloned using supported cloning tools such as SYSPREP. Running 'msdtc -uninstall' and then 'msdtc -install' from the command prompt will fix the problem. Note: Running 'msdtc -uninstall' will result in the
system losing all MS DTC configuration information.
yes, thats why cloning from one VM is not recommended! i used to clone windows from a VMware Virtual Machine, and had the problem "have same SID values" with windows.
Member
43 Points
126 Posts
Error in HMC 4.0 installation at DWSPV 34
Oct 26, 2007 05:55 AM|aqeel asghar|LINK
hello ever1!
just got struck here, the error popping up is:
************************************************************************************************************************************************************************************
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="New transaction cannot enlist in the specified transaction coordinator." code="0x8004d00a" executeSeqNo="143"><errorSource namespace="Error Provider" procedure="SetError" /><errorSource namespace="Managed Active Directory" procedure="RethrowError_" /><errorSource namespace="Managed Plans" procedure="IgnoreExists_" /><errorSource namespace="Managed Plans" procedure="CreateEventType_" /><errorSource namespace="Managed Plans" procedure="Initialize_" /><errorSource namespace="Managed Plans" procedure="Initialize" /></errorContext>
Stack Trace:
at Microsoft.Provisioning.DeploymentTool.Engine.ExecuteNamedProcDeploymentAction.CheckForFinished()
at Microsoft.Provisioning.DeploymentTool.Engine.DeploymentAction.Update()
************************************************************************************************************************************************************************************
it seems that SQL Server is generating this error. i have double checked MS DTC, i even tried it with "No Authentication Required" option. still no donuts.
Any Suggestions .....
Member
43 Points
126 Posts
Re: Error in HMC 4.0 installation at DWSPV 34
Oct 26, 2007 12:22 PM|aqeel asghar|LINK
well, just resolved it .... [:)]
it was the DNS problem in the end. MPS01's IP was given wrong in DNS of AD machine. i corrected it and installation process ran smooth.
generally this problem occurs when Database server can not access (ping) the other server which is accessing Database in a Distributed environment or otherwise, The acccessing server can not ping (NetBios access) Database server.
in my scenario, MPS01 was accessing DB server MPSSQL01, where they both were part of a domain. On the AD machine, IP of MPS01 was configured wrong in its DNS so it was not accessible from domain. With the correction of IP, the problem is fixed. Figuring it out took my whole day though.
[:)]
None
0 Points
8 Posts
Re: Error in HMC 4.0 installation at DWSPV 34
Dec 11, 2007 10:55 AM|TarkanVeKurdu|LINK
I am having the same issue here. All DNS configuration are correct anyway. What could be the reason of this problem here ?
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="New transaction cannot enlist in the specified transaction coordinator." code="0x8004d00a" executeSeqNo="152"><errorSource namespace="Error Provider" procedure="SetError" /><errorSource namespace="Managed Active Directory" procedure="RethrowError_" /><errorSource namespace="Managed Plans" procedure="IgnoreExists_" /><errorSource namespace="Managed Plans" procedure="CreateEventType_" /><errorSource namespace="Managed Plans" procedure="Initialize_" /><errorSource namespace="Managed Plans" procedure="Initialize" /></errorContext>
Stack Trace:
at Microsoft.Provisioning.DeploymentTool.Engine.ExecuteNamedProcDeploymentAction.CheckForFinished()
at Microsoft.Provisioning.DeploymentTool.Engine.DeploymentAction.Update()
Regards,
Tarkan
Member
43 Points
126 Posts
Re: Error in HMC 4.0 installation at DWSPV 34
Dec 13, 2007 05:04 AM|aqeel asghar|LINK
did u try pinging from MPS01 to MPSSQL01 and vice versa ...?
if its alright, it may be the problem with SQL Server 2005. it may not be configured to use network protocol (tcp/ip) (by default it is not configured to use tcp/ip)
use surface area configuration tool of SQL server to allow TCP/IP usage like this:
on surface area configuration window, click on surface area configuration for services and connections
select Database Engine -> Remote Connections and from right hand side pan select Local and Remote Connections -> Use both TCP/IP and named Pipes
then try again this procedure, this should fix the problem.
None
0 Points
2 Posts
Re: Error in HMC 4.0 installation at DWSPV 34
Jan 20, 2008 07:13 PM|trustuu|LINK
I got same issue.
I check remote connections that "Use bosth TCP/IP and named Pipes" is enabled.
I try pinging MPS01 to MPSSQL01, MPSSQL02, MPSSQLVS01(Virtual Server for SQL) and vice versa, it works too.
I ever configured HMC4.0 succefully before, different is only clustering configuration.
Could you give any clues?
None
0 Points
2 Posts
Re: Error in HMC 4.0 installation at DWSPV 34
Jan 20, 2008 10:16 PM|trustuu|LINK
Here is detail error log.
This error occured in Hosting Platform --> Hosted Plan Database --> Initialize Managed Plans Database.
I already checked DTS property inbound and outbound checked.
Could you please give me any hint?
Exception: Microsoft.Provisioning.DeploymentTool.Engine.DeploymentExceptionDeploymentFailed
Message: Deployment interrupted because of a failure. See inner exception.
Exception: Microsoft.Provisioning.DeploymentTool.Engine.NamedProcedureException
Message: <errorContext description="New transaction cannot enlist in the specified transaction coordinator." code="0x8004d00a" executeSeqNo="152"><errorSource namespace="Error Provider" procedure="SetError" /><errorSource namespace="Managed Active Directory" procedure="RethrowError_" /><errorSource namespace="Managed Plans" procedure="IgnoreExists_" /><errorSource namespace="Managed Plans" procedure="CreateEventType_" /><errorSource namespace="Managed Plans" procedure="Initialize_" /><errorSource namespace="Managed Plans" procedure="Initialize" /></errorContext>
---------------------------------------------------------------------
<response><errorContext description="New transaction cannot enlist in the specified transaction coordinator." code="0x8004d00a" executeSeqNo="152"><errorSource namespace="Error Provider" procedure="SetError"/><errorSource namespace="Managed Active Directory" procedure="RethrowError_"/><errorSource namespace="Managed Plans" procedure="IgnoreExists_"/><errorSource namespace="Managed Plans" procedure="CreateEventType_"/><errorSource namespace="Managed Plans" procedure="Initialize_"/><errorSource namespace="Managed Plans" procedure="Initialize"/></errorContext></response>
None
0 Points
10 Posts
Re: Error in HMC 4.0 installation at DWSPV 34
Jan 24, 2008 12:14 PM|hdawg|LINK
... and here's my error; none of the solutions seem to have worked for me. I've opened a case with support and will post my results. I'm running in a partially consolidated environment with no clustering (lab environment)
-----
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="New transaction cannot enlist in the specified transaction coordinator." code="0x8004d00a" executeSeqNo="143"><errorSource namespace="Error Provider" procedure="SetError" /><errorSource namespace="Managed Active Directory" procedure="RethrowError_" /><errorSource namespace="Managed Plans" procedure="IgnoreExists_" /><errorSource namespace="Managed Plans" procedure="CreateEventType_" /><errorSource namespace="Managed Plans" procedure="Initialize_" /><errorSource namespace="Managed Plans" procedure="Initialize" /></errorContext>
Stack Trace:
at Microsoft.Provisioning.DeploymentTool.Engine.ExecuteNamedProcDeploymentAction.CheckForFinished()
at Microsoft.Provisioning.DeploymentTool.Engine.DeploymentAction.Update()
Participant
1091 Points
1101 Posts
Re: Error in HMC 4.0 installation at DWSPV 34
Jan 24, 2008 01:24 PM|DmitriG|LINK
Make sure that MS DTC is running on both servers: MPS01 and MPSSQL01. You probably have to reinstall it. See instructions here - http://support.microsoft.com/kb/279786
Dmitri Gaikovoi
Member
2 Points
20 Posts
Re: Error in HMC 4.0 installation at DWSPV 34
Jan 25, 2008 04:57 AM|chrsm|LINK
Had the same problem in DWSPV.34
My MPS01 is an ESX VM and have been cloned from another Windows VM, which produced the following error the applicationlog.
--------------------------------
Event Type: Error
Event Source: MSDTC
Event Category: CM
Event ID: 4101
Date: 1/25/2008
Time: 10:36:27 AM
User: N/A
Computer: MPS01
Description:
The local MS DTC detected that the MS DTC on SQL01 has the same unique identity as the local MS DTC. This means that the two MS DTC will not be able to communicate with each other. This problem typically occurs if one of the systems were cloned using unsupported cloning tools. MS DTC requires that the systems be cloned using supported cloning tools such as SYSPREP. Running 'msdtc -uninstall' and then 'msdtc -install' from the command prompt will fix the problem. Note: Running 'msdtc -uninstall' will result in the system losing all MS DTC configuration information.
--------------------------------------------------------
So after reinstall of MSDTC everything is working. Remember to do DWSPV.24 after reinstalling.
Member
43 Points
126 Posts
Re: Error in HMC 4.0 installation at DWSPV 34
Jan 25, 2008 06:54 AM|aqeel asghar|LINK
yes, thats why cloning from one VM is not recommended! i used to clone windows from a VMware Virtual Machine, and had the problem "have same SID values" with windows.