Problem : microsoft exchange system attendant service on local computer started and then stopped

Problem : microsoft exchange system attendant service on local computer started and then stopped

my exchange server recently will not let me start the MS Exchange SA service.  when i start it i get the following error, “microsoft exchange system attendant service on local computer started and then stopped.  Some services stop automatically if they have no work to do, for example, the perfomance logs and alerts service.”  i dont really know what the shift before me did that might have affected this.

i get the following errors in event viewer:

Event Type:      Error
Event Source:      MSExchangeSA
Event Category:      General
Event ID:      1005
Date:            7/24/2009
Time:            10:11:55 PM
User:            N/A
Computer:      IMEFN01E
Description:
Unexpected error No site name is available for this machine. Facility: Win32 ID no: c007077f Microsoft Exchange System Attendant  occurred.

For more information, click http://www.microsoft.com/contentredirect.asp.

————————–———-———-———-———-———-———-———-——

Event Type:      Error
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2114
Date:            7/24/2009
Time:            10:11:55 PM
User:            N/A
Computer:      IMEFN01E
Description:
Process MAD.EXE (PID=3172). Topology Discovery failed, error 0x8007077f.

For more information, click http://www.microsoft.com/contentredirect.asp.

————————–———-———-———-———-———-———-———-——

Event Type:      Error
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2114
Date:            7/24/2009
Time:            10:14:38 PM
User:            N/A
Computer:      IMEFN01E
Description:
Process INETINFO.EXE (PID=1260). Topology Discovery failed, error 0x8007077f.

For more information, click http://www.microsoft.com/contentredirect.asp.


Solution : microsoft exchange system attendant service on local computer started and then stopped

run the command (install windows support tools)
nltest /dsgetsite
does it show the correct site name? if no, and error is DSGetSiteName failed: Status = 1919 0x77f ERROR_NO_SITENAME ?

Associate a Subnet with Default-First-Site-Name
Click Start, click Programs, point to Administrative Tools, and then click Active Directory Sites and Services.
Double-click the Sites node that corresponds to the Site where the Exchange Server resides, and then right-click Subnets.
Click New Subnet on the shortcut menu.
Type the IP address, and the subnet mask of the subnet, and then click Default-First-Site-Name on the Site Name list. Click OK to close the New Object-Subnet dialog box.

Start Registry Editor, Regedit.exe.
Locate and click the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters
Double-click the SiteName value, and then type the site name (as it is configured in Active Directory) in the Value Data box.NOTE: If the SiteName value does not exist, follow these steps to create it:

On the Edit menu, point to New, and then click String Value.
Type SiteName to change the name of the newly created value, and then press ENTER.
Double-click the SiteName value, and then type the site name in the Value Data box.
Quit Registry Editor.
Restart the computer.
Start the System attendant service. In Computer Management, double-click Services and Applications, click Services, right-click Microsoft Exchange System Attendant, and then click Start on the shortcut menu.
NOTE: The HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters registry key does not apply to domain controllers. After you manually configure site membership on the member server, the computer may still not be able to receive site-based policies or be able to form a security-enhanced channel with the correct domain controller.