thinkjim.com » servers

Could not start the Microsoft Exchange Management Service on Local Computer Error:

thinkjim — Thu, 21 Feb 2008 20:00:35 +0000

After rebooting a Windows 2000 Advanced Server (running Exchange 2000 SP3) the Microsoft Exchange Management Service Failed to Start. Manually starting the service generated the following error:

“Could not start the Microsoft Exchange Management Service on Local Computer. The service did not return an error. This could be an internal Windows error or an internal service error. If the problem persists, contact your system administrator.

The event log also contained an error:

Event ID: 6
Source: MSExchangeMGMT
Type: Error
Description: The Microsoft Exchange Management service encountered an error (0xThe specified module could not be found.)

A colleague of mine browsed eventID.net. A suggested solution was to check the path to the “atl.dll file in registry”. Registry Key:

HKEY_CLASSES_ROOT\CLSID\{44EC053A-400F-11D0-9DCD-00A0C90391D3}\
InprocServer32 @=”C:\\WINNT\\System32\\ATL.DLL

There were two keys present after searching the registry, one was pointing to the correct location (”c:\winnt\system32\atl.dll”) the other was pointing to c:\program files\ibm\dsa\atl.dll. The article suggests that only the c:\winnt\system32 path will work and the service will fail to start if it is pointing to a different location.

I’m no clearer as to the role that the atl.dll file plays with the exchange management service, but changing the second key so that it was re-pointed to c:\winnt\system32 did the trick. The service started successfully after a manual start. Earlier that week IBMs Dynamic System Analysis Tools (DSA tools) had been installed on the server. For whatever reason the tool seems to have changed one of the ATL.dll registry keys, causing the management service to fail.

Quick Field Report: Unhappy Server after applying SP1 for Backupexec 11D

thinkjim — Sat, 16 Feb 2008 14:16:09 +0000

OS: Windows 2000 SP4 (with rollups)
HP ML350 with HP surestore DLT80 External SCSI Drive Attached.
Offending Software: Backup Exec 11D

After installing service pack 1 for backup exec 11d the server required a reboot. After rebooting and on startup experienced difficulty browsing other machines using explorer and was unable to access the network connections in my network places. Unable to Browse web. First checked physical network connection (replaced cable and rebooted). No effect. Server was responding to ping. Event logs contained errors relating to the remote access service saying that it had failed to start and also:Event ID 7011: Service Control Manager

Type: Error
Description: Timeout (30000 milliseconds) waiting for a transaction response from the RasManservice.

Remote Access connection manager service was hung in ’starting’ state. Checked that the Remote Storage Manager wasn’t running (Backupexec doesn’t like it), it was. Disabled the Remote Storage Service, and attempted to stop the service which was running. Was unable to stop the service although I was able to disabled it. Attempted to shutdown server. Server would not shutdown. pressing the ’soft’ power off button generated an error about the remote storage manager. Had to do a hard reset. Server booted correctly, Remote storage Service remained disabled and did not start. No Remote access errors after bootup all services seem to be working correctly.

Lesson learned: Make sure the Remote Storage Service is disabled when running backupexec.

Restoring an Exchange 2000 server

thinkjim — Sat, 24 Jul 2004 20:00:37 +0000

OK, things aren’t going well. Not much has happened to the blog since I came up with the idea last month. However I have been busy;

Successfully managed to restore an Exchange 2000 server, when both its datastores had gone offline in a dirty state, and its transaction logs had been deleted. (very important to use exchange aware backup software).

Click here for an overview of the process.