Sign in
 
HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog
TechCenter >
> 
> 
Error 1023 and 2152 occurs during exchange 2010 sp2 rollover1 install

Answered Error 1023 and 2152 occurs during exchange 2010 sp2 rollover1 install

  • Tuesday, March 06, 2012 3:30 AM
     
     
    Sign In to Vote
    0

    error 1023:

    Product: Microsoft Exchange Server - Update 'Update Rollup 1 for Exchange Server 2010 Service Pack 2 (KB2645995) 14.2.283.3' could not be installed. Error code 1603. Additional information is available in the log file C:\Users\XX\AppData\Local\Temp\2\MSI2ecce.LOG.

    error 2152:

    Process powershell.exe () (PID=1456). An remote procedure call (RPC) request to the Microsoft Exchange Active Directory Topology service failed with error 5 (Error 0x5 (Access is denied) from HrGetServersForRole). Make sure that the Remote Procedure Call (RPC) service is running. In addition, make sure that the network ports that are used by RPC are not blocked by a firewall.

    Any ideas?

    Jason

     

All Replies

  • Tuesday, March 06, 2012 3:53 AM
     
     
    Sign In to Vote
    0

    Did you apply the rollup from a elevated command prompt (Run as administrator)? If not, do so.

    Always install Exchange 2010 rollups from an elevated command shell
    http://angrytechnician.wordpress.com/2010/03/12/always-install-exchange-2010-rollups-from-an-elevated-command-shell/

    MCTS: Messaging | MCSE: S+M

     
  • Tuesday, March 06, 2012 3:57 AM
     
     
    Sign In to Vote
    0

    When I right click on it the first option is Apply,

    There is no elevated command prompt option for me, any idea?

    Jason

     
  • Tuesday, March 06, 2012 4:00 AM
     
     
    Sign In to Vote
    0

    I tried this and same error,

    Product: Microsoft Exchange Server - Update 'Update Rollup 1 for Exchange Server 2010 Service Pack 2 (KB2645995) 14.2.283.3' could not be installed. Error code 1603. Additional information is available in the log file C:\Users\XX\AppData\Local\Temp\MSI560c5.LOG.

    Jason

     
  • Tuesday, March 06, 2012 4:22 AM
     
     Answered
    Sign In to Vote
    0

    Things that come to mind: disable antivirus for Exchange and HP agents, do not install from a network share, remove interim updates.

    Have you studied the error log?

    While written for Exchange 2007, some of Amit Tank's tips might help you:

    Exchange Update Rollup Installation. It is not Nightmare!!!
    http://exchangeshare.wordpress.com/2009/05/30/exchange-update-rollup-installation-it-is-not-nightmare/

    MCTS: Messaging | MCSE: S+M

    • Marked As Answer by Jason-chen Friday, March 09, 2012 4:53 AM
    •  
     
  • Tuesday, March 06, 2012 4:34 AM
     
     
    Sign In to Vote
    0

    Hi Jon, thanks for your reply.

    I googled a lot but didn't find a solution

    I followed this http://blog.powershell.no/2010/04/20/installing-exchange-server-20072010-update-rollups/ but still get the same error.

    What is interim update? I recently deployed this exchange 2010 and installed exchange 2010 sp2 directly.

    Jason

     
  • Tuesday, March 06, 2012 5:02 AM
     
     
    Sign In to Vote
    0

    This is the end of verbose log

    == Logging stopped: 3/5/2012  21:38:26 ===
    MSI (c) (B8:C4) [21:38:26:358]: Product: Microsoft Exchange Server - Update 'Update Rollup 1 for Exchange Server 2010 Service Pack 2 (KB2645995) 14.2.283.3' could not be installed. Error code 1603. Additional information is available in the log file c:\sp2ur1.log.

    MSI (c) (B8:C4) [21:38:26:358]: Windows Installer installed an update. Product Name: Microsoft Exchange Server. Product Version: 14.2.247.5. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: Update Rollup 1 for Exchange Server 2010 Service Pack 2 (KB2645995) 14.2.283.3. Installation success or error status: 1603.

    MSI (c) (B8:C4) [21:38:26:358]: Note: 1: 1729
    MSI (c) (B8:C4) [21:38:26:358]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (c) (B8:C4) [21:38:26:358]: Transforming table Error.

    MSI (c) (B8:C4) [21:38:26:358]: Transforming table Error.

    MSI (c) (B8:C4) [21:38:26:358]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (c) (B8:C4) [21:38:26:358]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (c) (B8:C4) [21:38:26:374]: Transforming table Error.

    MSI (c) (B8:C4) [21:38:26:374]: Transforming table Error.

    MSI (c) (B8:C4) [21:38:26:374]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (c) (B8:C4) [21:38:26:374]: Product: Microsoft Exchange Server -- Configuration failed.

    MSI (c) (B8:C4) [21:38:26:374]: Windows Installer reconfigured the product. Product Name: Microsoft Exchange Server. Product Version: 14.2.247.5. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 1603.

    MSI (c) (B8:C4) [21:38:26:374]: Grabbed execution mutex.
    MSI (c) (B8:C4) [21:38:26:374]: Cleaning up uninstalled install packages, if any exist
    MSI (c) (B8:C4) [21:38:26:374]: MainEngineThread is returning 1603
    === Verbose logging stopped: 3/5/2012  21:38:26 ===

    Jason

     
  • Tuesday, March 06, 2012 5:40 AM
     
     Proposed Answer
    Sign In to Vote
    0
    No idea. I would have restarted the server and tried again with verbose logging. This is described in the link to Exchange 2007 Rollup by Amit Tank, posted above. Made sure antivirus is disabled as well as third-party agents.

    MCTS: Messaging | MCSE: S+M


     
  • Thursday, March 08, 2012 9:17 AM
    Moderator
     
     
    Sign In to Vote
    0
    Hi Jason,

    Any update for your issue, I also did some tests, it is better restart it over.
    Before you update, confirm the exchange is healthy, such as the needed services are good, you also could run exbpa to confirm it.

    Regards!

    Gavin

    TechNet Community Support

     
  • Friday, March 09, 2012 4:53 AM
     
     Answered
    Sign In to Vote
    0

    I resolved this issue  followed by http://support.microsoft.com/kb/981474

    Actually I couldn't run 

    At the command prompt, type the following command, and then press ENTER:

    <var>exchange_install_folder</var>\bin\ServiceControl.ps1 AfterPatch

    Then I Set-ExecutionPolicy Unrestricted

    Thanks

    Jason

     
  • Friday, March 16, 2012 1:13 PM
     
     
    Sign In to Vote
    0

    I encountered the same thing..and yes, the solution was to execute the Rollup from an *elevated* Exchange Management Shell.