MSExchangeSA 1005

Product:	Exchange
ID:	1005
Source:	MSExchangeSA
Version:	6.5.0000.0
Message:	Unexpected error error code occurred.
Explanation
The appearance of an Event 1005 in the application log is usually accompanied by the problem of the System Attendant not starting. DNS Issues. For example, DNS may not be configured correctly on the Exchange Server. This is particularly possible if there is more than one Network Card on the server. System Attendant Service configured to start with some other account and not the Local System Account. Exchange Domain Servers Global Security Group may be missing, may have been moved to another container or may have permissions on it modified. File and Print Sharing may be disabled. NetBIOS over TCP/IP may be disabled. NetBIOS TCP/IP Helper Service may be disabled.
User Action
Check DNS Settings on the Server and ensure that they are correct. Ensure that the System Attendant Service is starting with the Local System Accountant. Ensure that the Exchange Domain Servers Global Security Group is present in the USERS Container. Ensure that File and Print Sharing and NetBIOS over TCP/IP are not disabled. Ensure that the TCP/IP Helper Service is not disabled.

Event ID: 1005
Source	MSExchangeSA
Type	Error
Description	Unexpected error <error description> occurred.
Things to understand	Why are some errors “unexpected”?
Comments	Adrian Grigorof (Last update 11/29/2003): Event 1005 seems to be a general event code used to indicate that something the System Attendant needs is missing or corrupt. Exchange records a 1005 error in various conditions. See the links below. - Error: 0xc0040000 - The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. Microsoft Exchange Server Information Store ID no: 8004011d-0526-00000000 - As per Microsoft: "Though the event appears to be a problem with the server, it is actually an expected behavior. The Exchange system attendant is attempting to contact the information store, which is not available at the specified time. After the Exchange Setup program has completed, it begins restarting all the related services". See M175100 and M236582. - Error: The specified domain either does not exist or could not be contacted. Facility: Win32 ID no: c007054b Microsoft Exchange System Attendant occurred. - See M252137 - Error: Function 'EcGetProxies2'. Exception: 0xc0000005 Location: 0x78001799 - no info - Error: The required MAPI profile cannot be created because the file MAPISVC.INF cannot be modified. - no info - Error: 80040a01 Microsoft Exchange System Attendant From a newsgroup post: "I recently had occasion to talk at length with an SBS support rep from MS PSS. He told me that he completely uninstalls his anti-virus program before installing service packs, hotfixes, etc. This seems a little extreme to me, but they apparently have a huge database of problems that are caused by anti-virus programs interfering with other processes." Several other posts suggested that the problem was fixed bu uninstalling the antivirus program before any Exchange service packs. -Error: 0x8009000f = "Object already exists" - See M329033,M325964,error code 0x8009000f Mihai Andrei (Last update 9/4/2005): - Error: "0xc0040000 - Network problems are preventing connection to the Microsoft Exchange Server computer. Microsoft Exchange Server Information Store ID no: 80040115-0514-000006bf" - See M288952. - Error: "No site name is available for this computer. Facility: Win32 ID no: c007077f Microsoft Exchange System Attendant" - See M299563. - Error: "An unknown error has occurred. ID no: 80040a01 Microsoft Exchange System Attendant" - See M314294. - Error: "0xc0040000 - The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. Microsoft Exchange Server Information Store ID no: 8004011d-0526-00000000" - See M275538. - Error: "The specified module could not be found. Facility:Win32 ID no: c007007e Microsoft System Attendant" - See M274447. Woodrow Wayne Collins (Last update 8/19/2005): - Error: "Network problems are preventing connection to the Microsoft Exchange Server computer" -For Small Business Server 4.5 as per Microsoft this event does not cause problems. See M228747. - Error: 80040a01 - See M327401. Ionut Marin (Last update 8/15/2005): - Error: The specified directory service attribute or value does not exist. Facility: Win32 ID no: 8007200a Microsoft Exchange System Attendant occurred. As per Microsoft: "This behavior can occur when the permissions set by the first Exchange 2000 server are modified and overwritten with the data from the second server during replication that occurs during the same time frame. This can occur when you install an additional Exchange 2000 server in another domain before the configuration objects of the first installation of Exchange 2000 Server in the grandchild domain have propagated throughout the entire Exchange organization". See M247473 on how to troubleshoot this problem. - Error: Unexpected error. There is no such object on the server.Facility: Win32 ID no: 80072030 Microsoft Exchange System Attendant occurred. See M273389. - Error: Unexpected error The system could not find the environment option that was entered. Facility: Win32 ID no: c00700cb Microsoft Exchange System Attendant occurred. See M833395. - Error: Unexpected error An unknown error has occurred. ID no: fffffffd Microsoft Exchange System Attendant occurred. See M251640. - Error: Unexpected error An unknown error has occurred. Facility: Win32 ID no: c0070810 Microsoft Exchange System Attendant occurred. See M283257. - Error: Unexpected error. The specified procedure could not be found. Facility: Win32 ID no: c007007f Microsoft Exchange System Attendant occurred. See M295620. - Error: Network problems are preventing connection to the Microsoft Exchange Server computer. Facility: Win32 ID no: c0040000 Microsoft Exchange Server Information Store occured. See M252543. - Error: Unexpected error The specified domain either does not exist or could not be contacted. Facility: Win32 ID no: c007054b Microsoft Exchange System Attendant occurred. See M273428. - Error: Unexpected error An unknown error has occurred. Facility: Win32 ID no: c0070952 Microsoft Exchange System Attendant occurred. See M297363. - Error: Unexpected error Access is denied. ID no: 00000005 Microsoft Exchange System Attendant occurred. See M271920. - Error: Unexpected error Access denied. Facility: LDAP Provider ID no: 80070005 Microsoft Exchange System Attendant occurred. See M301364. - Error: Unexpected error An unknown error has occurred. ID no: 80040a01 Microsoft Exchange System Attendant occurred. See M318431, M327844, and M328646. - Error: Unexpected error A local error has occurred. Facility: Win32 ID no: 8007203b Microsoft Exchange System Attendant occurred - See M316710. - Error: Unexpected error Invalid Signature. ID no: 80090006 Microsoft Exchange System Attendant occurred - See M831393. - Error: Unexpected error No site name is available for this machine. Facility: Win32 ID no: c007077f Microsoft Exchange System Attendant occurred - See M316349. - Error: 0xc1050000 - The attempt to log on to the Microsoft Exchange Server computer has failed. The MAPI provider failed. Microsoft Exchange Server Information Store ID no: 8004011d-0512-00000000 - See M888179 and M896703. - Error: Unexpected error - The RPC server is unavailable - See M842471. Event ID 1005 in the application log is usually accompanied by the problem of the System Attendant not starting. See MSEX2K3DB for troubleshooting tips on this event. Anonymous (Last update 8/10/2005): - Error: "Unexpected error A local error has occurred. Facility: Win32 ID no: 8007203b Microsoft Exchange System Attendant occurred" - I received this error and found that the netlogon service had stopped. I started the netlogon service and then the Exchange System Attendant started correctly. Arkady Karasin (Last update 7/28/2004): Unexpected error No site name is available for this machine - An error appears on Exchange 2000 W2K functions as second DC with AD, after removing AD by running DCPROMO. See M322834. Anonymous (Last update 9/22/2003): Error 0xc0040000 - This issue can occur because when you restore an earlier online backup to an empty Mdbdata folder (or restore an earlier online backup with the erase all existing data option) and start the Information Store service, a new Edb.log file is created with the current log generation. See M275602. Mikko Koljander (Last update 9/22/2003): M269489 was pretty much all the information that was needed. It was corrupted/missing registry key (HKEY_CLASSES_ROOT\LDAP\Clsid) for me that prevented the MSExchangeSA from starting. Re-created the key and the correct valua (GUID) and MSExchangeSA started OK along with the rest of the E2K services. According to MS this is problem with the MS product before IE 5.5SP2. Adrian Florin Moisei (Last update 5/9/2003): The error can occur if you try to mount the Mailbox Store or the Public Folder Store. This issue may occur if the Microsoft Windows 2000 Group Policy Object has been deleted or modified. See M316709 link below. Dave Dooley (Last update 4/21/2003): I got this error along with 1197 after I restored Exch 5.5 server to another box with a different name when attempting to start the IS. Then referenced MS M244976. I then just ran Exch SP 4 and all the services restarted. Sorin Ciulpan When this event appears together with 9022 and 9149, as per M325674 "This issue may occur if the server account does not have the correct permissions on both the Exchange Organization container and the server container in Active Directory". For error c00706b7 see M267573. Read also about Error/1028/MSExchangeSA as they are related. Harpert As per M312859, this issue may occur if a domain controller or a global catalog is not available or if there is only a very slow connection to the domain controller or global catalog.