Lỗi ad lds event 1161 trong windows server năm 2024
|
Hãy nâng cấp lên Microsoft Edge để tận dụng các tính năng mới nhất, bản cập nhật bảo mật và hỗ trợ kỹ thuật.
Trong bài viết nàyThis article describes an issue in which ADAM general Event ID 1161 is logged on an AD LDS server. Applies to: Windows Server 2012 R2 Original KB number: 3080830 SymptomsThe following event is logged in the ADAM log every time an instance is restarted on an AD LDS server that's running Windows Server 2012 R2. CauseThe address book hierarchy table does not exist in the Active Directory Lightweight Directory Services (AD LDS) database. Therefore, the event is triggered during service startup. Events from ‘ADAM.Events.xml’ could not be enumerated. (This error might be cleared after required post-installation configuration for Active Directory Lightweight Directory Services is completed.) Server Manager cannot get event data from the target server. The user might not have access rights to the target server event log, or event log files might not contain valid data. For some roles and features (Hyper-V, Print and Document Services, AD LDS), this error can occur after installation, but before required post-installation configuration has been completed. The error is resolved after post-installation configuration is complete. For AD FS, this error can occur if web agents are the only role services installed, but there is currently no known resolution for this case of the error. I went through the AD and couldn't find anything. This problem started on Saturday. I haven't found anything that might have caused it. The Exchange Server 2010 Edge Transport server role uses an instance of Active Directory Lightweight Directory Services (AD LDS) to store information about recipients and server configurations. In some situations you may wish to connect to the AD LDS instance with ADSEdit.msc to view or make changes to data. First you need to determine the port that the Exchange instance of AD LDS is running on. On the Edge Transport server open a command prompt and use the dbdsutil command to list the AD LDS instances. C:\>dsdbutil dsdbutil: list instances Instance Name: MSExchange Long Name: MSExchange LDAP Port: 50389 SSL Port: 50636 Install folder: C:Windows Database file: C:Program FilesMicrosoftExchange ServerV14TransportRolesDataAdamadamntds.dit Log folder: C:Program FilesMicrosoftExchange ServerV14TransportRolesDataAdam Service state: Running Next, launch ADSIEdit.msc, and open a new connection. Set the naming context to Configuration and type in the server name (or localhost) followed by the port your AD LDS instance is running on. Click OK to connect and you are now connected to the AD LDS instance being used by the Edge Transport server, and can view or modify the AD LDS data as necessary. About the AuthorPaul is a former Microsoft MVP for Office Apps and Services. He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server. Paul no longer writes for Practical365.com. Any of this relevant, has the server been restarted, has all installed roles been configured, are you running server manager with an account with appropriate permissions, are you running AD FS with the web agents role?: Server Manager cannot get event data from the target server. The user might not have access rights to the target server event log, or event log files might not contain valid data. For some roles and features (Hyper-V, Print and Document Services, AD LDS), this error can occur after installation, but before required post-installation configuration has been completed. The error is resolved after post-installation configuration is complete. For AD FS, this error can occur if web agents are the only role services installed, but there is currently no known resolution for this case of the error. Was this post helpful? thumb_up thumb_down VM's, running on a Dell 610 and 420, HyperV ESXi 5.5. Each is running on a different host. Was this post helpful? thumb_up thumb_down I've restarted, its accessing the server data for itself, and we are not on HyperV. Was this post helpful? thumb_up thumb_down Are there really that many roles on the dc's? 0 of 1 found this helpful thumb_up thumb_down They both appear to have LDS on them, has LDS been configured? Was this post helpful? thumb_up thumb_down No it hasn't. COuld having it in there be a cause of this? Was this post helpful? thumb_up thumb_down It says right in the text I posted from the troubleshooting document that an un-configured LDS role will cause this. 2 found this helpful thumb_up thumb_down Any update on this issue? 1 found this helpful thumb_up thumb_down Yes, removing the LDS roles on both DC's solved the problem after a reboot. 1 found this helpful thumb_up thumb_down Fantastic tip cduff !!!! I removing the LDS role and solved problem!! \o/ Many thanks. Was this post helpful? thumb_up thumb_down how do i reomve the LDS role pls the procedure i have restarted the both server but still show same error Was this post helpful? thumb_up thumb_down Just go remove Role and Features in Server manager Was this post helpful? thumb_up thumb_down If it is grayed out in server manager. Run PowerShell cmd Remove-WindowsFeature ADLDS You don't even have to reboot. Was this post helpful? thumb_up thumb_down I know that this post is a bit old, but thought i should just post to say thanks, removing ADLS via powershell worked a treat. Was this post helpful? thumb_up thumb_down Good to hear. Don't forget though the advice above regarding configuration. The reason for the issue is that ADLDS needs further configuration. |
