How to get SMS delivery reports on iPhone 4, 3GS or... Since I received my new iPhone 3G, I've been wondering why Apple didn't add an option for text message delivery reports to the iPhone 3G software (SMS delivery reports). Sometimes when you send a text...
A Simple System to Reorganise Your Emails After a Getting Things Done micro-seminar given by a friend, I took it upon myself to start learning about, and introducing, GTD into my life. I’m not an expert but a few simple changes have made a huge...
iPhone EDGE settings for Vodafone UK Well my unlocked iphone has finally arrived from the US, and I've been tweaking it for the last couple of hours so that everything is working properly. When I tried to fire up Safari on the iPhone I...
I had my old Telewest TV Drive (now called V+ box) replaced recently. Unfortunately the HDMI port had become faulty and this was causing interference / picture cut outs. I understand that there is a known fault with the HDMI port on TV Drives which can cause the solder joint to fail. The new box is painted matt black (instead of silver) and seems fine.
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.
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
