locked
Exchage 2010 mailbox role install error RRS feed

  • Question

  • I am getting an error when i try to install the mailbox role.  I have already run the AD prep commands and i have successfully installed my CAS,HUB and Edge roles.  I am reposting this to make it a question and not a discussion.  Can anyone tell me what this means?  thanks for your help.

    Summary: 6 item(s). 4 succeeded, 1 failed.
    Elapsed time: 00:01:22


    Preparing Setup
    Completed

    Elapsed Time: 00:00:00


    Stopping Services
    Completed

    Elapsed Time: 00:00:01


    Copy Exchange Files
    Completed

    Elapsed Time: 00:00:04


    Restoring services
    Completed

    Elapsed Time: 00:00:00


    Mailbox Role
    Failed

    Error:
    The following error was generated when "$error.Clear();
              $wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
              $manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "Scripts\TSCrimsonManifest.man");
              Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
            " was run: "Process execution failed with exit code 5.".

    Process execution failed with exit code 5.
    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=ms.exch.err.Ex88D115&l=0&cl=cp

    Elapsed Time: 00:01:16


    Finalizing Setup
    Cancelled

     

     

     

    Tuesday, October 26, 2010 2:38 PM

Answers

  • Well after a week of email support i finally upgraded to phone support and the issue was resolved.  The issue was resolved by running the following.

     

    regsvr32.exe DiagnosticCmdletController.dll

    This was in MS database for the error 5 code and not the other piece in the error log.

     

    Just to be safe we went ahead and added the NT service\eventlog to the local event log readers group.  it seems the other error message was dealing with this issue.

     

     

    • Marked as answer by KirkSH Tuesday, November 9, 2010 9:57 PM
    Tuesday, November 9, 2010 9:57 PM

All replies

  • Look in the Exchange Server Setup Log for more detailed information.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Tuesday, October 26, 2010 3:12 PM
  • I already did that and the only section that applies is here and i tried searching the internet for this error and i found nothing.

     

    [10/26/2010 03:15:38.0445] [1] Executing:
              $wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
              $manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "Scripts\TSCrimsonManifest.man");
              Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
           
    [10/26/2010 03:15:38.0492] [2] Active Directory session settings for 'Start-SetupProcess' are: View Entire Forest: 'True', Configuration Domain Controller: 'bugs.cic.scic.com', Preferred Global Catalog: 'duckdodgers.cic.scic.com', Preferred Domain Controllers: '{ bugs.cic.scic.com }'
    [10/26/2010 03:15:38.0492] [2] Beginning processing Start-SetupProcess -Name:'C:\Windows\system32\wevtutil.exe' -Args:'im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man" '
    [10/26/2010 03:15:38.0757] [2] Starting: C:\Windows\system32\wevtutil.exe with arguments: im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man"
    [10/26/2010 03:15:38.0944] [2] Process standard output: **** Warning: Publisher {d46a5e4c-6a53-411f-91f1-d205c8310818} is installed on
    the system. Only new values would be added. If you want to update previous
    settings, uninstall the manifest first.

    [10/26/2010 03:15:38.0944] [2] Process standard error: The publishers and channels are installed successfully. However, we can't enable one or more publishers and channels. Access is denied.

    [10/26/2010 03:15:39.0022] [2] [ERROR] Unexpected Error
    [10/26/2010 03:15:39.0037] [2] [ERROR] Process execution failed with exit code 5.
    [10/26/2010 03:15:39.0068] [2] Ending processing Start-SetupProcess
    [10/26/2010 03:15:39.0068] [1] The following 1 error(s) occurred during task execution:
    [10/26/2010 03:15:39.0068] [1] 0.  ErrorRecord: Process execution failed with exit code 5.
    [10/26/2010 03:15:39.0068] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code 5.
    [10/26/2010 03:15:39.0068] [1] [ERROR] The following error was generated when "$error.Clear();
              $wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
              $manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "Scripts\TSCrimsonManifest.man");
              Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
            " was run: "Process execution failed with exit code 5.".
    [10/26/2010 03:15:39.0068] [1] [ERROR] Process execution failed with exit code 5.
    [10/26/2010 03:15:39.0084] [1] [ERROR-REFERENCE] Id=MailboxComponent___13A8A6B7DE0A4fe3BEB5CB1D86105DA3 Component=EXCHANGE14:\Current\Release\PIM Storage\Content Indexing
    [10/26/2010 03:15:39.0084] [1] Setup is stopping now because of one or more critical errors.
    [10/26/2010 03:15:39.0084] [1] Finished executing component tasks.
    [10/26/2010 03:15:39.0146] [1] Ending processing Install-MailboxRole

     

     

    Tuesday, October 26, 2010 3:51 PM
  • Have you tried running setup.com in a command window as administrator?


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Tuesday, October 26, 2010 5:47 PM
  • same thing happens.
    Tuesday, October 26, 2010 6:31 PM
  • Hi,

     

    To troubleshoot the issue, please perform the following steps.

     

    1. Please refer to the following article to register the DiagnosticCmdletController.dll file and then try to install Mail role.

     

    http://support.microsoft.com/kb/951183

     

    If the error message persists, please move on the next steps.

     

    2. Go to Start/Run and type Installer. Find the Microsoft Full Text Indexing Engine for Exchange. Right-Click, Select to uninstall. Then, please reinstall it again. If the issue persists, please refer to the following steps to uninstall Exchange 2010 completely and reinstall Exchange 2010.

     

    3.  Uninstall all Exchange 2010 components and removed IIS.

    4. Restart the machine and installed pre-requisites for Exchange 2010 for IIS using following command:

     

    Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy -Restart

     

    What’s the result? If the issue persists, please open Event Log and post the error message here for research.

     

    Thanks.


    Novak Wu-MSFT
    Thursday, October 28, 2010 6:59 AM
  • I did all of things you posted.  After step 4 I then ran the setup again.  I got the same error and here is the event viewer.  I would like to post the setup log file also.

    Log Name:      Application
    Source:        MSExchangeSetup
    Date:          10/28/2010 9:01:46 AM
    Event ID:      1002
    Task Category: Microsoft Exchange Setup
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      MailboxDB.cic.scic.com
    Description:
    Exchange Server component Mailbox Role failed.
    Error: Error:
    The following error was generated when "$error.Clear();
              $wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
              $manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "Scripts\TSCrimsonManifest.man");
              Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
            " was run: "Process execution failed with exit code 5.".

    Process execution failed with exit code 5.

     
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchangeSetup" />
        <EventID Qualifiers="0">1002</EventID>
        <Level>2</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2010-10-28T14:01:46.000000000Z" />
        <EventRecordID>2200</EventRecordID>
        <Channel>Application</Channel>
        <Computer>MailboxDB.cic.scic.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Mailbox Role</Data>
        <Data>Error:
    The following error was generated when "$error.Clear();
              $wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
              $manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "Scripts\TSCrimsonManifest.man");
              Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
            " was run: "Process execution failed with exit code 5.".

    Process execution failed with exit code 5.

    </Data>
      </EventData>
    </Event>
    Thursday, October 28, 2010 2:04 PM
  • Hi,

     

    Are all other Exchange 2010 components uninstalled successfully?

     

    Based on the error message, please also perform the following steps.

     

    1. Assure the Remote Registry service and TCP/IP NETBIOS Helper service are started.

    2. Refer to the following article and assure all the system prerequisites are installed. For example, please run the following commands in Windows PowerShell console.

     

    sc config NetTcpPortSharing start=auto

    ServerManagerCmd -ip Exchange-MBX.xml

     

    http://technet.microsoft.com/en-us/library/bb691354(EXCHG.140).aspx

     

    However, if the issue persists, please upload the whole Exchange setup log and Event Log to Skydrive (www.skydrive.live.com), and then share the link to me for research.

     

    Thanks.


    Novak Wu-MSFT
    Friday, October 29, 2010 2:32 AM
  • I tried everything and the same result keeps happening.  i have uploaded the setup log and here is the link

    http://cid-b65975d2a5854327.office.live.com/self.aspx/exchange%20setup%20logs/setup%20log.txt

    Sunday, October 31, 2010 2:17 PM
  • I haven't run into this before, but below is where your setup log gets angry. There appears to be some kind of access issue going on. Did you run setup with the "As an Administrator" option?

     

    [10/26/2010 03:15:38.0944] [2] Process standard error: The publishers and channels are installed successfully. However, we can't enable one or more publishers and channels. Access is denied.

    [10/26/2010 03:15:39.0022] [2] [ERROR] Unexpected Error
    [10/26/2010 03:15:39.0037] [2] [ERROR] Process execution failed with exit code 5.
    [10/26/2010 03:15:39.0068] [2] Ending processing Start-SetupProcess
    [10/26/2010 03:15:39.0068] [1] The following 1 error(s) occurred during task execution:
    [10/26/2010 03:15:39.0068] [1] 0.  ErrorRecord: Process execution failed with exit code 5.
    [10/26/2010 03:15:39.0068] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code 5.
    [10/26/2010 03:15:39.0068] [1] [ERROR] The following error was generated when "$error.Clear();
              $wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
              $manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "Scripts\TSCrimsonManifest.man");
              Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
            " was run: "Process execution failed with exit code 5.".
    [10/26/2010 03:15:39.0068] [1] [ERROR] Process execution failed with exit code 5.
    [10/26/2010 03:15:39.0084] [1] [ERROR-REFERENCE] Id=MailboxComponent___13A8A6B7DE0A4fe3BEB5CB1D86105DA3 Component=EXCHANGE14:\Current\Release\PIM Storage\Content Indexing


    Microsoft Premier Field Engineer, Exchange
    MCSA 2000/2003, CCNA
    MCITP: Enterprise Messaging Administrator 2010
    Former Microsoft MVP, Exchange Server
    My posts are provided “AS IS” with no guarantees, no warranties, and they confer no rights.
    Sunday, October 31, 2010 3:09 PM
  • As Brian mentioned, the issue may occur by incorrect permission. Please assure the current user account has enough privilege to install Mailbox role.

     

    Thanks.


    Novak Wu-MSFT
    Monday, November 1, 2010 2:10 AM
  • Yeah I saw that in the setup log but found nothing on the internet about that error.  i have tried run as administrator and the user is a domain admin  , exchange admin and an admin on the local machine.  Is there anything installed o this machine that would block this error.  What publishers is it trying to enable?
    Monday, November 1, 2010 2:41 AM
  • I also have this in the event viewer log and the firewall is turned off: Log Name: Application Source: MSExchange ADAccess Date: 10/31/2010 9:36:39 PM Event ID: 2152 Task Category: General Level: Error Keywords: Classic User: N/A Computer: Description: Process ExSetupUI.exe (PID=4920). An remote procedure call (RPC) request to the Microsoft Exchange Active Directory Topology service failed with error 1753 (Error 0x6d9 (There are no more endpoints available from the endpoint mapper) 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. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="MSExchange ADAccess" /> <EventID Qualifiers="49156">2152</EventID> <Level>2</Level> <Task>1</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2010-11-01T02:36:39.000000000Z" /> <EventRecordID>2232</EventRecordID> <Channel>Application</Channel> <Computer>MailboxDB.cic.scic.com</Computer> <Security /> </System> <EventData> <Data>ExSetupUI.exe</Data> <Data>4920</Data> <Data>1753</Data> <Data>Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from HrGetServersForRole</Data> </EventData> </Event>
    Monday, November 1, 2010 3:15 AM
  • Please add the user to Schema Admin group and Enterprise Admin group, and then run the installation again. If the issue persists, please also try the suggestions from the link below:

     

    http://forums.msexchange.org/m_1800494656/mpage_1/key_/tm.htm#1800494656

     

    Thanks.
    Novak Wu-MSFT
    Wednesday, November 3, 2010 8:16 AM
  • The user is a schema and enterprise admin and I went through the link and all of that has been checked and it still gives the same error.  I put in a Tech Support Request 3 days ago and MS can't find out what is wrong. 
    Thursday, November 4, 2010 4:21 PM
  • I understand that you have contacted our Phone Support. If there is any update about the case, please share it to us.


    Novak Wu-MSFT
    Friday, November 5, 2010 8:35 AM
  • As of right now we are looking at the permissions dealing with the event viewer.  It seems that the NT Service\Eventlog user hsould be on the following registry keys.  It still hasn't fixed the issue.

     

    <!-- /* Font Definitions */ @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-alt:"Century Gothic"; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-520092929 1073786111 9 0 415 0;} @font-face {font-family:Verdana; panose-1:2 11 6 4 3 5 4 4 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1593833729 1073750107 16 0 415 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman","serif"; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-size:10.0pt; mso-ansi-font-size:10.0pt; mso-bidi-font-size:10.0pt;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.WordSection1 {page:WordSection1;} -->

    HKLM\Software\Microsoft\Windwos\CurrentVersion\Reliability

    HKLM\System\CurrentControlSet\Control\WMI\Autologger\EventLog-Application\

     

    The main problem now is the time zone difference between myself and the tech.  He works nights and i work during the day.  I asked to have that changed to hopefully speed up this process. 

    Friday, November 5, 2010 3:09 PM
  • Hi KirkSH,

     

    Is the issue fixed after contacting our Phone support engineer? If there is any update, please let us know.

     

    Thanks.


    Novak Wu-MSFT
    Tuesday, November 9, 2010 3:02 AM
  • Well after a week of email support i finally upgraded to phone support and the issue was resolved.  The issue was resolved by running the following.

     

    regsvr32.exe DiagnosticCmdletController.dll

    This was in MS database for the error 5 code and not the other piece in the error log.

     

    Just to be safe we went ahead and added the NT service\eventlog to the local event log readers group.  it seems the other error message was dealing with this issue.

     

     

    • Marked as answer by KirkSH Tuesday, November 9, 2010 9:57 PM
    Tuesday, November 9, 2010 9:57 PM
  • To anyone that experiences this issue with the exchange mailbox role failure - we also just experienced this same issue on a brand new install on windows 2008R2 SP1 / Exchange 2010 SP1   ( client currently running an exchange 2003 server ).  

    We received the exact same error that KirkSH reported with the mailbox role install failure.  However in our case the resolution was not to regsvr32 the dll, but as others reported it is definitely a permissions issue.  And it turns out this is a permissions issue which we have seen on an inconsistent basis with many win2008 and win7 installs.

    This permission issue usually manifests itself with the failure of the DHCP client service failure to start - and a restart of the service will display an access denied error.  In our case the DHCP client service on the server was also failing to start which gave us the clue to use the following script to fix both issues:

    Open a cmd prompt with elevated admin permissions  - then enter the following:

    net localgroup Administrators localservice /add

    Press enter and reboot the server.   

    In our case this fixed the dhcp client service failure and also the Exch2010 mailbox role install.

    • Proposed as answer by LawrenceHe Monday, August 3, 2015 4:39 PM
    Thursday, December 8, 2011 1:06 AM
  • This worked for me when trying to install Exchange 2010 SP1

    http://gallery.technet.microsoft.com/office/Exchange-2010-SP1-SP2-c939e791

    Thursday, April 25, 2013 4:56 PM
  • Thanks Toddritt, this worked for me on WinSrvr2012!!
    Friday, December 27, 2013 3:33 PM
  • Thanks ascdew as adding the net localgroup Administrators localservice /add resolved our issue and allowed the Exchange 2010 SP3 mailbox role to install.  The customer had a very extensive default domain policy with many security settings enabled that had to have caused this issue.

    cheers,

    Larry

    Monday, August 3, 2015 4:39 PM
  • Hello,

    We came across this same issue and thanks to following discussion, issue is resolved: https://social.technet.microsoft.com/Forums/exchange/en-US/52a7e8a7-6c87-41e3-99ab-be9846aaec09/exchage-2010-mailbox-role-install-error?prof=required

    We could not install the mailbox role during a new Exchange 2010 SP3 install and tried many of the suggestions in this article.  It turns out the default domain policy was causing this issue and running the below command allowed us to install the Mailbox role.

    net localgroup Administrators localservice /add

    Hope this helps someone else,

    Larry

    • Proposed as answer by LawrenceHe Monday, August 3, 2015 4:41 PM
    Monday, August 3, 2015 4:41 PM