Stanislav Zhelyazkov has been working in IT since 2007. Stanislav has started his IT career as a Help Desk Specialist in 2007 while studying Informatics in the University of Ruse. He also worked in HP Enterprise Services (now known as DXC), maintaining large corporate IT infrastructures for clients in Holland, Switzerland and Germany and was involved in a Private Cloud project based on MS Hyper-V and System Center. He was also in the role of Principal Consultant in Lumagate developing and consulting companies on Azure, OMS, management and Private clouds. Currently he is Cloud Infrastructure Engineer at Sentia Denmark. Stanislav is active community member at MSDN forums providing answers on Azure. His blogposts can be found at www.cloudadministrator.net or www.systemcentercentral.com.
View all posts by Stanislav Zhelyazkov
12 thoughts on “Appling Update Rollup 2 on System Center 2012 R2 Service Management Server Fails With An Error Occurred While Executing a Custom Action:_PatchMP”
I get the same error and reboot does not fix
Try searching the log what is the actual MSI error. Usually that helps for me.
No real mention of the MSI
02:51:21:ApplyQuickFixEngineering: Return value was 1603. Check the log at C:\Users\SQL_ADMIN\AppData\Local\Temp\SCSM2012R2_CU_KB2904710_i386_7.5.3079.61.msp.2.log for more detailed information.
02:51:21:ApplyQfe: FAILED: We did not successfuly install QFE SCSM2012R2_CU_KB2904710_i386_7.5.3079.61.msp.
02:51:21:ProcessInstalls: Patcher returned error 1603:Fatal error during installation
1603 is a MSI error – http://support.microsoft.com/kb/290158
Unfortunately does not say much. In my cases a restart of the server fixed the installation.If you cannot find other useful information the log you may try to use procmon to trace the setup or raise a case to MS.
Ive rebooted the Service Manager system with the console. This is dev and the databases live on another server. I can reboot that one too if you think there is any connection.
My issue was on the SCSM management server. This was the only server that I needed to reboot.
Ok thanks. Unfortunately that isn’t doing the trick. Maybe I will see if it is possible to chat with Microsoft on this. By the way, have you used the Exchange Connector 3.0 to connect SCSM to Exchange?
did you get any response from MS on this?
Looks as though I am having the same issue, and looking for a solution.
Also let me know how i can help with the Exchange connector, had to spend some time, but i have it figured out, and can offer some assistance.
Yes. Try to open case to MS. No I haven’t used the exchange connector.
I am having the problem with UR2 ad UR3 when applying to both the DW server and another server with the web components. No problems with the management servers. Would be interested to know if anyone has root caused this.
Actually the error displayed on SCSM install wizard is too general. It just shows you at what stage it failed. I look at the setup logs for more information. There usually you can see MSI error or something else that might hint you what is the cause.