Outlook Web App didn’t initialize error after Ex2010 SP1 Update Rollup 3

Environment:

4x Win2k8 R2 CAS/HUB Servers

4x Win2k8 R2 Mailbox Servers

All servers were installed with Update Rollup3 from a powershell window run as admin. i.e. Administrator was in titlebar

On all servers UR3 was installed with the following paramaters E:\Exchange2010Scripts\Exchange2010-KB2529939-v3-x64-en_UpdateRollup3.msp /lxv* c:\SP1UR3.log

The rollup on all servers stated that it finished sucessfully in the log file, the event log and through the installer.

However 1 out of the 4 CAS servers had a serious OWA issue:

 

Outlook Web App didn’t initialize. If the problem continues, please contact your helpdesk.

Couldn’t find a base theme (folder name=base).

Checking the C:\ExchangeSetupLogs\Updatecas.log showed the reason for this error..

  [15:45:24] ***********************************************
[15:45:24] * UpdateCas.ps1: 15/10/2010 3:45:24 PM
[15:45:24] Error updating OWA/ECP: The term 'Get-ExchangeServer' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
[16:59:55] ***********************************************
[16:59:55] * UpdateCas.ps1: 15/10/2010 4:59:55 PM
[16:59:55] Error updating OWA/ECP: The term 'Get-ExchangeServer' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
[20:33:15] ***********************************************
[20:33:15] * UpdateCas.ps1: 4/05/2011 8:33:15 PM
[20:33:15] Error updating OWA/ECP: The term 'Get-ExchangeServer' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
[22:59:19] ***********************************************

As can be seen this same issue occured on previous update rollups on this server.

To fix the problem i manually re-ran the C:\Program Files\Microsoft\Exchange Server\V14\Bin\UpdateCas.ps1 script, and now the updatecas.log shows it sucusfully updated owa/ecp directories, and everything was working again.

My question is why does this server keep doing this, and i have seen numerous people post questions about the same issue.

I looked at the updatecas.ps1 script and there is a line to add the Exchange snap in:

add-PSSnapin -Name Microsoft.Exchange.Management.PowerShell.E2010

So why in some instances is this not working and why isnt this error being captured by the update rollup?

UPDATE: Thanks to IAMEdward from technet forums we have a solution & a explanation for why it is occurring!

The reason this is happening is there are some Powershell registry keys missing in [HKEY_LOCAL_MACHINE\SOFTWARE\MicrosoftPowerShell\1\PowerShellSnapIns].  In my case Microsoft.Exchange.Management.PowerShell.E2010.reg and Microsoft.Exchange.Management.Powershell.Support.reg were missing on the Hub/CAS server that was throwing this error in OWA.  I exported the registry keys from one of my other CAS servers and then imported them into the one that was missing the keys.

I can confirm the CAS server i was having the issue with, also had the Powersehell.E2010 and Support reg keys missing under [HKEY_LOCAL_MACHINE\SOFTWARE\MicrosoftPowerShell\1\PowerShellSnapIns].

When i ran get-pssnapin -registered i only had the Microsoft.Exchange.Management.PowerShell.Setup.

So I was missing

Microsoft.Exchange.Management.PowerShell.E2010
Microsoft.Exchange.Management.Powershell.Support

Exporting the REG from another CAS and loading it in the broken CAS, looks to have solved the probelem as i can now run Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010 without error.

This was not picked up because any exchange commands were always run from the Exchange management Shell, which loads  E:\Exchange Server\V14\bin\RemoteExchange.ps1′; Connect-ExchangeServer -auto” which obviously uses a different method to connect(than the standard add-pssnapin), which worked even when the above registry keys were not there.

Also it would seem that the error checking in the Exchange installers is not very good, as all install log files exit sucessfully with a zero exit code.

So might be a good idea for MS to put some better error checking in, and at the very least verify the above reg keys exist.

Cheers All

Advertisements
This entry was posted in Computers and Internet. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s