SAPup broke during phase SHDINST_OS in module PREP_INSTALL / Installation

This trouble ticket was created by SAPup on 20150711204813
-------------------------------------------------------------
SAPup broke during phase SHDINST_OS in module PREP_INSTALL / Installation
Error Message: Action 'install' for DCOM service failed, see phase log for details: Cannot create a file when that file already exists.

-------------------------------------------------------------
-------------------------------------------------------------
Summary of SAPup:
-------------------------------------------------------------
SAPehpi Release: lmt_004
SAPehpi Version: SAPup release lmt_004 version 58.000
Start Release:  701
Target Release:  702
-------------------------------------------------------------
Summary of host system details:
-------------------------------------------------------------
SID:   SOL
Host:   dummy-SolMan
MS Host:  dummy-SolMan
GW Host:  dummy-SolMan
Start Path:  C:\usr\sap\SOL\DVEBMGS00\exe
Kernel Path:  C:\usr\sap\SOL\DVEBMGS00\exe
-------------------------------------------------------------
Summary of operating system details:
-------------------------------------------------------------
OS Type:  Windows NT X86_64
OS Version:  6.0
-------------------------------------------------------------
Summary of database details:
-------------------------------------------------------------
Database Type:  ora
Database Version: 11.2.0.3.0
-------------------------------------------------------------
Summary of RFC details:
-------------------------------------------------------------
Host:   dummy-SolMan
GW Host:  dummy-SolMan
Client:   000
Destination:  SOL
Language:  E
System No.:  00
-------------------------------------------------------------
-------------------------------------------------------------



Solution:

This is caused due to incorrect SAPService<SID> user password provided to SUM.

 

Check your SAPService<SID> user password that you provided to SUM.

You might have provided incorrect password to SUM during the Configuration phase.

 

Change the SAPService<SID> user password to what you had provided to SUM.

Also make sure you update the same password in 'Services' related to instance owned by SAPService<SID> user.

 

Once done, resume your SUM, the error will no longer occur.

 

Thanks

Yoonus