Exchange 2010

[Jawloms]

I have inherited an Exchange 2010 setup with no service packs. The server is incredibly slow, and there are two databases on (one called "temp" and one called "Mailbox Database 0102828846") with staff and students randomly strewn across either. I want to move to 2013 (or possibly even 2016 even though it's a bit new still) but can't until I apply SP3. It won't apply. I have made a copy of it and a DC in a virtual environment in their own VLAN. I have come across so many errors during the process of applying the SP and managed to resolve them all up until this one. It goes through quite happily until "Hub Transport Role" and then gives the below;

 

Hub Transport Role

Failed

 

Error:

The following error was generated when "$error.Clear();

$vdirName = "PowerShell (Default Web Site)";

$proxyVdirName = "PowerShell-Proxy (Default Web Site)";

$InternalPowerShellUrl="http://" + $RoleFqdnOrName + "/powershell";

$vdir = get-PowerShellVirtualDirectory -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $vdirName };

$proxyVdir = get-PowerShellVirtualDirectory -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $proxyVdirName };

 

if ($vdir -ne $null -or $proxyVdir -ne $null)

{

update-PowerShellVirtualDirectoryVersion -DomainController $RoleDomainController;

}

 

if ($vdir -eq $null)

{

$vdirName = "PowerShell";

new-PowerShellVirtualDirectory $vdirName -InternalUrl $InternalPowerShellUrl -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$false -RequireSSL:$false;

}

else

{

Set-PowerShellVirtualDirectory $vdirName -InternalUrl $InternalPowerShellUrl -DomainController $RoleDomainController -WindowsAuthentication:$false -RequireSSL:$false;

}

 

if ($proxyVdir -eq $null)

{

$proxyVdirName = "PowerShell-Proxy";

new-PowerShellVirtualDirectory $proxyVdirName -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$true -RequireSSL:$true -AppPoolId "MSExchangePowerShellProxyAppPool" -Path ($RoleInstallPath + "ClientAccess\PowerShell-Proxy");

}

else

{

Set-PowerShellVirtualDirectory $proxyVdirName -DomainController $RoleDomainController -WindowsAuthentication:$true -RequireSSL:$true;

}

" was run: "A failure occurred while trying to update metabase properties.".

 

A failure occurred while trying to update metabase properties.

 

The system cannot find the path specified.

 

Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex88D115&l=0&cl=cp

 

Elapsed Time: 00:05:28

 

 

 

I have obviously done a lot of Googling, but can't find anything overly helpful, and if I click on the "Click here for help", it takes me to an article which says "You've found an error that doesn't have an article written about it.". Anyone got any ideas please?

 

Thank you

 

Stuart

[Sagima]

I would probably install another exchange 2010 (virtual) and migrate the mailboxes to it - probably to some more sensible named databases (teachers, support, pupils or similar).

Then you can use the server your exchange is currently on to put your new exchange 2013 on (which you can do with just the latest CU release rather than having to do all the patching). Remember to run the uninstaller on that exchange to remove it properly to save you looking through adsi edit, manually removing references.

(of course random references to old exchange servers in ad might be why you can't update your current one - they were the the cause of al my exchange problems when I started here)

[IanT]

No need to install another exchange server, look here:

 

https://supertekboy.com/2014/05/06/5-errors-upgrading-to-exchange-2010-sp3-and-how-to-fix-them/#.VhTf0PTz7GY

[Jawloms]

@Sagima - I had wondered if I may have to build another 2010 server and move everyone to that.

@IanT - If I do step five only in that list, then the upgrade completes at last, thank you! OWA no longer works though......

[3s-gtech]

Did you re-create the mailbox at the end?

[Jawloms]

The Discovery one? Yes.

[featured_spectre]

Have you given OWA the right cert in IIS?

[Jawloms]

It's looking like it simply doesn't work in a virtual environment which has been segregated from the rest of the network. I'd assumed that the exchange server and the DC with all the roles on it would be enough, but apparently not. I didn't actually see if OWA worked in this environment before I applied SP3, so I'm going to restore it again and check. I wanted to restore anyway to double check my steps work.

[IanT]

What errors are you seeing with OWA?

 

A screenshot may be useful.