locked
Exchange 2013 installation error RRS feed

  • Question

  • Hi,

    We have an Exchange 2007 environment and are installing a fresh 2013 environment to migrate to.  The Client Access servers installed successfully, but when I go to install a mailbox server I get the following error:

    Error:
    The following error was generated when "$error.Clear();
              if (!$RoleIsDatacenter -and !$RoleIsDatacenterDedicated)
              {
                $arbUsers = @(get-user -Filter {lastname -eq "MSExchApproval 1f05a927-3be2-4fb9-aa03-b59fe3b56f4c"} -IgnoreDefaultScope -ResultSize 1);
                if ($arbUsers.Length -ne 0)
                {
                  $mbxname = $arbUsers[0].name;
                  $mbxs = @( get-mailbox -arbitration -Filter {name -eq $mbxname} -IgnoreDefaultScope -resultSize 1 );
                  if ( $mbxs.length -eq 0)
                  {
                    $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                    if ($dbs.Length -ne 0)
                    {
                      enable-mailbox -Arbitration -identity $arbUsers[0] -database $dbs[0].Identity;
                    }
                  }
                }
              }
            " was run: "The Mailbox database "Mailbox Database 0191534003" isn't on a server running Exchange 2013 or a later version. If you want to create or enable a Exchange 2010 mailbox, or want to enable the archive or remote archive for a Exchange 2010 Sp1 mailbox, please execute the cmdlet from a Exchange 2010 server.".

    Does anyone have any thoughts on this one?  We don't have any Exchange 2010 servers.  The installer stops at this error.  The database it refers to is the one it created earlier during the same install, so not sure what it means when it says it isn't on an Exchange 2013 server.  This DB is on another local volume.

    Thank you,

    Kurt

    Tuesday, July 14, 2015 2:45 PM

Answers

  • Hi

    can you check in ADSIEdit for this db and remove it?


    Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Marked as answer by k2009 Wednesday, July 15, 2015 4:55 PM
    Tuesday, July 14, 2015 2:53 PM

All replies

  • Hi

    can you check in ADSIEdit for this db and remove it?


    Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Marked as answer by k2009 Wednesday, July 15, 2015 4:55 PM
    Tuesday, July 14, 2015 2:53 PM
  • Do you have the latest exchange 2007 rollup 10 for Sp3 installed?

    Was exchange 2010 install ever attempted? It would appear that the 2013 may be referencing a AD object that was at one point created, you may need to lookup an article on removing exchange 2010 manually and use adsiedit.msc to maybe verify or remove an object or two if it was attempted at some point.

    I also found this article that may help explain.

    http://msexchangeguru.com/2013/01/02/exchange-2013-error/

    Tuesday, July 14, 2015 2:58 PM
  • Did you encounter an error the first time you ran it (that wasn't the DB error)?

    It most likely stopped after the creation (addition to AD) of the DB and that's why you're receiving the error. If you've performed the pre-reqs as Darren was mentioning and it passes, you can then manually remove it as what Edward said.

    Tuesday, July 14, 2015 4:24 PM
  • I don't think we got this error the first time - instead as you suspect it was another error about not having the new Client Access servers turned on.  (I had shut them down as they were acting as an SCP and clients were getting cert errors, but I couldn't update the SCP until I had the mailbox server.)  I see where I can delete it from within ADSI but there is another issue.  The server name I am using was previously used in the org and the uninstall did not go well.  So the Exchange tools still think the old server exists.  Try as I might I cannot get Exchange to fully uninstall on that server.  So is there a way to clear this server out of the Exchange org/AD?  Maybe using ADSI edit?  (I don't see it in there so far but Exchange is remembering it from somewhere.)

    I will check the article Darren linked to see if this discusses how to get rid of old Exchange objects.

    Thank you,

    Kurt

    Tuesday, July 14, 2015 4:57 PM
  • When I remove the DB in ADSI edit should I delete it off the server itself as well?

    Also, some of this trouble may be due to an old Exchange 2007 server of the same name.  I couldn't uninstall it so I eventually tried reinstalling it.  Now it is in a state of showing up in the Exchange console, and the server is turned off.  Do you know how to remove it from there?  It is not in ADSI edit but the 2013 server of the same name is (I can tell it is the new one in the version entry in properties).  I think the database delete will work but don't want to try the install again until the old entity in the Exchange console is gone.  Interestingly it shows up in the Exchane 2007 console on the Exchange servers but not in my local Exchange console.

    Thank you,

    Kurt


    • Edited by k2009 Tuesday, July 14, 2015 6:00 PM Input product key.
    Tuesday, July 14, 2015 5:28 PM
  • okay, so you had a server, turned it off and now used the same name for exchange 2013? was the db located on this box?

    I think you need to plan this and how you are going to do the cleanup, you have multiple things that need correcting and we need to start with one at a time. Too many changes at once will cause chaos in your environment.

    Lets start, did you upgrade the schema/ad or did you let the wizard update it for you when you ran the 2013 install?

    secondly adsiedit should have the old server info but you will need to either run the 2007 (unless the schema changed) and then recover it using the setup:mrecover.


    Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Proposed as answer by David Wang_ Wednesday, July 15, 2015 1:51 AM
    Tuesday, July 14, 2015 6:40 PM
  • Yes, the old server would not completely uninstall, so at one point I reinstalled it hping I could uninstall it later but got the same result.  This left the entry for it in the Exchange console with it wanting the license key - I input that today.  There was a db but it was empty.  Basically this server was only being used as an offline address book host as we had trouble running it on a cluster.

    I did upgrade the schema and AD from the command line a week ago and that all went fine.

    Looks like the schema changed as the properties for the server in ADSIedit show all the installation paths for the 2013 server and not the 2007 one.

    Are youi saying I need to run this setup:mrecover on the old 2007 Exchange server (that Exchange was mostly removed on)?

    Thank you,

    Kurt

    Tuesday, July 14, 2015 6:57 PM
  • If you didnt update the schema then yes but as you have you cannot install 2007 again.

    can you do some more searching in adsiedit for your 2007 and its db? You need to clear out these entries before you can continue with your 2013 setup.


    Edward van Biljon - Exchange MVP

    Tuesday, July 14, 2015 7:01 PM
  • I was able to get the Exchange 2007 server removed from the Exchange 2007 tools - by uninstalling the Exchange 2013 server of the same name.  I guess the objects had become somehow linked or as one.  This also removed the server object from ADSIedit and I had previously removed the database from there.  So now it looks better in that all traces of the 2007 server are gone.

    In the future I will watch the naming more closely - in this case the old server wasn't showing up in my Exchange tools so I didn't know that Exchange was still "keeping" it until I logged onto the server and used the tools from there.The only thing is when I uninstalled Exchange 2013 it did not fully complete, and got through the services but gave me an error for the language packs - saying the files were in use.  I couldn't determine which packs were installed but something else told me none of them were because UM wasn't installed. 

    So at this point trying to resume setup again.  It detects that a previous install is partially there and is resuming the install, but gets stuck at 98% on the transport service - the log just keeps saying it is trying to start it.  Finally it ended with an error saying it cannot start the transport service.

    Any ideas on how to complete this install?

    Thanks, Kurt

    

    Tuesday, July 14, 2015 9:06 PM
  • Hi,

    I agree with Edward, you need to to clear out these exchange 2007 entries before installing 2013 .

    I have noticed you had a new problem.

    Now the transport service can't start.

    Please make sure the dependency service are starting.

    Please check the application logs and system logs for further analysis.

    Regards,

    David

    Wednesday, July 15, 2015 2:36 AM
  • I did wind up getting all of the 2007 stuff out of the AD. 

    I tried various things with the transport service including going through the logs but came to the conclusion that I should get this all uninstalled before trying to fix it.  Now on the uninstall it errors out on the language packs.  Any idea of how to get them off?  It errors on them saying the v15 folder is in use.  Not seeing what is using it.  The setup log gives no additional information.

    If I can't uninstall this I will need to do a complete server rebuild because I can't uninstall this product on a fresh 2012 R2 server build.

    Here is the end of the setup log:

    [07/14/2015 21:34:05.0161] [2] Active Directory session settings for 'Uninstall-MsiPackage' are: View Entire Forest: 'True', Configuration Domain Controller: 'OLINDC01.olin.edu', Preferred Global Catalog: 'OLINDC01.olin.edu', Preferred Domain Controllers: '{ OLINDC01.olin.edu }'
    [07/14/2015 21:34:05.0161] [2] User specified parameters:  -ProductCode:'dedffb64-42ec-4e26-7c1a-430e86df378c' -LogFile:'C:\ExchangeSetupLogs\Uninstall.7C1A.Client.20150714-173107.msilog'
    [07/14/2015 21:34:05.0161] [2] Beginning processing uninstall-MsiPackage
    [07/14/2015 21:34:05.0161] [2] Removing MSI package with code 'dedffb64-42ec-4e26-7c1a-430e86df378c'.
    [07/14/2015 21:34:07.0937] [2] Ending processing uninstall-MsiPackage
    [07/14/2015 21:34:07.0953] [2] Beginning processing Write-ExchangeSetupLog
    [07/14/2015 21:34:07.0953] [2] Remove Language Packs completed.
    [07/14/2015 21:34:07.0953] [2] Ending processing Write-ExchangeSetupLog
    [07/14/2015 21:34:07.0953] [1] The following 2 error(s) occurred during task execution:
    [07/14/2015 21:34:07.0953] [1] 0.  ErrorRecord: Cannot remove the item at 'D:\Program Files\Microsoft\Exchange Server\V15\' because it is in use.
    [07/14/2015 21:34:07.0953] [1] 0.  ErrorRecord: System.Management.Automation.PSInvalidOperationException: Cannot remove the item at 'D:\Program Files\Microsoft\Exchange Server\V15\' because it is in use.
    [07/14/2015 21:34:07.0969] [1] [ERROR] The following error was generated when "$error.Clear();
                        $regPath='HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall';
                        
                        $PackageGUIDRegEx = "{DEDFFB[0-9a-fA-F]{2}-42EC-4E26-[0-9a-fA-F]{4}-430E86DF378C}";
                        
                        $InstallPath = (Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\ExchangeServer\v15\setup').MsiInstallPath;
                        
                        if(test-path ($regPath))
                        {
                            Write-ExchangeSetupLog -info ("Removing " +  $RoleLanguagePackType + " Language Packs.");
                            Get-ChildItem ($regPath) | foreach{
                                if($_ -match "(?<ProductCode>$PackageGUIDRegEx)") {
                                    $langPackPackageCode = $matches['ProductCode'];
                                    if($langPackPackageCode -ne $null -and $langPackPackageCode.Length -ne 0) {
                                        Write-ExchangeSetupLog -info ("Removing package $langPackPackageCode");
                                        $language = $langPackPackageCode.Substring(20,4);
                                        $logFilePath = [IO.Path]::Combine($RoleLogFilePath,"Uninstall") + '.' + $language + '.' + "Client" + "." + $RoleLogDateTime + ".msilog";
                                        uninstall-MsiPackage -ProductCode ($langPackPackageCode) -LogFile ($logFilePath);
                                    };
                                };
                            };
                            Remove-Item -Path $InstallPath -Include *.Localized.js -Recurse
                            Remove-Item -Path $InstallPath -Include *.Localized.min.js -Recurse
                            Write-ExchangeSetupLog -info "Remove Language Packs completed.";
                        };
                    
            " was run: "Cannot remove the item at 'D:\Program Files\Microsoft\Exchange Server\V15\' because it is in use.".
    [07/14/2015 21:34:07.0969] [1] [ERROR] Cannot remove the item at 'D:\Program Files\Microsoft\Exchange Server\V15\' because it is in use.
    [07/14/2015 21:34:07.0969] [1] 1.  ErrorRecord: Cannot remove the item at 'D:\Program Files\Microsoft\Exchange Server\V15\' because it is in use.
    [07/14/2015 21:34:07.0969] [1] 1.  ErrorRecord: System.Management.Automation.PSInvalidOperationException: Cannot remove the item at 'D:\Program Files\Microsoft\Exchange Server\V15\' because it is in use.
    [07/14/2015 21:34:07.0969] [1] [ERROR] The following error was generated when "$error.Clear();
                        $regPath='HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall';
                        
                        $PackageGUIDRegEx = "{DEDFFB[0-9a-fA-F]{2}-42EC-4E26-[0-9a-fA-F]{4}-430E86DF378C}";
                        
                        $InstallPath = (Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\ExchangeServer\v15\setup').MsiInstallPath;
                        
                        if(test-path ($regPath))
                        {
                            Write-ExchangeSetupLog -info ("Removing " +  $RoleLanguagePackType + " Language Packs.");
                            Get-ChildItem ($regPath) | foreach{
                                if($_ -match "(?<ProductCode>$PackageGUIDRegEx)") {
                                    $langPackPackageCode = $matches['ProductCode'];
                                    if($langPackPackageCode -ne $null -and $langPackPackageCode.Length -ne 0) {
                                        Write-ExchangeSetupLog -info ("Removing package $langPackPackageCode");
                                        $language = $langPackPackageCode.Substring(20,4);
                                        $logFilePath = [IO.Path]::Combine($RoleLogFilePath,"Uninstall") + '.' + $language + '.' + "Client" + "." + $RoleLogDateTime + ".msilog";
                                        uninstall-MsiPackage -ProductCode ($langPackPackageCode) -LogFile ($logFilePath);
                                    };
                                };
                            };
                            Remove-Item -Path $InstallPath -Include *.Localized.js -Recurse
                            Remove-Item -Path $InstallPath -Include *.Localized.min.js -Recurse
                            Write-ExchangeSetupLog -info "Remove Language Packs completed.";
                        };
                    
            " was run: "Cannot remove the item at 'D:\Program Files\Microsoft\Exchange Server\V15\' because it is in use.".
    [07/14/2015 21:34:07.0969] [1] [ERROR] Cannot remove the item at 'D:\Program Files\Microsoft\Exchange Server\V15\' because it is in use.
    [07/14/2015 21:34:07.0969] [1] [ERROR-REFERENCE] Id=LanguagePackUninstallationComponent___9a89e7313d524f298d51c24709f69125 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    [07/14/2015 21:34:07.0969] [1] Setup is stopping now because of one or more critical errors.
    [07/14/2015 21:34:07.0969] [1] Finished executing component tasks.
    [07/14/2015 21:34:08.0031] [1] Ending processing remove-InstalledLanguages
    [07/14/2015 21:34:08.0047] [0] The Exchange Server setup operation didn't complete.  More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
    [07/14/2015 21:34:08.0047] [0] End of Setup

    Wednesday, July 15, 2015 12:48 PM
  • Running process explorer I was able to stop the search process that was holding files open in the v15 folder, but still cannot uninstall.  The process explorer shows no files in use when I start the uninstall, but then when it runs a bunch of stuff shows in use in the v15/bin folder.  If I remove that folder an again try the uninstall from the cd file setup.exe it says it cannot find the setup.exe in the v15/bin folder.  So it is almost like it is running the setup.exe that is in the v15/bin folder in the Exchange install and then can't uninstall itself because it is in use.  Anyone know how to get around this?

    • Edited by k2009 Wednesday, July 15, 2015 2:17 PM
    Wednesday, July 15, 2015 2:17 PM
  • I was able to uninstall Exchange 2013 using the exsetup utility within the v15\bin folder.

    Still will probably rebuild it as don't want crud lying around in the registry and such.  I am marking Edwards first answer as the answer as removing the db in adsiedit allowed me to proceed with the initial install, and it probably would have worked if not for the name issues.

    Thank you,

    Kurt

    Wednesday, July 15, 2015 4:55 PM