Exchange Installation Error on Mailbox role: Transport Service Step

The error I receive occurs at 47% of the Mailbox Role: Transport Service installation.  The details of the error are as follows:
    Mailbox role: Transport service                                                                  
FAILED
     The following error was generated when "$error.Clear();
          if ($server -eq $null)
            set-ExchangeServerRole -Identity $RoleNetBIOSName -IsProvisionedServer:$true -DomainController $RoleDomainController
        " was run: "Active Directory operation failed on DC1.xxxxxx.xxxxxx.com. This error is not retriable. Additional information: The object cannot be added because the parent is not on the list of possible superiors.
Active directory response: 00002099: NameErr: DSID-0305109C, problem 2005 (NAMING_VIOLATION), data 0, best match of:
        'CN=EXCH-MBOX1,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=AZGT,CN=
Microsoft Exchange,CN=Services,CN=Configuration,DC=xxxxxx,DC=xxxxxx,DC=com'
The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
<SystemDrive>:\ExchangeSetupLogs folder.
Also, when opening the setup log I have this:
[12/26/2012 17:51:25.0809] [1] [ERROR] A naming violation occurred.
[12/26/2012 17:51:25.0809] [1] [ERROR-REFERENCE] Id=ProvisionServerComponent___a16cb82f909348d3a32b9046f3bfb9ba Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[12/26/2012 17:51:25.0809] [1] Setup is stopping now because of one or more critical errors.
[12/26/2012 17:51:25.0809] [1] Finished executing component tasks.
[12/26/2012 17:51:25.0809] [1] Ending processing Install-BridgeheadRole
[12/26/2012 17:51:25.0825] [0] The Exchange Server setup operation didn't complete.  More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[12/26/2012 17:51:25.0825] [0] End of Setup
[12/26/2012 17:51:25.0825] [0] **********************************************
I have done a ton of searches trying to find a resolution to this error and there are two pages with a similar issue for Exchange 2007 but after trying the solutions suggested, the installation still fails with the same error.
http://social.technet.microsoft.com/Forums/en-US/exchangesvrdeploylegacy/thread/dfa9961a-9b20-4c17-ae4d-ebf44c66c18f/
http://exchangetroubleshooting.blogspot.com/2011/05/unable-to-run-preparead-command.html/
Some additional information:
This is a clean installation of Exchange 2013 in a forest that has never had exchange.
The domain and forest preparations run without errors and are at functional level of 2003.
The Exchange server has all prerequisites installed for a Mailbox server role and is running on a VM with Server 2012 as the OS.
This error occurs on other VMs as well that we are trying to implement as mailbox servers in the same forest.
I am running the installation as an enterprise, schema, domain admin.
Thanks for your help in advance.

Yes.  I cleaned out Exchange with ADSIEdit so I could re-run the Prepare Schema, domain and all domains and then re-ran setup to show the output here.  But the install still failed.
PS F:\> .\setup /IacceptExchangeServerLicenseTerms /PrepareSchema
Welcome to Microsoft Exchange Server 2013 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Performing Microsoft Exchange Server Prerequisite Check
    Prerequisite Analysis                                                                            
COMPLETED
Configuring Microsoft Exchange Server
    Extending Active Directory schema                                                                
COMPLETED
The Exchange Server setup operation completed successfully.
PS F:\> .\setup /IacceptExchangeServerLicenseTerms /PrepareAD /OrganizationName:AZGT
Welcome to Microsoft Exchange Server 2013 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Performing Microsoft Exchange Server Prerequisite Check
    Prerequisite Analysis                                                                            
COMPLETED
 Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have b
een detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
 For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.
aspx
Configuring Microsoft Exchange Server
    Organization Preparation                                                                         
COMPLETED
The Exchange Server setup operation completed successfully.
PS F:\> .\setup /IacceptExchangeServerLicenseTerms /PrepareAllDomains
Welcome to Microsoft Exchange Server 2013 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Performing Microsoft Exchange Server Prerequisite Check
    Prerequisite Analysis                                                                            
COMPLETED
Configuring Microsoft Exchange Server
    Prepare Domain Progress                                                                          
COMPLETED
The Exchange Server setup operation completed successfully.
PS F:\>
PS F:\> .\setup /IAcceptExchangeServerLicenseTerms /mode:install /roles:Mailbox /TargetDir:"C:\Program Files\Microsoft\Exchange Server\V15"
Welcome to Microsoft Exchange Server 2013 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Languages
Management tools
Mailbox role: Transport service
Mailbox role: Client Access service
Mailbox role: Unified Messaging service
Mailbox role: Mailbox service
Performing Microsoft Exchange Server Prerequisite Check
    Configuring Prerequisites                                                                        
COMPLETED
    Prerequisite Analysis                                                                            
COMPLETED
Configuring Microsoft Exchange Server
    Preparing Setup                                                                                  
COMPLETED
    Stopping Services                                                                                
COMPLETED
    Copying Exchange Files                                                                           
COMPLETED
    Language Files                                                                                   
COMPLETED
    Restoring Services                                                                               
COMPLETED
    Language Configuration                                                                           
COMPLETED
    Exchange Management Tools                                                                        
COMPLETED
    Mailbox role: Transport service                                                                  
FAILED
     The following error was generated when "$error.Clear();
          if ($server -eq $null)
            set-ExchangeServerRole -Identity $RoleNetBIOSName -IsProvisionedServer:$true -DomainController $RoleDomainCo
ntroller
        " was run: "Active Directory operation failed on DC1.XXXX.XXXX.com. This error is not retriable. Addi
tional information: The object cannot be added because the parent is not on the list of possible superiors.
Active directory response: 00002099: NameErr: DSID-0305109C, problem 2005 (NAMING_VIOLATION), data 0, best match of:
        'CN=EXCHMBOX1,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=AZGT,CN=
Microsoft Exchange,CN=Services,CN=Configuration,DC=XXXX,DC=XXXX,DC=com'
The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
<SystemDrive>:\ExchangeSetupLogs folder.
PS F:\>

Similar Messages

  • Exchange 2013 SP1 Installation Error in "Mailbox Role: Transport service"

    I tried an installation last week on a Windows Server 2008 R2 but was unable to get it to work. With the value of hindsight, I am inclined to think the error was more with the Web Site making EAC unavailable. I subsequently got it installed in my personal
    lab environment by creating a VM with a fresh install of Windows Server 2008 R2 SP1. 
    With this information I then went back to the customer's site and installed a clean version of Windows Server 2008 R2 SP1 in a virtual machine under Hyper-V. After installing all the prerequisites the install appeared to be going just fine but then in failed
    in Step 7 with the following error:
    The following error was generated when "$error.Clear();
    if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) )
    Update-RmsSharedIdentity -ServerName $RoleNetBIOSName
    " was run: "Database is mandatory on UserMailbox.".
    I know MS Exchange hides most of its information in AD so my suspicion is that the failed install on the real server has left some residual information in AD. Note that the original install on the real machine won't uninstall because the prior install attempt
    hasn't finished.
    The relevant part of the Exchange Setup Log is:
    [07/22/2014 14:22:57.0593] [2] Active Directory session settings for 'Update-RmsSharedIdentity' are: View Entire Forest: 'True', Configuration Domain Controller: 'AWSDC.aws.local', Preferred Global Catalog: 'AWSDC.aws.local', Preferred Domain Controllers: '{
    AWSDC.aws.local }'
    [07/22/2014 14:22:57.0593] [2] User specified parameters:  -ServerName:'EXCHANGE'
    [07/22/2014 14:22:57.0593] [2] Beginning processing Update-RmsSharedIdentity
    [07/22/2014 14:22:58.0031] [2] RMS Shared Identity user 'CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042,CN=Users,DC=aws,DC=local' (originating server = 'AWSDC.aws.local') is being linked to computer 'CN=EXCHANGE,CN=Computers,DC=aws,DC=local' (originating
    server = 'AWSDC.aws.local').
    [07/22/2014 14:22:58.0156] [2] [ERROR] Database is mandatory on UserMailbox.
    [07/22/2014 14:22:58.0156] [2] Ending processing Update-RmsSharedIdentity
    [07/22/2014 14:22:58.0156] [1] The following 1 error(s) occurred during task execution:
    [07/22/2014 14:22:58.0156] [1] 0.  ErrorRecord: Database is mandatory on UserMailbox.
    [07/22/2014 14:22:58.0156] [1] 0.  ErrorRecord: Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.
       at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
       at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.Link()
       at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
    [07/22/2014 14:22:58.0156] [1] [ERROR] The following error was generated when "$error.Clear(); 
              if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) )
                Update-RmsSharedIdentity -ServerName $RoleNetBIOSName
            " was run: "Database is mandatory on UserMailbox.".
    [07/22/2014 14:22:58.0156] [1] [ERROR] Database is mandatory on UserMailbox.
    Does anyone have suggestions about what to do with ADSI Edit to fix the problems?
    I think I am getting close to having a working Exchange!!

    Hi,
    Agree with Amit's suggestion. Please use the following cmdlet to re-home the arbitration mailbox which does not have database attribute stamped and check the result.
    Set-Mailbox "FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042" -Arbitration -Database "xxx"
    Hope it helps.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Echange 2013 Installation Failing at Mailbox Role: Transport Service - 97%

    Hi all, let me just preface by saying thank you very much all your time, help, and patience!  
    So I've gone through the Exchange 2013 deployment guide, have installed all the pre-requisites, and am now trying to install Exchange 2013 CU7 on (2) 2008 R2 Enterprise SP1 servers.  Unfortunately it is failing on both of them at the Mailbox
    Role: Transport Service - 97% with the following error:
    Error:
    The following error was generated when "$error.Clear(); 
              $maxWait = New-TimeSpan -Minutes 8
              $timeout = Get-Date;
              $timeout = $timeout.Add($maxWait);
              $currTime = Get-Date;
              $successfullySetConfigDC = $false;
              while($currTime -le $timeout)
                $setSharedCDCErrors = @();
                try
                  Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
                  $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
                  if($successfullySetConfigDC)
                    break;
                  Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
                catch
                  Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
                Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
                Start-Sleep -Seconds 30;
                $currTime = Get-Date;
              if( -not $successfullySetConfigDC)
                Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
            " was run: "System.Exception: Unable to set shared config DC.
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
       at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    I've seen and heard the suggestions about enabling IPv6 on the servers as well as the Domain Controllers which I've done to no avail.  We do not have IPv6 addresses available on our network as we use IPv4 space, but I've heard just having the
    IPv6 adapter disabled is a lot of times the issue.  So the adapters are set to DHCP even though there's no IPv6 address for it to grab.  The 2008 R2 servers that I'm trying to install Exchange 2013 on are VMs on ESX.  Will the
    install fail even if it offers to pick up the installation where I left off?  Do I need to completely start from scratch?  Any help would be wonderful!

    Hi,
    Please verify whether the port 3268 listen on DC.
    Please try to enable GC role on all DCs.
    Then restart Exchange server, try to find whether Event 2080 exists with all DCs.
    Then try to re-install Exchange Server 2013 CU7.
    Thanks
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Mavis Huang
    TechNet Community Support

  • Exchange 2013 CU7 Installation crash on Mailbox role: Transport Service!!

    Hi
    I need some help, very urgent.
    I started cu7 Installation, and in the middle the Installation failed:
    Error:
    The following error was generated when "$error.Clear();
                # Apply XML Transforms to FIPS configuration file if schema changed
                Write-ExchangeSetupLog -Info "Applying XML Transforms to FIPS configuration";
                $FipsBinPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\bin");
                [Reflection.Assembly]::LoadFile([System.IO.Path]::Combine($FipsBinPath, "FSCConfigurationServerInterfaces.dll"));
                [Reflection.Assembly]::LoadFile([System.IO.Path]::Combine($FipsBinPath, "FSCConfigSupport.dll"));
                $configServer = New-Object Microsoft.FSC.Configuration.ConfigManagerClass;
                if(! $configServer)
                  Write-ExchangeSetupLog -Error "Configuration Server object could not be created.";
                else
                  try
                    $configServer.Upgrade();
                    Write-ExchangeSetupLog -Info "Configuration.xml was upgraded successfully";
                  catch
                    Write-ExchangeSetupLog -Error "Upgrade of Configuration.xml was unsuccessfull, $_";
                  # Stop the process if it is still running
                  # We silently continue because if process has already exited, Stop-Process will throw error
                  # Error is non-terminating and so can be suppressed
                  Stop-Process -processname FSCConfigurationServer -Force -ErrorAction SilentlyContinue;
              " was run: "System.Exception: Upgrade of Configuration.xml was unsuccessfull, Exception calling "Upgrade" with "0" argument(s): "Root element is missing."
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
       at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    I couldn't find any information about that
    Any sugggestion what I can do?
    Regards
    Peter

    Hi,
    If it is unable to start Transport service, please try the following method to solve this issue.
    Go to “C:\Program Files\Microsoft\Exchange Server\V15\FIP-FS\Data”
    Deleted the file "Configuration.xml" and renamed "Configuration.xml.back" to Configuration.xml.
    Then try to re-install Exchange Mailbox Server.
    Note: remember to back up the file "Configuration.xml" and "Configuration.xml.back"
    Best Regards.
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Lynn-Li
    TechNet Community Support

  • Installation of Exchange 2013 Failed on Mailbox Role Transport Service

    Hi All,
    Getting this error when trying to install a new exchange 2013 server. Thanks in advance
    Error:
    The following error was generated when "$error.Clear();
              if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) )
                Update-RmsSharedIdentity -ServerName $RoleNetBIOSName
            " was run: "Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.
       at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
       at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientObjectSession.Save(ADRecipient instanceToSave)
       at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.Link()
       at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

    Hi,
    This problem occurs because the federated built-in e-mail account that links to the computer account no longer exists. Or, the federated built-in e-mail account in the AD
     directory service is corrupted.
    Please try to follow these steps to solve this problem.
        1. Remove the FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 e-mail account by using the ADSIEDIT tool. To do this, follow these steps:
    Click Start, click Run, type adsiedit.msc, and then click
    OK.
    Locate the Default Naming Context node, and then locate to the
    CN=Users container.
    Locate and then right-click the CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 container. Then, click
    Delete.
        2. Rerun the Exchange Server 2013 Mailbox role setup application.
        3. Create a new federated e-mail account by using the following command:
    New-Mailbox -Arbitration -Name FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 -UserPrincipalName FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042@<Default_Accepted_Domain>
    If this issue persistes, please let me know.
    Best Regards.

  • Trying to Install Exchange 2013 SP1 on Windows Server 2012 R2 but getting an error on mailbox role install

    On Step 1 of 7, the "Mailbox role: Client Access service," I got an error during installing:
    Error:
    The following error was generated when "$error.Clear(); 
              Install-ExchangeCertificate -WebSiteName "Exchange Back End" -services "IIS, POP, IMAP" -DomainController $RoleDomainController -InstallInTrustedRootCAIfSelfSigned $true
              if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
                Install-AuthCertificate -DomainController $RoleDomainController
            " was run: "Could not grant Network Service access to the certificate with thumbprint 8FCF29D8F3A4D8E3D649BF4231DC9B4641D5A077 because a cryptographic exception was thrown.".
    I couldn't find help anywhere on this. Can someone help me? If you need any more info, please let me know ^_^

    Try the solution provided in this thread:
    https://social.technet.microsoft.com/Forums/exchange/en-US/e4b23442-e3c9-4611-9fde-fac848ca217b/error-could-not-grant-network-service-access-to-the-certificate-with-thumbprint?forum=exchangesvrdeploy
    Thanks,
    MikeV
    MCSE 2012
    If the above solutions doesn't work, try moving the certificate with the thumbprint identified in the error, to the Trusted Root Certification Authority folder
    Thanks,
    MikeV
    MCSE 2012

  • Installation Error with Contacts Group DS & Servic...

    Hello,
    just recieved my new N85 and installed the PC Suit 7.1 on the PC.
    If i start PC Suit and at example kalendar, pc suit asks me for installing contacts group DS Plugin an to update service controllers from version 1.00(0) to 1.43(0). My N85 prompts everytime and asks me if i want, so if i confirm installation, it ends everytime after a few seconds with an installation error. - cannot install :-(
    I read something about deinstalling the two older plugins first may possibly help, but i can't find it anywhere. Not in apps-manager (german version=program-manager). But it must be installed, because he seems to find version 1.00(0) on the N85.
    can someone help me to solve this problem?
    Solved!
    Go to Solution.

    Good point, that happened to me on my previous phone, N80. Can't remember what the problem was but it was re-introduced. I would say backing up and restoring Contacts, Calendar and Notes, however, would probably not reintroduce problem. Maybe you could do a reset, upgrade the plug-ins, then restore your personal information?
    If you found this post helpful, please click on the green "Kudos!" star. Cheers!

  • Exchange 2010 - Error setting a new transport rule for email disclaimer

    Hi
    Trying to setup some additional email disclaimer rules on Hub transport under Org Config on exchange 2010. We allready have a few and they work ok, however we are trying to replace this woth some alternate ones and are getting the error
    The length of the property is too long. the maximum length is 8192 and the length of the value provided is 8522.
    Most of this length comes from the html code we are inserting into the disclaimer. I've reduced it by about as much as i can but it's still too large. Does anybody have any suggestions or know if it;s possible to increase the 8192 sixze limit ?
    Regards
    Roger

    Hi Roger,
    For AD replication packet the ideal size is 8K. Or the above error may occur due to build/design issues.
    You can eliminate this size related issue by splitting the large rule into multiple rules. This size limit is Per Rule and does not add up for all rules. 

  • Error in step 8 - transport service

    hi there,
    i need some help here... in the instalation of exchange server 2012 apear this error on mailbox roles: transport service.
    how i renew the certificate? that the program ask...
    thanks.
    Error:
    The following error was generated when "$error.Clear(); 
              Install-ExchangeCertificate -services IIS -DomainController $RoleDomainController
              if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
                Install-AuthCertificate -DomainController $RoleDomainController
            " was run: "System.Security.Cryptography.CryptographicException: The certificate is expired.
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

    Hi John,
    Based on my experience, this error usually is caused by incorrect system time.
    And as we know first place to check is ExchangeSetup.log, open the log file and press Ctrl+End, you will reach the end of the file the place where our error will be available. Then check the
    validity of certificate(Start time and End time), if the certificate is valid, please make sure your system time is correct.
    And if the certificate is expired, you need to renew the certificate.
    Click the link below for more information:
    Renewing Certification Authorities
    http://technet.microsoft.com/en-us/library/cc962077.aspx
    Hope it can be helpful.
    Best regards,
    Eric

  • Exchange Server crashed while installing Transport service

    Hi!
    Having some massive issues with the initial install of Exchange 2013 SP1 on Windows Server 2012 Standard.
    Basically, it has crashed multiple times and usually at the end of the install, so I end up with a partial installation which then needs to be manually removed as it won't remove it via the Programs and Features option.
    I have finally got the error after doing the install from the powershell.
    Take note, I am part of the Schema Groups and Domain Admins and have fulfilled the Exchange 2013  prerequisites.
    The server came from Dell with Windows 2012 set up already, Ive just downloaded the Exchange 2013 iso from microsoft and mounted it.
    I've tried also running the setup.exe as administrator (I am also logged in as the domain administrator)
    The last command that I ran from power shell is this.
    Setup.exe /mode:Install /role:ClientAccess,Mailbox /DomainController:SERVER /IAcceptExchangeServerLicenseTerms
    Then I get the below error, regardless of the error the server has 16gb of memory with not much else going on, the hard drives have plenty of space so no issues there either.
    Error:
    The following error was generated when "$error.Clear(); 
                Write-ExchangeSetupLog -Info "Setting up FIPS configuration based on Exchange Install Path";
                $FipsDataPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Data");
                $FipsEnginesPath = [System.IO.Path]::Combine($FipsDataPath, "Engines");
                Write-ExchangeSetupLog -Info "Loading FipFs snapin";
                Add-PsSnapin Microsoft.Forefront.Filtering.Management.PowerShell -ErrorAction SilentlyContinue;
                Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:TraceFile" -Value $FipsDataPath -Confirm:$false
                Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:Engines" -Value $FipsEnginesPath -Confirm:$false
                # Copy Microsoft Engine to Engines folder during the install
                $FipsBinPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Bin");
                $MicrosoftEngineSourcePath = [System.IO.Path]::Combine($FipsBinPath, "Engine\Microsoft");
                $MicrosoftEngineDestinationPath = [System.IO.Path]::Combine($FipsEnginesPath, "amd64\Microsoft");
                $MicrosoftEngineExists = Test-Path $MicrosoftEngineDestinationPath
                if(! $MicrosoftEngineExists)
                  Robocopy $MicrosoftEngineSourcePath $MicrosoftEngineDestinationPath /S /COPYALL
              " was run: "Creating an instance of the COM component with CLSID {2DC947D7-A2DC-4276-A554-891346CE2032} from the IClassFactory failed due to the following error: 8007000e Not enough storage is available to complete
    this operation. (Exception from HRESULT: 0x8007000E (E_OUTOFMEMORY)).".
    Error:
    The following error was generated when "$error.Clear(); 
                Write-ExchangeSetupLog -Info "Setting up FIPS configuration based on Exchange Install Path";
                $FipsDataPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Data");
                $FipsEnginesPath = [System.IO.Path]::Combine($FipsDataPath, "Engines");
                Write-ExchangeSetupLog -Info "Loading FipFs snapin";
                Add-PsSnapin Microsoft.Forefront.Filtering.Management.PowerShell -ErrorAction SilentlyContinue;
                Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:TraceFile" -Value $FipsDataPath -Confirm:$false
                Set-ConfigurationValue -XPath "/fs-conf:Configuration/fs-sys:Machine/fs-sys:Paths/fs-sys:Engines" -Value $FipsEnginesPath -Confirm:$false
                # Copy Microsoft Engine to Engines folder during the install
                $FipsBinPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\Bin");
                $MicrosoftEngineSourcePath = [System.IO.Path]::Combine($FipsBinPath, "Engine\Microsoft");
                $MicrosoftEngineDestinationPath = [System.IO.Path]::Combine($FipsEnginesPath, "amd64\Microsoft");
                $MicrosoftEngineExists = Test-Path $MicrosoftEngineDestinationPath
                if(! $MicrosoftEngineExists)
                  Robocopy $MicrosoftEngineSourcePath $MicrosoftEngineDestinationPath /S /COPYALL
              " was run: "Creating an instance of the COM component with CLSID {2DC947D7-A2DC-4276-A554-891346CE2032} from the IClassFactory failed due to the following error: 8007000e Not enough storage is available to complete
    this operation. (Exception from HRESULT: 0x8007000E (E_OUTOFMEMORY)).".
    The 2 things that I had to fix during install was that the registry was missing the FIPS entry, once I had manually created that entry again the Exchange installation got up installing the Mailbox role: Transport Service and then errored with the above message.
    As this is a fairly new product theres not much information out there.
    Any Help will be appreciated.
    Thanks,
    Cameron

    Hi 
    Since you have mentioned that It has crashed multiple times its not successful its better to try the installation on a different PC or you can try formatting the box and proceed with the exchange  installation since its a new Exchange 2013 installation.
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you

  • Mailbox Role Setup Error

    Hello, when trying to install the Mailbox Role: Transport Service, I get the following error:
    Error:
    The following error was generated when "$error.Clear();
    configure-WSManIISHosting -EnableKerberosModule;
    " was run: "Application 'PowerShell' doesn't exist in the default Web site in 'C:\Windows\system32\inetsrv\config\ApplicationHost.Config'. Make sure the application isn't deleted from the default Web site.".
    Any ideas how to resolve this? I've tried everything.
    Thank you.

    Sure. Here is the log.
    [01/27/2015 14:17:29.0001] [1] Processing component 'WSMan IIS Hosting Configuration' (WSMan IIS Hosting Configuration Component).
    [01/27/2015 14:17:29.0001] [1] Executing:
    configure-WSManIISHosting -EnableKerberosModule;
    [01/27/2015 14:17:29.0016] [2] Active Directory session settings for 'Configure-WSManIISHosting' are: View Entire Forest: 'True', Configuration Domain Controller: 'WIN-M9G032Q55DG', Preferred Global Catalog: 'WIN-M9G032Q55DG', Preferred Domain Controllers:
    '{ WIN-M9G032Q55DG }'
    [01/27/2015 14:17:29.0016] [2] Beginning processing configure-WSManIISHosting -EnableKerberosModule:'True'
    [01/27/2015 14:17:29.0047] [2] Changing the start type of WINRM service to Automatic Delayed...
    [01/27/2015 14:17:29.0047] [2] Starting WINRM service...
    [01/27/2015 14:17:29.0047] [2] Checking required files...
    [01/27/2015 14:17:29.0125] [2] Checking required registry keys...
    [01/27/2015 14:17:29.0125] [2] Checking current IIS configuration...
    [01/27/2015 14:17:29.0141] [2] [ERROR] Application 'PowerShell' doesn't exist in the default Web site in 'C:\Windows\system32\inetsrv\config\ApplicationHost.Config'. Make sure the application isn't deleted from the default Web site.
    [01/27/2015 14:17:29.0141] [2] [ERROR] Application 'PowerShell' doesn't exist in the default Web site in 'C:\Windows\system32\inetsrv\config\ApplicationHost.Config'. Make sure the application isn't deleted from the default Web site.
    [01/27/2015 14:17:29.0141] [2] Ending processing configure-WSManIISHosting
    [01/27/2015 14:17:29.0157] [1] The following 1 error(s) occurred during task execution:
    [01/27/2015 14:17:29.0157] [1] 0. ErrorRecord: Application 'PowerShell' doesn't exist in the default Web site in 'C:\Windows\system32\inetsrv\config\ApplicationHost.Config'. Make sure the application isn't deleted from the default Web site.
    [01/27/2015 14:17:29.0157] [1] 0. ErrorRecord: System.InvalidOperationException: Application 'PowerShell' doesn't exist in the default Web site in 'C:\Windows\system32\inetsrv\config\ApplicationHost.Config'. Make sure the application isn't deleted from the
    default Web site.
    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
    at Microsoft.Exchange.Management.Deployment.ConfigureWSManIISHosting.CheckIISConfigurationFile()
    at Microsoft.Exchange.Management.Deployment.ConfigureWSManIISHosting.InternalProcessRecord()
    at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
    [01/27/2015 14:17:29.0157] [1] [ERROR] The following error was generated when "$error.Clear();
    configure-WSManIISHosting -EnableKerberosModule;
    " was run: "Application 'PowerShell' doesn't exist in the default Web site in 'C:\Windows\system32\inetsrv\config\ApplicationHost.Config'. Make sure the application isn't deleted from the default Web site.".
    [01/27/2015 14:17:29.0157] [1] [ERROR] Application 'PowerShell' doesn't exist in the default Web site in 'C:\Windows\system32\inetsrv\config\ApplicationHost.Config'. Make sure the application isn't deleted from the default Web site.
    [01/27/2015 14:17:29.0157] [1] [ERROR-REFERENCE] Id=WSManIISHostingConfigurationComponent___5cd9e3f8000e4019bb27b9ffc70ab482 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    [01/27/2015 14:17:29.0157] [1] Setup is stopping now because of one or more critical errors.
    [01/27/2015 14:17:29.0157] [1] Finished executing component tasks.
    [01/27/2015 14:17:29.0157] [1] Ending processing Install-BridgeheadRole
    [01/27/2015 14:17:32.0199] [0] End of Setup
    [01/27/2015 14:17:32.0199] [0] **********************************************
    Here is the Ps1:
    # Component tasks
    # Tasks for 'WSMan IIS Hosting Configuration' component
    # [ID = WSManIISHostingConfigurationComponent___5cd9e3f8000e4019bb27b9ffc70ab482, Wt = 1, isFatal = True] "WSMan IIS Hosting Configuration Component"
    1/27/2015 9:17:29 AM:
    configure-WSManIISHosting -EnableKerberosModule;

  • Exchange 2013 CU 6 update fails on transport service

    i ran the update and it keeps getting the following error and i cannot find any info on the error
    Exchange Server component Mailbox role: Transport service failed.
    Error: Error:
    The following error was generated when "$error.Clear();
              $feVdirName = "PowerShell (Default Web Site)";
              $beVdirName = "PowerShell (Exchange Back End)";
              $vdirName = "PowerShell";
              $InternalPowerShellUrl="http://" + $RoleFqdnOrName + "/powershell";
              get-PowerShellVirtualDirectory -ShowMailboxVirtualDirectories -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $beVdirName -or $_.Name -eq $feVdirName } | remove-PowerShellVirtualDirectory
    -DomainController $RoleDomainController;
              new-PowerShellVirtualDirectory $vdirName -Role Mailbox -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$true -RequireSSL:$true -WebSiteName "Exchange Back
    End" -Path ($RoleInstallPath + "ClientAccess\PowerShell-Proxy");
              new-PowerShellVirtualDirectory $vdirName -Role Mailbox -InternalUrl $InternalPowerShellUrl -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$false -RequireSSL:$false
    -WebSiteName "Default Web Site" -AppPoolId "MSExchangePowerShellFrontEndAppPool";
            " was run: "System.ArgumentException: The virtual directory 'PowerShell' already exists under 'MST-MAIL1.fibigroup.net/Exchange Back End'.
    Parameter name: VirtualDirectoryName
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalValidate()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

    Hi,
    Thanks for your response.
    The error explains that the virtual directory 'PowerShell' already exists, so we need to remove the 'PowerShell' under "Default Web Site" and "Exchange Back End" firstly, and then continue to upgrade the Exchange 2013 CU6.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Failing installation - Missing system mailbox accounts

    I had installed Exchange 2013 SP1 and it seemed to be working correctly. I installed CU7 and everything fell apart. Massive errors all over the place. I gave up and removed all mailboxes, removed the databases, and uninstalled Exchange 2013.  I then
    went into ADUC and manually removed the remaining system mailboxes.
    I reloaded a brand new install of Server 2012 R2 (same name as previous exchange 2013 install) and I went to install Exchange 2013 again.  I ran it from the GUI and did not run /PrepareSchema or /PrepareAD in advance.  My understanding was that
    running the GUI would do this and since the prepare schema switch in particular is unnecessary since the schema was already updated from the previous install I did not worry about it.
    Install fails with:
    Error:
    The following error was generated when "$error.Clear();
              if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) )
                Update-RmsSharedIdentity -ServerName $RoleNetBIOSName
            " was run: "Microsoft.Exchange.Management.Tasks.RmsSharedIdentityUserNotFoundException: RMS Shared Identity user FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 not found.
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow)
       at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.Link()
       at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    So yes the federated mailbox referenced above does not exist.  As I said I thought the install would have run the /PrepareAD steps and created it.  So I try and run the setup /PrepareAD myself to generate the system mailboxes and that fails:
    PS C:\Users\administrator.mydomain.local\Downloads\Exchange2013cu7> .\setup /PrepareAD  /IacceptExchangeServerLicenseTerms
    Welcome to Microsoft Exchange Server 2013 Cumulative Update 7 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Mailbox role: Transport service
    Mailbox role: Client Access service
    Mailbox role: Unified Messaging service
    Mailbox role: Mailbox service
    Client Access role: Front End Transport service
    Client Access role: Client Access Front End service
    Performing Microsoft Exchange Server Prerequisite Check
        Configuring Prerequisites                                                                        
    COMPLETED
        Prerequisite Analysis                                                                            
    FAILED
         A Setup failure previously occurred while installing the HubTransportRole role. Either run Setup again for just thi
    s role, or remove the role using Control Panel.
         For more information, visit:
    http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.InstallWatermar
    k.aspx
    The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
    <SystemDrive>:\ExchangeSetupLogs folder.
    So looking in the ExchangeSetup.log I find this:
    [12/22/2014 23:32:27.0524] [1] User specified parameters:
    [12/22/2014 23:32:27.0524] [1] Beginning processing Get-SendConnector
    [12/22/2014 23:32:27.0587] [1] Searching objects of type "SmtpSendConnectorConfig" with filter "$null", scope "SubTree" under the root "Administrative Groups".
    [12/22/2014 23:32:27.0587] [1] Request filter in Get Task: (&(objectCategory=msExchRoutingSMTPConnector)(|(&(msExchVersion<=1125899906842624)(!(msExchVersion=1125899906842624)))(!(msExchVersion=*)))).
    [12/22/2014 23:32:27.0665] [1] Previous operation run on domain controller 'DC1.mydomain.local'.
    [12/22/2014 23:32:27.0665] [1] Preparing to output objects. The maximum size of the result set is "Unlimited".
    [12/22/2014 23:32:27.0696] [1] Ending processing Get-SendConnector
    [12/22/2014 23:32:27.0696] [1] Evaluated [Rule:SendConnectorException] [HasException:False] [Value:"False"] [ParentValue:"System.DirectoryServices.ResultPropertyCollection"] [Thread:41] [Duration:00:00:09.9289411]
    [12/22/2014 23:32:27.0696] [1] Finished [Rule:SendConnectorException] [Duration:00:00:09.9444335]
    [12/22/2014 23:32:27.0712] [1] Evaluated [Setting:PowerShellExecutionPolicy] [HasException:False] [Value:"False"] [ParentValue:"<NULL>"] [Thread:45] [Duration:00:00:09.9445571]
    [12/22/2014 23:32:27.0712] [1] Finished [Setting:PowerShellExecutionPolicy] [Duration:00:00:09.9445571]
    [12/22/2014 23:32:27.0712] [1] Evaluated [Rule:PowerShellExecutionPolicyCheckSet] [HasException:False] [Value:"False"] [ParentValue:"<NULL>"] [Thread:45] [Duration:00:00:09.9445571]
    [12/22/2014 23:32:27.0712] [1] Finished [Rule:PowerShellExecutionPolicyCheckSet] [Duration:00:00:09.9445571]
    [12/22/2014 23:32:27.0727] [1] Finished [Analysis:Prereq] [Duration:00:00:10.2101752]
    [12/22/2014 23:32:27.0743] [1] Failed [Rule:InstallWatermark] [Message:A Setup failure previously occurred while installing the HubTransportRole role. Either run Setup again for just this role, or remove the role using Control Panel.]
    Stuck.  Can't finish install, can't uninstall.
    I should also mention. I have a working Exchange 2007 server in the environment. 

    Holy guacamole!  I was able to finish the setup.
    When I ran setup /PrepareAD I also ran /PrepareSchema and /PrepareDomain but I did it in the usual order: PrepareSchema first, PrepareAD second and PrepareDomain third. 
    I figured, “can’t hurt, might help.”  The schema theoretically should have already been extended when I installed CU7 onto my SP1 install. But as I posted here:
    https://social.technet.microsoft.com/Forums/office/en-US/2de87b3f-52e4-4c1c-8f18-421f948d41c3/seemingly-successful-install-of-exchange-2013-sp1-turns-into-many-errors-in-event-logs-after-upgrade?forum=exchangesvrdeploy#697e5abf-180b-4d78-b841-b5a46cb1ee63
    that did not go well.
    I noticed lots of event log entries on the DC saying the schema had been modified. 
    That may be normal even if running PrepareSchema again but I wonder if it was not an indication that the schema had actually not been extended from SP1 to CU7 after all.
    What was common to both of these problematic installs of CU7 was that I had simply run setup and not done the preinstall switches. 
    The Exchange installation wizard is supposed to do this but I am now wondering if the wizard for CU7 actually does not. 
    If CU7 had made the configuration changes on the exchange server without doing whatever changes were necessary from the preinstall switches, that might help explain why it all went wobbly (in the technical sense) after the CU7 install on my first server.
    Sadly though I see many of the same error messages in the event log that I was seeing on my first install.

  • Error During install Exchange 2013 through Powershell on Server 2012 "Mailbox role: Client Access service"

    Dear all
    During install Exchange 2013 through Powershell on Server 2012 I got this error in Mailbox role: Client Access service :
    The following error was generated when "$error.Clear();
    $BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
    new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController
    set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
    " was run: "An error occurred while creating the IIS virtual directory 'IIS://MONAMBX2.mona.local/W3SVC/2/ROOT/o
    wa' on 'MONAMBX2'.".
    The following error was generated when "$error.Clear();
    $BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
    new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController
    set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
    " was run: "The operation couldn't be performed because object 'MONAMBX2\OWA (Exchange Back End)' couldn't be fo
    und on 'MonaDc1.mona.local'.".
    Any advice please !!

    I can't answer your question but I had a similar issue when I was trying to move our mailbox database off the C: drive.  Our environment still has an Exchange 2007 server in it and when I was trying to move the database on the 2013 server, I would get
    error messages saying the database does not exist.  It seemed like it was trying to move the database on the 2007 server from the similar error messages that I was getting.  To get around it, I deleted the database and created a new one on the drive
    where we wanted it.
    I discovered this when I was configuring the Antispam settings.  I deleted our 2007 settings, added them to the 2013 shell, the settings appeared on our 2007 server.  The shell on 2013 was making changes to 2007.
    I'm not sure if there is a "Get|Set or New" command that I/we should be using when this happens.  Or maybe my issues will be fixed if I just remove the Exchange 2007 server?  I'm not ready to do that yet because I can't configure the spam filtering
    on 2013 yet with its shell not being able to make the changes that we need.
    I don't know if your environment is in coexistence mode like mine.
    Hopefully someone else out there has an answer or can tell us when/how the shell can make the appropriate changes to the 2013 server.  Does this happen after the 2007 server is removed?

  • Exchange Passive Node Failover - Getting An Error While Installing Mailbox Role in Passive Node

    Hello,
    I was having Exchange 2007 CCR in Two Nodes, Due to hardware fail my passive node is crash. Now i want to recover my passive node i follow this steps
     http://www.msexchange.org/articles-tutorials/exchange-server-2007/high-availability-recovery/re-installing-cluster-nodes-exchange-2007-ccr-based-mailbox-server-setup-part2.html
    Evict the Damaged Node from the Cluster
    Install Windows Server 2003 on the replacement node
    Use the same drive letters and folder structure for the database and log file drives
    Install the same service packs & software updates as the cluster active node
     Use a unique computer name
    for the replacement node
    Join the replacement node to the domain
    Add the replacement node to the Cluster using Cluster Administrator
    When im installing Passive node i'm getting an error when mailbox role is installing "Object refernce not set to an instance of an object"
    Please Advise

    [1/6/2015 12:28:31 PM] [1] Processing component 'All Roles Precompile Management Binaries' (Pre-compiling management binaries.).
    [1/6/2015 12:28:31 PM] [1] Executing '$fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\microsoft.Exchange.Rpc.dll"); precompile-ManagedBinary -BinaryName $fullPath;', handleError = False
    [1/6/2015 12:28:31 PM] [2] Launching sub-task '$error.Clear(); $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\microsoft.Exchange.Rpc.dll"); precompile-ManagedBinary -BinaryName $fullPath;'.
    [1/6/2015 12:28:31 PM] [2] Beginning processing.
    [1/6/2015 12:28:31 PM] [2] Starting: C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\ngen.exe arguments: install "C:\Program Files\Microsoft\Exchange Server\bin\microsoft.Exchange.Rpc.dll" /verbose
    [1/6/2015 12:28:41 PM] [2] Process standard output: Microsoft (R) CLR Native Image Generator - Version 2.0.50727.42
    Copyright (C) Microsoft Corporation 1998-2002. All rights reserved.
    Installing assembly C:\Program Files\Microsoft\Exchange Server\bin\microsoft.Exchange.Rpc.dll
    Compiling 3 assemblies:
        Compiling assembly C:\Program Files\Microsoft\Exchange Server\bin\microsoft.Exchange.Rpc.dll ...
    Microsoft.Exchange.Rpc, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
     Source MVID: {A77F7B45-C91D-4B18-94DB-D563EB0D1F84}
     Source HASH: 1c8367b62a1131417ed73fe3e751c3828b38a5a1
     NGen GUID sign: {66199311-02ED-4287-D82B-3AB75FED547C}
     OS:  WinNT
     Processor: amd64
     Runtime: 2.0.50727.926
     mscorwks.dll: TimeStamp=46D8E98C, CheckSum=009E1083
     Flags:  
     Scenarios:  <no debug info> <no debugger> <no profiler> <no instrumentation>
     Granted set: <PermissionSet class="System.Security.PermissionSet"
    version="1"
    Unrestricted="true"/>
     File:  C:\WINDOWS\assembly\NativeImages_v2.0.50727_64\Microsoft.Exchange.#\11931966ed028742d82b3ab75fed547c\Microsoft.Exchange.Rpc.ni.dll
     Dependencies:
      mscorlib, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{F107DDB2-5499-4106-A503-4AA24B5E4A4F}
       Sign:c2219dc660a826c6a3b4bc7e85de9105086db23d
       Hardbound Guid:{687FCFEB-5108-AC0C-E27B-D065DA0AE3B9}
      Microsoft.VisualC, Version=8.0.0.0, PublicKeyToken=b03f5f7f11d50a3a:
       Guid:{1483EE61-9ACA-4942-AC0A-402784F7E1B9}
       Sign:40be9432586208c4bb49866ff7ea31bc16665a6b
      System, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{71EFBB87-F94E-4397-8D46-76BB8FF60448}
       Sign:d464740812db1d60e65c51092d09f67028463192
       Hardbound Guid:{D5F143E5-1AD8-CB94-12D2-3D4AFFC46E22}
        Finished compiling assembly C:\Program Files\Microsoft\Exchange Server\bin\microsoft.Exchange.Rpc.dll ...
        Compiling assembly Microsoft.VisualC, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a ...
    Microsoft.VisualC, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
     Source MVID: {1483EE61-9ACA-4942-AC0A-402784F7E1B9}
     Source HASH: 40be9432586208c4bb49866ff7ea31bc16665a6b
     NGen GUID sign: {01CF6F39-E4D3-0686-274B-9F5584B1BA3D}
     OS:  WinNT
     Processor: amd64
     Runtime: 2.0.50727.926
     mscorwks.dll: TimeStamp=46D8E98C, CheckSum=009E1083
     Flags:  
     Scenarios:  <no debug info> <no debugger> <no profiler> <no instrumentation>
     Granted set: <PermissionSet class="System.Security.PermissionSet"
    version="1">
    <IPermission class="System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
    version="1"
    Flags="SkipVerification"/>
    </PermissionSet>
     File:  C:\WINDOWS\assembly\NativeImages_v2.0.50727_64\Microsoft.VisualC\396fcf01d3e48606274b9f5584b1ba3d\Microsoft.VisualC.ni.dll
     Dependencies:
      mscorlib, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{F107DDB2-5499-4106-A503-4AA24B5E4A4F}
       Sign:c2219dc660a826c6a3b4bc7e85de9105086db23d
       Hardbound Guid:{687FCFEB-5108-AC0C-E27B-D065DA0AE3B9}
      Microsoft.VisualC, Version=8.0.0.0, PublicKeyToken=b03f5f7f11d50a3a:
       Guid:{1483EE61-9ACA-4942-AC0A-402784F7E1B9}
       Sign:40be9432586208c4bb49866ff7ea31bc16665a6b
        Finished compiling assembly Microsoft.VisualC, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a ...
        Compiling assembly System.Data.SqlXml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 ...
    System.Data.SqlXml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
     Source MVID: {9F0BE212-39D8-4977-8C55-D2ADED637952}
     Source HASH: b97802318037f8b266acd7d3f0e16e3a9fb92384
     NGen GUID sign: {92C14596-C6E1-628A-572D-F352D8489683}
     OS:  WinNT
     Processor: amd64
     Runtime: 2.0.50727.926
     mscorwks.dll: TimeStamp=46D8E98C, CheckSum=009E1083
     Flags:  
     Scenarios:  <no debug info> <no debugger> <no profiler> <no instrumentation>
     Granted set: <PermissionSet class="System.Security.PermissionSet"
    version="1"
    Unrestricted="true"/>
     File:  C:\WINDOWS\assembly\NativeImages_v2.0.50727_64\System.Data.SqlXml\9645c192e1c68a62572df352d8489683\System.Data.SqlXml.ni.dll
     Dependencies:
      mscorlib, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{F107DDB2-5499-4106-A503-4AA24B5E4A4F}
       Sign:c2219dc660a826c6a3b4bc7e85de9105086db23d
       Hardbound Guid:{687FCFEB-5108-AC0C-E27B-D065DA0AE3B9}
      System.Data.SqlXml, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{9F0BE212-39D8-4977-8C55-D2ADED637952}
       Sign:b97802318037f8b266acd7d3f0e16e3a9fb92384
      System, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{71EFBB87-F94E-4397-8D46-76BB8FF60448}
       Sign:d464740812db1d60e65c51092d09f67028463192
       Hardbound Guid:{D5F143E5-1AD8-CB94-12D2-3D4AFFC46E22}
      System.Xml, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{2B8AEF52-78D4-4F03-BA8B-F0B5272945C8}
       Sign:218b87cdd9259fa6d554495522606b60250a72d6
       Hardbound Guid:{D76087B7-4045-EE39-A98A-147340E84C24}
      System.Configuration, Version=2.0.0.0, PublicKeyToken=b03f5f7f11d50a3a:
       Guid:{933D8A04-B103-4B70-BE89-87F8F370AEC4}
       Sign:f825e55c996a6136191e393eadffe07e2ed2b984
        Finished compiling assembly System.Data.SqlXml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 ...
    [1/6/2015 12:28:41 PM] [2] Process standard error:
    [1/6/2015 12:28:41 PM] [2] Ending processing.
    [1/6/2015 12:28:41 PM] [1] Executing '$fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\microsoft.Exchange.Common.IL.dll"); precompile-ManagedBinary -BinaryName $fullPath;', handleError = False
    [1/6/2015 12:28:41 PM] [2] Launching sub-task '$error.Clear(); $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\microsoft.Exchange.Common.IL.dll"); precompile-ManagedBinary -BinaryName $fullPath;'.
    [1/6/2015 12:28:41 PM] [2] Beginning processing.
    [1/6/2015 12:28:41 PM] [2] Starting: C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\ngen.exe arguments: install "C:\Program Files\Microsoft\Exchange Server\bin\microsoft.Exchange.Common.IL.dll" /verbose
    [1/6/2015 12:28:41 PM] [2] Process standard output: Microsoft (R) CLR Native Image Generator - Version 2.0.50727.42
    Copyright (C) Microsoft Corporation 1998-2002. All rights reserved.
    Installing assembly C:\Program Files\Microsoft\Exchange Server\bin\microsoft.Exchange.Common.IL.dll
    Compiling 1 assembly:
        Compiling assembly C:\Program Files\Microsoft\Exchange Server\bin\microsoft.Exchange.Common.IL.dll ...
    Microsoft.Exchange.Common.IL, Version=0.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
     Source MVID: {2C563679-AE56-41C7-8A80-8A0D965AFF9E}
     Source HASH: 318bf726c3ec004b8db6dfa3ad02a4eae82b4890
     NGen GUID sign: {DBE4EF23-FE16-7D26-5A96-72F3C43A5B66}
     OS:  WinNT
     Processor: amd64
     Runtime: 2.0.50727.926
     mscorwks.dll: TimeStamp=46D8E98C, CheckSum=009E1083
     Flags:  
     Scenarios:  <no debug info> <no debugger> <no profiler> <no instrumentation>
     Granted set: <PermissionSet class="System.Security.PermissionSet"
    version="1"
    Unrestricted="true"/>
     File:  C:\WINDOWS\assembly\NativeImages_v2.0.50727_64\Microsoft.Exchange.#\23efe4db16fe267d5a9672f3c43a5b66\Microsoft.Exchange.Common.IL.ni.dll
     Dependencies:
      mscorlib, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{F107DDB2-5499-4106-A503-4AA24B5E4A4F}
       Sign:c2219dc660a826c6a3b4bc7e85de9105086db23d
       Hardbound Guid:{687FCFEB-5108-AC0C-E27B-D065DA0AE3B9}
        Finished compiling assembly C:\Program Files\Microsoft\Exchange Server\bin\microsoft.Exchange.Common.IL.dll ...
    [1/6/2015 12:28:41 PM] [2] Process standard error:
    [1/6/2015 12:28:41 PM] [2] Ending processing.
    [1/6/2015 12:28:41 PM] [1] Executing '$fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\Microsoft.Exchange.Diagnostics.dll"); precompile-ManagedBinary -BinaryName $fullPath;', handleError = False
    [1/6/2015 12:28:41 PM] [2] Launching sub-task '$error.Clear(); $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\Microsoft.Exchange.Diagnostics.dll"); precompile-ManagedBinary -BinaryName $fullPath;'.
    [1/6/2015 12:28:41 PM] [2] Beginning processing.
    [1/6/2015 12:28:41 PM] [2] Starting: C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\ngen.exe arguments: install "C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Diagnostics.dll" /verbose
    [1/6/2015 12:29:01 PM] [2] Process standard output: Microsoft (R) CLR Native Image Generator - Version 2.0.50727.42
    Copyright (C) Microsoft Corporation 1998-2002. All rights reserved.
    Installing assembly C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Diagnostics.dll
    Compiling 2 assemblies:
        Compiling assembly C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Diagnostics.dll ...
    Microsoft.Exchange.Diagnostics, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
     Source MVID: {8CBFBD3F-1859-44DB-B85B-3DE8CA01DF33}
     Source HASH: 1a70943ea983aa1742e98704ccbfb40bfef33c23
     NGen GUID sign: {77300B68-787B-A1CA-3298-EFA73DB0406B}
     OS:  WinNT
     Processor: amd64
     Runtime: 2.0.50727.926
     mscorwks.dll: TimeStamp=46D8E98C, CheckSum=009E1083
     Flags:  
     Scenarios:  <no debug info> <no debugger> <no profiler> <no instrumentation>
     Granted set: <PermissionSet class="System.Security.PermissionSet"
    version="1"
    Unrestricted="true"/>
     File:  C:\WINDOWS\assembly\NativeImages_v2.0.50727_64\Microsoft.Exchange.#\680b30777b78caa13298efa73db0406b\Microsoft.Exchange.Diagnostics.ni.dll
     Dependencies:
      mscorlib, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{F107DDB2-5499-4106-A503-4AA24B5E4A4F}
       Sign:c2219dc660a826c6a3b4bc7e85de9105086db23d
       Hardbound Guid:{687FCFEB-5108-AC0C-E27B-D065DA0AE3B9}
      Microsoft.Exchange.Data.Common, Version=8.0.681.0, PublicKeyToken=31bf3856ad364e35:
       Guid:{F2CA7D1F-DA42-4E38-AF97-547F51FA377C}
       Sign:b8f148b173ec7d9e604f21424493a289b6e9873a
      System, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{71EFBB87-F94E-4397-8D46-76BB8FF60448}
       Sign:d464740812db1d60e65c51092d09f67028463192
       Hardbound Guid:{D5F143E5-1AD8-CB94-12D2-3D4AFFC46E22}
      Microsoft.Exchange.Rpc, Version=8.0.0.0, PublicKeyToken=31bf3856ad364e35:
       Guid:{A77F7B45-C91D-4B18-94DB-D563EB0D1F84}
       Sign:1c8367b62a1131417ed73fe3e751c3828b38a5a1
      System.Configuration, Version=2.0.0.0, PublicKeyToken=b03f5f7f11d50a3a:
       Guid:{933D8A04-B103-4B70-BE89-87F8F370AEC4}
       Sign:f825e55c996a6136191e393eadffe07e2ed2b984
      Microsoft.Exchange.Common.IL, Version=0.0.0.0, PublicKeyToken=31bf3856ad364e35:
       Guid:{2C563679-AE56-41C7-8A80-8A0D965AFF9E}
       Sign:318bf726c3ec004b8db6dfa3ad02a4eae82b4890
        Finished compiling assembly C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Diagnostics.dll ...
        Compiling assembly Microsoft.Exchange.Data.Common, Version=8.0.681.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 ...
    Microsoft.Exchange.Data.Common, Version=8.0.681.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
     Source MVID: {F2CA7D1F-DA42-4E38-AF97-547F51FA377C}
     Source HASH: b8f148b173ec7d9e604f21424493a289b6e9873a
     NGen GUID sign: {7A773BF5-FF43-09DF-08EF-86BA364EACF8}
     OS:  WinNT
     Processor: amd64
     Runtime: 2.0.50727.926
     mscorwks.dll: TimeStamp=46D8E98C, CheckSum=009E1083
     Flags:  
     Scenarios:  <no debug info> <no debugger> <no profiler> <no instrumentation>
     Granted set: <PermissionSet class="System.Security.PermissionSet"
    version="1"
    Unrestricted="true"/>
     File:  C:\WINDOWS\assembly\NativeImages_v2.0.50727_64\Microsoft.Exchange.#\f53b777a43ffdf0908ef86ba364eacf8\Microsoft.Exchange.Data.Common.ni.dll
     Dependencies:
      mscorlib, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{F107DDB2-5499-4106-A503-4AA24B5E4A4F}
       Sign:c2219dc660a826c6a3b4bc7e85de9105086db23d
       Hardbound Guid:{687FCFEB-5108-AC0C-E27B-D065DA0AE3B9}
      Microsoft.Exchange.Data.Common, Version=8.0.681.0, PublicKeyToken=31bf3856ad364e35:
       Guid:{F2CA7D1F-DA42-4E38-AF97-547F51FA377C}
       Sign:b8f148b173ec7d9e604f21424493a289b6e9873a
      System, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{71EFBB87-F94E-4397-8D46-76BB8FF60448}
       Sign:d464740812db1d60e65c51092d09f67028463192
       Hardbound Guid:{D5F143E5-1AD8-CB94-12D2-3D4AFFC46E22}
      System.Configuration, Version=2.0.0.0, PublicKeyToken=b03f5f7f11d50a3a:
       Guid:{933D8A04-B103-4B70-BE89-87F8F370AEC4}
       Sign:f825e55c996a6136191e393eadffe07e2ed2b984
      System.Xml, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{2B8AEF52-78D4-4F03-BA8B-F0B5272945C8}
       Sign:218b87cdd9259fa6d554495522606b60250a72d6
        Finished compiling assembly Microsoft.Exchange.Data.Common, Version=8.0.681.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 ...
    [1/6/2015 12:29:01 PM] [2] Process standard error:
    [1/6/2015 12:29:01 PM] [2] Ending processing.
    [1/6/2015 12:29:01 PM] [1] Executing '$fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\Microsoft.Exchange.Common.dll"); precompile-ManagedBinary -BinaryName $fullPath;', handleError = False
    [1/6/2015 12:29:01 PM] [2] Launching sub-task '$error.Clear(); $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\Microsoft.Exchange.Common.dll"); precompile-ManagedBinary -BinaryName $fullPath;'.
    [1/6/2015 12:29:01 PM] [2] Beginning processing.
    [1/6/2015 12:29:01 PM] [2] Starting: C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\ngen.exe arguments: install "C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Common.dll" /verbose
    [1/6/2015 12:29:04 PM] [2] Process standard output: Microsoft (R) CLR Native Image Generator - Version 2.0.50727.42
    Copyright (C) Microsoft Corporation 1998-2002. All rights reserved.
    Installing assembly C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Common.dll
    Compiling 4 assemblies:
        Compiling assembly C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Common.dll ...
    Microsoft.Exchange.Common, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
     Source MVID: {090DC806-FB68-4A89-A969-BD125452394C}
     Source HASH: b982dcf50fe022b926a03529b85ca2e23a60d148
     NGen GUID sign: {792B0253-E3BE-1EFA-9121-A58ACC443015}
     OS:  WinNT
     Processor: amd64
     Runtime: 2.0.50727.926
     mscorwks.dll: TimeStamp=46D8E98C, CheckSum=009E1083
     Flags:  
     Scenarios:  <no debug info> <no debugger> <no profiler> <no instrumentation>
     Granted set: <PermissionSet class="System.Security.PermissionSet"
    version="1"
    Unrestricted="true"/>
     File:  C:\WINDOWS\assembly\NativeImages_v2.0.50727_64\Microsoft.Exchange.#\53022b79bee3fa1e9121a58acc443015\Microsoft.Exchange.Common.ni.dll
     Dependencies:
      mscorlib, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{F107DDB2-5499-4106-A503-4AA24B5E4A4F}
       Sign:c2219dc660a826c6a3b4bc7e85de9105086db23d
       Hardbound Guid:{687FCFEB-5108-AC0C-E27B-D065DA0AE3B9}
      Microsoft.Exchange.Data.Common, Version=8.0.681.0, PublicKeyToken=31bf3856ad364e35:
       Guid:{F2CA7D1F-DA42-4E38-AF97-547F51FA377C}
       Sign:b8f148b173ec7d9e604f21424493a289b6e9873a
      System.ServiceProcess, Version=2.0.0.0, PublicKeyToken=b03f5f7f11d50a3a:
       Guid:{B5D02EE9-B8F4-493D-98DE-B99067CAF039}
       Sign:346c2ee41e7e70d67ce4640726edd8203d3f276f
      System, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{71EFBB87-F94E-4397-8D46-76BB8FF60448}
       Sign:d464740812db1d60e65c51092d09f67028463192
       Hardbound Guid:{D5F143E5-1AD8-CB94-12D2-3D4AFFC46E22}
      Microsoft.Exchange.Diagnostics, Version=8.0.0.0, PublicKeyToken=31bf3856ad364e35:
       Guid:{8CBFBD3F-1859-44DB-B85B-3DE8CA01DF33}
       Sign:1a70943ea983aa1742e98704ccbfb40bfef33c23
      Microsoft.Exchange.Common.IL, Version=0.0.0.0, PublicKeyToken=31bf3856ad364e35:
       Guid:{2C563679-AE56-41C7-8A80-8A0D965AFF9E}
       Sign:318bf726c3ec004b8db6dfa3ad02a4eae82b4890
      System.Xml, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{2B8AEF52-78D4-4F03-BA8B-F0B5272945C8}
       Sign:218b87cdd9259fa6d554495522606b60250a72d6
      System.Configuration, Version=2.0.0.0, PublicKeyToken=b03f5f7f11d50a3a:
       Guid:{933D8A04-B103-4B70-BE89-87F8F370AEC4}
       Sign:f825e55c996a6136191e393eadffe07e2ed2b984
        Finished compiling assembly C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Common.dll ...
        Compiling assembly System.ServiceProcess, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a ...
    System.ServiceProcess, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
     Source MVID: {B5D02EE9-B8F4-493D-98DE-B99067CAF039}
     Source HASH: 346c2ee41e7e70d67ce4640726edd8203d3f276f
     NGen GUID sign: {9B9F9598-687E-0C63-2CA3-B8EDA6232888}
     OS:  WinNT
     Processor: amd64
     Runtime: 2.0.50727.926
     mscorwks.dll: TimeStamp=46D8E98C, CheckSum=009E1083
     Flags:  
     Scenarios:  <no debug info> <no debugger> <no profiler> <no instrumentation>
     Granted set: <PermissionSet class="System.Security.PermissionSet"
    version="1"
    Unrestricted="true"/>
     File:  C:\WINDOWS\assembly\NativeImages_v2.0.50727_64\System.ServiceProce#\98959f9b7e68630c2ca3b8eda6232888\System.ServiceProcess.ni.dll
     Dependencies:
      mscorlib, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{F107DDB2-5499-4106-A503-4AA24B5E4A4F}
       Sign:c2219dc660a826c6a3b4bc7e85de9105086db23d
       Hardbound Guid:{687FCFEB-5108-AC0C-E27B-D065DA0AE3B9}
      System.ServiceProcess, Version=2.0.0.0, PublicKeyToken=b03f5f7f11d50a3a:
       Guid:{B5D02EE9-B8F4-493D-98DE-B99067CAF039}
       Sign:346c2ee41e7e70d67ce4640726edd8203d3f276f
      System, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{71EFBB87-F94E-4397-8D46-76BB8FF60448}
       Sign:d464740812db1d60e65c51092d09f67028463192
       Hardbound Guid:{D5F143E5-1AD8-CB94-12D2-3D4AFFC46E22}
      System.Configuration.Install, Version=2.0.0.0, PublicKeyToken=b03f5f7f11d50a3a:
       Guid:{D5488AB9-12B4-4921-AA95-21DB22B1179F}
       Sign:f4643c4fbc352b9201db4aed87752b52241d6f41
      System.Windows.Forms, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{1FF9D862-38A6-4352-A1BC-17E1C0B67EC2}
       Sign:7779b2d88e7f75ffc31828f7112e7066410162e8
      System.Drawing, Version=2.0.0.0, PublicKeyToken=b03f5f7f11d50a3a:
       Guid:{A3205C19-31D6-4357-9F8E-A9513306DEC7}
       Sign:fb709be7704fcf1fd7055d39ebaf4388194d2889
        Finished compiling assembly System.ServiceProcess, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a ...
        Compiling assembly System.Configuration.Install, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a ...
    System.Configuration.Install, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
     Source MVID: {D5488AB9-12B4-4921-AA95-21DB22B1179F}
     Source HASH: f4643c4fbc352b9201db4aed87752b52241d6f41
     NGen GUID sign: {C503523D-FD52-F19C-05CB-4B7336D79A49}
     OS:  WinNT
     Processor: amd64
     Runtime: 2.0.50727.926
     mscorwks.dll: TimeStamp=46D8E98C, CheckSum=009E1083
     Flags:  
     Scenarios:  <no debug info> <no debugger> <no profiler> <no instrumentation>
     Granted set: <PermissionSet class="System.Security.PermissionSet"
    version="1"
    Unrestricted="true"/>
     File:  C:\WINDOWS\assembly\NativeImages_v2.0.50727_64\System.Configuratio#\3d5203c552fd9cf105cb4b7336d79a49\System.Configuration.Install.ni.dll
     Dependencies:
      mscorlib, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{F107DDB2-5499-4106-A503-4AA24B5E4A4F}
       Sign:c2219dc660a826c6a3b4bc7e85de9105086db23d
       Hardbound Guid:{687FCFEB-5108-AC0C-E27B-D065DA0AE3B9}
      System.Configuration.Install, Version=2.0.0.0, PublicKeyToken=b03f5f7f11d50a3a:
       Guid:{D5488AB9-12B4-4921-AA95-21DB22B1179F}
       Sign:f4643c4fbc352b9201db4aed87752b52241d6f41
      System, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{71EFBB87-F94E-4397-8D46-76BB8FF60448}
       Sign:d464740812db1d60e65c51092d09f67028463192
       Hardbound Guid:{D5F143E5-1AD8-CB94-12D2-3D4AFFC46E22}
      System.Runtime.Serialization.Formatters.Soap, Version=2.0.0.0, PublicKeyToken=b03f5f7f11d50a3a:
       Guid:{13BC79E5-AB8A-48B6-B2CC-0854119DCBDA}
       Sign:1014fd9f161aff328c98924d6088ae65aa3030d7
      System.Windows.Forms, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{1FF9D862-38A6-4352-A1BC-17E1C0B67EC2}
       Sign:7779b2d88e7f75ffc31828f7112e7066410162e8
        Finished compiling assembly System.Configuration.Install, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a ...
        Compiling assembly System.Runtime.Serialization.Formatters.Soap, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a ...
    System.Runtime.Serialization.Formatters.Soap, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
     Source MVID: {13BC79E5-AB8A-48B6-B2CC-0854119DCBDA}
     Source HASH: 1014fd9f161aff328c98924d6088ae65aa3030d7
     NGen GUID sign: {34727167-AFF5-E848-9451-78BC72A62EC8}
     OS:  WinNT
     Processor: amd64
     Runtime: 2.0.50727.926
     mscorwks.dll: TimeStamp=46D8E98C, CheckSum=009E1083
     Flags:  
     Scenarios:  <no debug info> <no debugger> <no profiler> <no instrumentation>
     Granted set: <PermissionSet class="System.Security.PermissionSet"
    version="1"
    Unrestricted="true"/>
     File:  C:\WINDOWS\assembly\NativeImages_v2.0.50727_64\System.Runtime.Seri#\67717234f5af48e8945178bc72a62ec8\System.Runtime.Serialization.Formatters.Soap.ni.dll
     Dependencies:
      mscorlib, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{F107DDB2-5499-4106-A503-4AA24B5E4A4F}
       Sign:c2219dc660a826c6a3b4bc7e85de9105086db23d
       Hardbound Guid:{687FCFEB-5108-AC0C-E27B-D065DA0AE3B9}
      System.Runtime.Serialization.Formatters.Soap, Version=2.0.0.0, PublicKeyToken=b03f5f7f11d50a3a:
       Guid:{13BC79E5-AB8A-48B6-B2CC-0854119DCBDA}
       Sign:1014fd9f161aff328c98924d6088ae65aa3030d7
      System.Xml, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{2B8AEF52-78D4-4F03-BA8B-F0B5272945C8}
       Sign:218b87cdd9259fa6d554495522606b60250a72d6
      System, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{71EFBB87-F94E-4397-8D46-76BB8FF60448}
       Sign:d464740812db1d60e65c51092d09f67028463192
        Finished compiling assembly System.Runtime.Serialization.Formatters.Soap, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a ...
    [1/6/2015 12:29:04 PM] [2] Process standard error:
    [1/6/2015 12:29:04 PM] [2] Ending processing.
    [1/6/2015 12:29:04 PM] [1] Executing '$fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\Microsoft.Exchange.Core.Strings.dll"); precompile-ManagedBinary -BinaryName $fullPath;', handleError = False
    [1/6/2015 12:29:04 PM] [2] Launching sub-task '$error.Clear(); $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\Microsoft.Exchange.Core.Strings.dll"); precompile-ManagedBinary -BinaryName $fullPath;'.
    [1/6/2015 12:29:04 PM] [2] Beginning processing.
    [1/6/2015 12:29:04 PM] [2] Starting: C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\ngen.exe arguments: install "C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Core.Strings.dll" /verbose
    [1/6/2015 12:29:04 PM] [2] Process standard output: Microsoft (R) CLR Native Image Generator - Version 2.0.50727.42
    Copyright (C) Microsoft Corporation 1998-2002. All rights reserved.
    Installing assembly C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Core.Strings.dll
    Compiling 1 assembly:
        Compiling assembly C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Core.Strings.dll ...
    Microsoft.Exchange.Core.Strings, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
     Source MVID: {E671C74F-10AB-419E-8A0F-4C027B3981B5}
     Source HASH: bef5663bd404d89f1c9e4e8df9e17b782e4ce766
     NGen GUID sign: {C4BFD0BF-BC1A-FF4C-DACE-61165E6BEE7C}
     OS:  WinNT
     Processor: amd64
     Runtime: 2.0.50727.926
     mscorwks.dll: TimeStamp=46D8E98C, CheckSum=009E1083
     Flags:  
     Scenarios:  <no debug info> <no debugger> <no profiler> <no instrumentation>
     Granted set: <PermissionSet class="System.Security.PermissionSet"
    version="1"
    Unrestricted="true"/>
     File:  C:\WINDOWS\assembly\NativeImages_v2.0.50727_64\Microsoft.Exchange.#\bfd0bfc41abc4cffdace61165e6bee7c\Microsoft.Exchange.Core.Strings.ni.dll
     Dependencies:
      mscorlib, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{F107DDB2-5499-4106-A503-4AA24B5E4A4F}
       Sign:c2219dc660a826c6a3b4bc7e85de9105086db23d
       Hardbound Guid:{687FCFEB-5108-AC0C-E27B-D065DA0AE3B9}
      Microsoft.Exchange.Data.Common, Version=8.0.681.0, PublicKeyToken=31bf3856ad364e35:
       Guid:{F2CA7D1F-DA42-4E38-AF97-547F51FA377C}
       Sign:b8f148b173ec7d9e604f21424493a289b6e9873a
        Finished compiling assembly C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Core.Strings.dll ...
    [1/6/2015 12:29:04 PM] [2] Process standard error:
    [1/6/2015 12:29:04 PM] [2] Ending processing.
    [1/6/2015 12:29:04 PM] [1] Executing '$fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\Microsoft.Exchange.Net.dll"); precompile-ManagedBinary -BinaryName $fullPath;', handleError = False
    [1/6/2015 12:29:04 PM] [2] Launching sub-task '$error.Clear(); $fullPath = [System.IO.Path]::Combine($RoleInstallPath, "bin\Microsoft.Exchange.Net.dll"); precompile-ManagedBinary -BinaryName $fullPath;'.
    [1/6/2015 12:29:04 PM] [2] Beginning processing.
    [1/6/2015 12:29:04 PM] [2] Starting: C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\ngen.exe arguments: install "C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Net.dll" /verbose
    [1/6/2015 12:29:13 PM] [2] Process standard output: Microsoft (R) CLR Native Image Generator - Version 2.0.50727.42
    Copyright (C) Microsoft Corporation 1998-2002. All rights reserved.
    Installing assembly C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Net.dll
    Compiling 3 assemblies:
        Compiling assembly C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Net.dll ...
    Microsoft.Exchange.Net, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
     Source MVID: {9177A7BE-2ECC-40D4-B5FB-0C643A1130E4}
     Source HASH: 2d34ca7cbaf2359fe068828351a1d8d30e21a536
     NGen GUID sign: {BBAEC190-74C2-84D5-C4B9-F7BA04A86E4E}
     OS:  WinNT
     Processor: amd64
     Runtime: 2.0.50727.926
     mscorwks.dll: TimeStamp=46D8E98C, CheckSum=009E1083
     Flags:  
     Scenarios:  <no debug info> <no debugger> <no profiler> <no instrumentation>
     Granted set: <PermissionSet class="System.Security.PermissionSet"
    version="1"
    Unrestricted="true"/>
     File:  C:\WINDOWS\assembly\NativeImages_v2.0.50727_64\Microsoft.Exchange.#\90c1aebbc274d584c4b9f7ba04a86e4e\Microsoft.Exchange.Net.ni.dll
     Dependencies:
      mscorlib, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{F107DDB2-5499-4106-A503-4AA24B5E4A4F}
       Sign:c2219dc660a826c6a3b4bc7e85de9105086db23d
       Hardbound Guid:{687FCFEB-5108-AC0C-E27B-D065DA0AE3B9}
      System, Version=2.0.0.0, PublicKeyToken=b77a5c561934e089:
       Guid:{71EFBB87-F94E-4397-8D46-76BB8FF60448}
       Sign:d464740812db1d60e65c51092d09f67028463192
       Hardbound Guid:{D5F143E5-1AD8-CB94-12D2-3D4AFFC46E22}
      Microsoft.Exchange.Data.Common, Version=8.0.681.0, PublicKeyToken=31bf3856ad364e35:
       Guid:{F2CA7D1F-DA42-4E38-AF97-547F51FA377C}
       Sign:b8f148b173ec7d9e604f21424493a289b6e9873a
      Microsoft.Exchange.Common, Version=8.0.0.0, PublicKeyToken=31bf3856ad364e35:
       Guid:{090DC806-FB68-4A89-A969-BD125452394C}
       Sign:b982dcf50fe022b926a03529b85ca2e23a60d148
      System.ServiceProcess, Version=2.0.0.0, PublicKeyToken=b03f5f7f11d50a3a:
       Guid:{B5D02EE9-B8F4-493D-98DE-B99067CAF039}
       Sign:346c2ee41e7e70d67ce4640726edd8203d3f276f
      Microsoft.Exchange.Diagnostics, Version=8.0.0.0, PublicKeyToken=31bf3856ad364e35:
       Guid:{8CBFBD3F-1859-44DB-B85B-3DE8CA01DF33}
       Sign:1a70943ea983aa1742e98704ccbfb40bfef33c23
      Interop.CertEnroll, Version=8.0.0.0, PublicKeyToken=31bf3856ad364e35:
       Guid:{0E330E86-15D9-46AE-A943-0160454E3570}
       Sign:10641c56e63c1e3b9be7bfb997e948658dc1e2d1
      System.DirectoryServices, Version=2.0.0.0, PublicKeyToken=b03f5f7f11d50a3a:
       Guid:{E467B35C-E345-465C-8CCB-F6D3E2E81276}
       Sign:ad9b0b1379315a2b0fc5d0367fa95cf9bd4681c9
      Interop.XEnroll, Version=8.0.0.0, PublicKeyToken=31bf3856ad364e35:
       Guid:{678158A1-9581-44D6-BF1A-126EA654836E}
       Sign:01a0beca7e00e08f1291a22cfe2830785bf7f0ab
      System.Configuration, Version=2.0.0.0, PublicKeyToken=b03f5f7f11d50a3a:
       Guid:{933D8A04-B103-4B70-BE89-87F8F370AEC4}
       Sign:f825e55c996a6136191e393eadffe07e2ed2b984
      Microsoft.Exchange.Core.Strings, Version=8.0.0.0, PublicKeyToken=31bf3856ad364e35:
       Guid:{E671C74F-10AB-419E-8A0F-4C027B3981B5}
       Sign:bef5663bd404d89f1c9e4e8df9e17b782e4ce766
        Finished compiling assembly C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Net.dll ...
        Compiling assembly Interop.CertEnroll, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 ...
    Interop.CertEnroll, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
     Source MVID: {0E330E86-15D9-46AE-A943-0160454E3570}
     Source HASH: 10641c56e63c1e3b9be7bfb997e948658dc1e2d1
     NGen GUID sign: {671C04E0-0279-45A6-2B1C-22C0FA104F19}
     OS:  WinNT
     Processor: amd64
     Runtime: 2.0.50727.926
     mscorwks.dll: TimeStamp=46D8E98C, CheckSum=009E1083
     Flags:  
     Scenarios:  <no debug info> <no debugger> <no profiler> <no instrumentation>
     Granted set: <PermissionSet class="System.Security.PermissionSet"
    version="1"

Maybe you are looking for

  • String problem in web tutorial

    HI, I tried to create the web tutorial, the first step, that is to put a label, text field, button and static text. This line is my problem in the helloButton action "String name= (String)nameField.getText();" I am not sure where a static text field

  • Export BPEL files

    Hi everyone: Is possible to export documents/models  from a SAP services to BPEL files ? Which part of SAP service could do that ? Thanks.

  • Hierarchy Viewer: Setting default zoom level and levelFetchSize

    I have couple of questions on Hierarchy Viewer: (1) Is it possible to set the zoom level to say 50% by default when the HV is rendered first time. By default the nodes are rendered at 100%, but I would like to render them at 50% by default - and on h

  • A simple question about c:out and the ADF bindings

    I have a small problem which I can't figure out :-( The solution is probably dead easy, but I don't see it .. The problem is : I have a jsp-file which have the following tags : <c:out value="${bindings.EstimatedInterest}" /> <c:out value="${bindings.

  • Songs purchased on iPad are not downloaded to Mac

    Hello there, today I have upgraded my iPad2 2 to iOS5 and updated my MacBookAir by installing iTunes 10.5 and setting up the iCloud data on the System Preferences Panel. Then I have purchased a song from iPad the iTunes Store, just to try how the "mi