A thread in Active Directory Domain Services is waiting for the completion of a RPC made to the following directory service. All domain controllers in the following site that can replicate the directory partition over this transport are currently unavailable. There is insufficient site connectivity information in Active Directory Sites and Services for the KCC to create a spanning tree replication topology. Or, one or more domain controllers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible domain controllers.
AIS Monitoring Platform has discovered that the File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on this domain controller. This could be caused by a number of problems such as corruption in Jet database log file, an invalid root path, a missing directory, a missing disk volume, a file system on the volume that does not support NTFS 5.0, insufficient disk space etc.
AIS Monitoring Platform has discovered that none of the preferred bridgehead servers can replicate the directory partition. This issue may occur if you promote the Windows Server 2003-based computer to act as a domain controller in a Microsoft Windows 2000 domain. You specify a Windows 2000-based server as the preferred bridgehead server for a site in the domain. You transfer the domain naming operations master role to the Windows Server 2003-based domain controller.
AIS Monitoring Platform has discovered that replication has been aborted due to Schema mismatch. Replication requires consistent schema but last attempt to synchronize the schema had failed. It is crucial that schema replication functions properly.
AIS Monitoring Platform has discovered that the Active Directory authentication request are taking long time. A bottleneck can take place on any Windows subsystem or network component, and occurs when one resource prevents a different resource from operating optimally. Incorrectly configured settings or the insufficient distribution of resources between network components can result in bottlenecks occurring.
AIS Monitoring agent has discovered that communicationis broken between DFSR partners, following are common reasons for DFSR failures RPC erros, low disk space for staging area, dynamic rpc ports not open etc
AIS Monitoring Platform has discovered that the DFS Replication cannot replicate the replicated folder because the configured local path is not the fully qualified path name of an existing, accessible local folder. This replicated folder is not replicating to or from this server.
AIS Monitoring Platform has discovered that the DFS Replication service stopped replication, When the DFS Replication service initializes the replicated folders for the replication process, it traverses all related paths to check whether the replicated folders are reparse points that act as symbolic links or that act as mount points. The DFS Replication service expects to open synchronous handles to access these paths. However, it uses the asynchronous handles incorrectly. The DFS Replication service cannot handle the I/O requests that are held by a filter driver. Therefore, the DFS Replication service stops responding.
AIS Monitoring Platform has discovered that the DFS Replication service failed to clean up old staging files for the replicated folder at local path . The service might fail to replicate some large files and the replicated folder might get out of sync.
AIS Monitoring Platform has discovered that the DFS Replication service encountered errors replicating one or more files because adequate free space was not available on volume . This volume contains the replicated folder the staging folder or both. Please make sure that enough free space is available on this volume for replication to proceed
AIS Monitoring Platform has discovered that The DFS Replication service failed to contact the domain controller to access configuration information. Replication is stopped. The service will try again during the next configuration polling cycle.
AIS Monitoring Platform has discovered that there is possible issue with the Replication. Inbound or outbound replication failure causes Active Directory objects that represent the replication topology, replication schedule, domain controllers, users, computers, passwords, security groups, group memberships, and Group Policy to be inconsistent between domain controllers. Directory inconsistency causes either operational failures or inconsistent results, depending on the domain controller that is contacted for the operation at hand. Active Directory depends on network connectivity, name resolution, authentication and authorization, the directory database, the replication topology, and the replication engine. When the root cause of a replication problem is not immediately obvious, determining the cause among the many possible causes requires systematic elimination of probable causes.
AIS Monitoring Platform has discovered that the DC Diagnostic connectvity test failed because GUID DNS name could not be resolved. This can be caused if the zone is not dynamic or the zone doesn’t exist. Multiple DNS servers, but not replicated can also cause this issue.
This alert condition indicates an Active Directory lingering object. One of two conditions exists on the destination domain controller: 1) Event ID 1388: Inbound replication of the lingering object has occurred on the destination domain controller. 2) Event ID 1988: Inbound replication of the directory partition of the lingering object has been blocked on the destination domain controller.
AIS Monitoring agent has discovered that Active Directory Web Services could not service. This service provides a Web Service interface to instances of the directory service Impact : Client applications such as Active Directory PowerShell, will not be able to access or manage any directory service instances that are running locally on this server.
AIS Monitoring agent has discovered that attempt to establish a replication link for the following writable directory partition failed. Impact : This domain controller will be unable to replicate with the source domain controller until this problem is corrected.
AIS Monitoring agent has discovered that ctive Directory Domain Services could not update the object with changes received from the directory service. Simultaneous changes against Active Directory object attributes on different domain controllers may cause this problem. Impact : Replication warning. The directory is busy. It couldnt update object CN=… with changes made by directory GUID._msdcs.domain.
AIS Monitoring agent has detected that local domain controller has not recently received replication. Impact: Domain Controlleer may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled.
AIS Monitoring agent has discovered that server is the owner of FSMO role, but does not consider it valid Impact : Operations which require contacting a FSMO operation master will fail until this condition is corrected.
AIS Monitoring agent has discovered on-premises objects or attributes failed to synchronize with Office 365 due to duplicate entries found Impact: Duplicate users exist in O365 which prevents on-premise AD user to sync with Azure AD.
AIS Monitoring agent has detected the cloud account used to access Office 365 had its password changed due to which Azure AD Connect services won?t start. Impact: New users created will not be synced also any changes made on existing objects i.e. attributes will not be synced to Azure AD.
AIS Monitoring agent has discovered failure while connecting to Windows Azure Active Directory during export. Directory Synchronization connectivity issue found Impact: New users created will not be synced also any changes made on existing objects i.e. attributes will not be synced to Azure AD.
AIS Monitoring agent has detected export to Azure AD failed. Cause: The rules configuration has changed since the last full import or full synchronization. Impact: New users created will not be synced also any changes made on existing objects i.e. attributes will not be synced to Azure AD.
AIS Monitoring agent has detected DFS Replication service stopped replication on volume #:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. Impact : Replication will be stopped.
AIS Monitoring agent has detected DFS Replication service stopped replication on the folder with the following local path: ###. This server has been disconnected from other partners for ### days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected. Impact : Replication will be stopped.
AIS Monitoring agent has detected the DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. Impact DNS server roles will stop responding.
AIS Monitoring agent has detected that the DNS server could not configure the network connections of this computer with the local computer’s IP address as the preferred DNS server. Impact : Domain controller may not be able to dynamically register DC locator records in DNS. Absence of these records may prevent other Active Directory domain controllers and domain members from locating this domain controller.
AIS Monitoring Platform has discovered that the NetDiag DNS test failed with error [WARNING] The DNS entries for this DC are not registered correctly on DNS server. This can be caused if DNS records are not registered in the DNS server, no other computer or user is able to locate the domain controller.
AIS Monitoring Platform has discovered FSMO role RID Manager issue. When you try to add new users, groups, computers, mailboxes, domain controllers, or other objects to Active Directory on a Microsoft Windows Server 2003-based computer or a Windows 2000-based computer, you may receive the following error message: Cannot create the object because directory service was unable to allocate a relative identifier. This problem occurs When the relative ID (RID) Master is restored from backup, it tries to synchronize with other domain controllers to verify that there are no other RID Masters online. However, the synchronization process fails if there are no domain controllers available to synchronize with, or if replication is not working. The RID pool has been exhausted, or objects in Active Directory that are related to RID allocation use incorrect values or are missing.
AIS Monitoring Platform has discovered that the Domain controller diagnostic Knowledge Consistency Checker (KCC) test failed with multiple errors events. The Knowledge Consistency Checker (KCC) constructs and maintains the Active Directory replication topology automatically. Every 15 minutes, the KCC examines the sum of all directory partition replicas that reside on domain controllers in the forest, as well as administrator-defined settings for connections, sites, and site links.
AIS Monitoring Platform has discovered High CPU usage for process LSASS.exe on domain controller. When your server re-creates or imports objects into the Active Directory the CPU utilization is higher than you expect during the operation. If there are a lot of objects, the CPU utilization may remain at 100 percent for the duration of the operation.
AIS Monitoring Platform has discovered that the LsaPolicy operation failed due to network path. A test related to replication is the NetLogons test. It checks to see that replication is not failing because of insufficient logon privileges.
AIS Monitoring Platform has discovered write timeout problems with NTDS Database. This may be caused due to Anti-virus or the hardware issues. Acrive Directory folders should be excluded from any Anti-virus software. It may encounter strange issues since the anti-virus will prevent or slow down directory operations. High Disk I/O OR the error normally occurs when a physical drive failed in a SCSI RAID array, therefore Active Directory had a difficult time writing to the database.
AIS Monitoring Platform has discovered increase in NTDS DRA Pending Replication Operations. This indicates number of directory synchronizations that are queued for this server that are not yet processed. This counter helps in determining replication backlog. The larger the number, the larger the backlog.
Saaz IntelliScripts has found problem with NTFRS Journal wrap errors, FRS is a multi-threaded, multi-master replication engine that Windows domain controllers use to replicate system policies and logon scripts for Windows clients.
AIS Monitoring Platform has discovered that the Domain Controller Diagnostic test for FSMO check failed with Domain Owner, but is not responding to DS RPC Bind. This indicates RPC issue due to secure channel broken OR DNS name resolution problem.