EMC Crash with exception “FX:{A5406CA3-6393-48a0-8827-CF06F0C94C55}”

There has been many instances where the Exchange Management console crashes when I used to work on Exchange Servers, particularly on Exchange Server 2010. Most of the time the issue gets resolved when you end the task from Task Manager and launch a new session.

However, in this particular Exchange Server I was working with, the MMC kept on crashing throwing exceptions. This post provides the steps to resolve a similar issue.

The Exception I kept on getting is shown below :

FX:{A5406CA3-6393-48a0-8827-CF06F0C94C55}

mmc crash

This issue can be resolved with the help of a small .bat script..

All you have to do is in a notepad copy the below script and save it in .bat format.

set __COMPAT_LAYER=RUNASINVOKER
set COMPLUS_Version=v2.0.50727
“C:\Program Files\Microsoft\Exchange Server\V14\Bin\Exchange Management Console.msc”

Execute the script and confirm the working of EMC.

 

Reference :- https://social.technet.microsoft.com/Forums/exchange/en-US/02881780-9982-4a5a-a7fd-1cf609913779/exchange-2010-installing-emc-sp2-on-windows-8?forum=exchangesvrdeploylegacy

Advertisements

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

Recently, I faced an issue logging in to OWA on our client’s Exchange 2010 server. The error reported was as follows :

Outlook Web App didn’t initialize. If the problem continues, please contact your helpdesk.
Couldn’t find a base theme (folder name=base)

owa1

Initial troubleshooting steps were taken, like restarting the Microsoft Exchange Form Based Authentication service, re-creating OWA virtual directories etc..

Upon further researching on the issue, I found a similar post online where the OWA crashed after installing the Exchange updates..

So, in order to resolve the issue all you need to do is launch Exchange Management Shell, navigate to the location C:\Program Files\Microsoft\Exchange Server\V14\Bin and then execute the power shell script UpdateCas.ps1.

owa2

This script will find your OWA/ECP virtual directories, update them and make some modifications to metabase etc.. Once completed, you will be able to access your OWA/ECP like before.. 🙂

 

Reference :- https://social.technet.microsoft.com/Forums/exchange/en-US/dd91598d-3af9-4a98-8493-34726c763c62/owa-failed-to-initialize-after-install-of-rollup-1-for-exchage-sp1?forum=exchange2010

Procedure to delete shadow copies on Windows server 2003 and later

Volume Shadow Copy :-

VSS or Volume Shadow Copy is a service that creates snapshots or point in time copy  [shadow copies] of disk volumes. This service was introduced in Windows Server 2003.

Components of VSS :->

  • VSS Writer : Each VSS-aware application installs its own VSS writer to a computer during the initial installation.
  • VSS Requestor : Software that commands the creation of Shadow Copies. It is actually the backup application itself.
  • VSS Provider : It takes care of keeping the shadow copies after that consistent point-in-time

How to delete shadow copies ?

vssadmin delete shadows /for=<ForVolumeSpec> [/oldest | /all | /shadow=<ShadowID>] [/quiet]

To get the shadowID, use the command : vssadmin list shadows
  • /for=<ForVolumeSpec> – Specifies the volume for which the shadow copies needs to be deleted
  • /oldest – Deletes only the oldest shadow copy
  • /all – Deletes all the shadow copies of the specified volume
  • /shadow=<ShadowID> – Deletes the shadow copy specified by the ShadowID
  • /quiet – command will not display any messages

How to troubleshoot VSS errors ?

In CMD, execute the command vssadmin list writers. In the result, check whether any errors are reported for the writers. Also, check the result for vssadmin list providers and troubleshoot if any errors are reported.