I have a Exchange 2007 SP1 Enterprise server running on a Windows 2003 R2 64-bit server. IIS is version 6. It has been running great for over two years. It has been patched on a regular basis. I have been backing up the data stores with Backup Exec 12.5. That has been working great too. On Friday, the backups failed and again on Monday. I started looking into the issue (I am part time here) and found that I the backup job did not recognize the data stores. I tried to browse to them through backup exec, but was not able to locate. I tried reloading the Exchange server agent, but have no luck. The error message left indicated that there may be a mismatch on the service pack and security fix levels. I normally do those types of updates after hours. When I tried to open the MMC on the backup server, I received the error message: -------------------------------------------------------- Microsoft Exchange Error -------------------------------------------------------- The following error(s) were reported while loading topology information: Get-ActiveSyncVirtualDirectory Failed Error: An error occurred while trying to access IIS (Internet Information Service) metabase. Make sure the Internet Information Service Manager component is installed and configured properly. Unknown error (0x80005000) Get-OabVirtualDirectory Failed Error: An error occurred while trying to access IIS (Internet Information Service) metabase. Make sure the Internet Information Service Manager component is installed and configured properly. Unknown error (0x80005000) Get-OWAVirtualDirectory Failed Error: An error occurred while trying to access IIS (Internet Information Service) metabase. Make sure the Internet Information Service Manager component is installed and configured properly. Unknown error (0x80005000) -------------------------------------------------------- OK -------------------------------------------------------- I then tried to load the MMC on the Exchange server and received this error message: Server stack trace: at Microsoft.Exchange.Data.Directory.SuitabilityVerifier.IsServerSuitable(String fqdn, Boolean isGlobalCatalog, NetworkCredential credential, LocalizedString& errorMessage) at Microsoft.Exchange.Data.Directory.SuitabilityVerifier.IsServerSuitableIgnoreExceptions(String fqdn, Boolean isGlobalCatalog, NetworkCredential credential, LocalizedString& errorMessage) at Microsoft.Exchange.Data.Directory.DirectoryServicesTopologyProvider.FindDomainController(Domain domain, String site, NetworkCredential credential) at Microsoft.Exchange.Data.Directory.DirectoryServicesTopologyProvider.GetDCForDomain(String fqdn, NetworkCredential networkCredential) at Microsoft.Exchange.Data.Directory.DirectoryServicesTopologyProvider.DiscoverDC() at Microsoft.Exchange.Data.Directory.DirectoryServicesTopologyProvider..ctor() at Microsoft.Exchange.Data.Directory.TopologyProvider.InitializeInstance() at Microsoft.Exchange.Data.Directory.TopologyProvider.GetInstance() at Microsoft.Exchange.Data.Directory.AdminSessionADSettings.get_ConfigurationDomainController() at Microsoft.Exchange.Management.SnapIn.Esm.ExchangeSystemManagerSettings.EnforceADSettings() at Microsoft.Exchange.Management.SnapIn.Esm.MasterDataSet.EnforceADSettings() at Microsoft.Exchange.Management.SnapIn.Esm.ExchangeRootSnapIn.Initialize(IProgressProvider progressProvider) at Microsoft.Exchange.Management.SnapIn.ExchangeScopeNode.OnExpand(AsyncStatus status) at Microsoft.ManagementConsole.NodeSyncManager.ProcessRequest(NodeRequestInfo info, IRequestStatus requestStatus) at Microsoft.ManagementConsole.SnapIn.ProcessRequest(Request request) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request) at Microsoft.ManagementConsole.Executive.RequestStatus.BeginRequest(IMessageClient messageClient, RequestInfo requestInfo) at Microsoft.ManagementConsole.Executive.SnapInRequestOperation.ProcessRequest() at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback) The MMC works fine on my workstation and on another workstation in the IT department. I opened a shell from my workstation and typed in the following with success: Get-ActiveSyncVirtualDirectory Get-OabVirtualDirectory Get-OWAVirtualDirectory When I tried this from the server, I received the following for each of the above commands: WARNING: An unexpected error has occurred and debug information is being generated: Could not load file or assembly 'System.DirectoryServices.Protocols, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. Get-OwaVirtualDirectory : Could not load file or assembly 'System.DirectoryServ ices.Protocols, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a 3a' or one of its dependencies. The system cannot find the file specified. At line:1 char:23 Email, Blackberry Enterprise server, and OWA work fine and there have been no other user interruptions. I have rebooted the server and the backup server with the same results. No updates have been applied to the servers in close to 3 weeks. Theses errors appear to be on the mail server and the backup server only. I know that this is a lot information, but I wanted to be as detailed as possible. Thanks for any assistance that you can give.

I applieWindows Critical Updates on the server, but still the same issues.

I opened a support call with Microsoft and eventually a solution presented itself.It was found that the .Net that I had installed had become corrupt. I had to perform a repair of .Net 3.5.1 to resolve the issue .NET Framework 3.5 SP1 - silent repair "%windir%\Microsoft.NET\Framework\v3.5\Microsoft .NET Framework 3.5 SP1\setup.exe" /q /norestart .NET Framework 3.5 SP1 - unattended repair "%windir%\Microsoft.NET\Framework\v3.5\Microsoft .NET Framework 3.5 SP1\setup.exe" /qb /norestart A reboot was required after the update had occured.This resolved the issue.