Exchange 2000/2003 System Attendant does not start after disaster recovery installation, event ID 90
After you run an Exchange disaster recovery installation, System Attendant may not start, and you may receive the following event ID messages:
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 9022
Description:
Microsoft Exchange System Attendant encountered an error while processing the security data for Exchange server ''.
For more information, click
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 9149
Description:
Microsoft Exchange System Attendant failed to start Exchange server ''. Error code '0x80070005'.
For more information, click
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 1005
Description:
Unexpected error Access denied. Facility: LDAP Provider ID no: 80070005 Microsoft Exchange System Attendant occurred.
CAUSE
This issue may occur if the server account does not have the correct permissions on the Exchange server container in Active Directory.
RESOLUTION
To resolve this issue, use ADSI Edit to grant the correct permissions for the server account on the Exchange server container in Active Directory.
ADSI Edit is located in the SupportTools folder of the Windows 2000 or Windows Server 2003 CD. To install Windows 2000 or Windows Server 2003 Support Tools, follow these steps:
1. Insert the Windows 2000 Server or Windows Server 2003 CD in your CD-ROM drive.
2. Click No if you are prompted to reinstall Windows 2000 Server or Windows Server 2003.
3. Open the Support/Tools folder. For complete setup information, see the Sreadme.doc file that is available in this folder.
4. Double-click Setup.exe or suptools.msi.
5. Follow the instructions that appear on your screen.
How to Use ADSI Edit to Grant the Correct Permissions
Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.
1. Start ADSI Edit.
1. Click Start, click Run, type adsiedit.msc, and then click OK.
2. Click Tools, and then click ADSI Edit.
2. Expand Configuration, expand Configuration (CN=Configuration,DC=domain,DC=com), expand Services, and then expand Microsoft Exchange.
3. Expand OrganizationName, expand Administrative Groups, expand AdministrativeGroupName, and then expand Servers.
4. Right-click Server Name, and then click Properties.
5. Click the Security tab, verify that the server object is in the list of accounts with rights, and then verify that the Allow check box for Full Control is selected. If this permission is not selected, click to select the Allow check box for Full Control, and then click OK.
6. Quit ADSI Edit.
7. Wait for the change to replicate among the domain controllers.
8. Start System Attendant.[@more@]
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 9022
Description:
Microsoft Exchange System Attendant encountered an error while processing the security data for Exchange server '
For more information, click
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 9149
Description:
Microsoft Exchange System Attendant failed to start Exchange server '
For more information, click
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 1005
Description:
Unexpected error Access denied. Facility: LDAP Provider ID no: 80070005 Microsoft Exchange System Attendant occurred.
CAUSE
This issue may occur if the server account does not have the correct permissions on the Exchange server container in Active Directory.
RESOLUTION
To resolve this issue, use ADSI Edit to grant the correct permissions for the server account on the Exchange server container in Active Directory.
ADSI Edit is located in the SupportTools folder of the Windows 2000 or Windows Server 2003 CD. To install Windows 2000 or Windows Server 2003 Support Tools, follow these steps:
1. Insert the Windows 2000 Server or Windows Server 2003 CD in your CD-ROM drive.
2. Click No if you are prompted to reinstall Windows 2000 Server or Windows Server 2003.
3. Open the Support/Tools folder. For complete setup information, see the Sreadme.doc file that is available in this folder.
4. Double-click Setup.exe or suptools.msi.
5. Follow the instructions that appear on your screen.
How to Use ADSI Edit to Grant the Correct Permissions
Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.
1. Start ADSI Edit.
1. Click Start, click Run, type adsiedit.msc, and then click OK.
2. Click Tools, and then click ADSI Edit.
2. Expand Configuration, expand Configuration (CN=Configuration,DC=domain,DC=com), expand Services, and then expand Microsoft Exchange.
3. Expand OrganizationName, expand Administrative Groups, expand AdministrativeGroupName, and then expand Servers.
4. Right-click Server Name, and then click Properties.
5. Click the Security tab, verify that the server object is in the list of accounts with rights, and then verify that the Allow check box for Full Control is selected. If this permission is not selected, click to select the Allow check box for Full Control, and then click OK.
6. Quit ADSI Edit.
7. Wait for the change to replicate among the domain controllers.
8. Start System Attendant.[@more@]
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/208722/viewspace-1027000/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- After mysql installation, we need to change the password of root as belowMySql
- Task01&Task02:課程簡介、Installation、Getting Start
- function ALV 獲取OO ALV event IDFunction
- ORA-00445: background process "J000" did not start after 120 seconds
- [20191119]測試dbms_system.wait_for_event.txtAI
- How to redirect to a specific web page after sign out from Entra IDWeb
- alter system set event和set events的區別
- IOMESH Installation
- SAP Cloud for Customer(C4C)後臺ABAP系統的System ID和client IDCloudclient
- 2.3.3.2 Application InstallationAPP
- A Tomcat 8.0 installation is expectedTomcat
- [Windows無法連線到 System Event Notification Service服務]解決方案Windows
- pgsql 執行建庫指令碼時候出現ERROR: relation "xxx_id_seq" does not existSQL指令碼Error
- Adding Drivers into VMWare ESXi Installation Image
- 07-Plugin ‘scala’ is incompatible with this installationPlugin
- Include manifest for over-the-air installationAI
- Exchange Online Mailbox RestorationAIREST
- start uniappAPP
- Rockchip RK3588 - Rockchip Linux Recovery recovery原始碼分析Linux原始碼
- JDK 載入jar中的檔案資源出現Cannot be resolved to absolute file path because it does not reside in the file systemJDKJARIDE
- Exchange - Add Owner of Distribution Group
- event_x ()、event_y ()、event_x_root ()、event_y_root ()
- Re:從零開始的機器學習 - Titanic: Machine Learning from Disaster機器學習MacAST
- ‘map’ does not name a type
- What does -> do in clojure?
- does not support SSL connections
- Windows Server 2019 Installation 安裝.net 3.5WindowsServer
- 外部插入.after()
- Microsoft Office 2003 Web ComponentsROSWeb
- rac中 crsctl start/stop crs and crsctl start/stop cluster 區別
- Data exchange of settype COMM_PRFREEATTR
- Exchange 2013 管理 視訊教程
- 【RabbitMQ】direct type exchange example in golangMQGolang
- 【RabbitMQ】topic type exchange example in golangMQGolang
- 【RabbitMQ】fanout type exchange example in golangMQGolang
- 手機刷TWRP Recovery
- Windows2000/2003/2008伺服器IIS匯入伺服器證書的方法(IIS5、IIS6、IIS7)Windows伺服器
- 3.1.5.6 Forcing an Instance to Start
- 開發springboot startSpring Boot