6201 Plugin DSScheduler reports exception. ERROR.DS.EWS Exception (Active Directory issue)

Description

Getting this event log error usually means the GFI Archiver is unable to communicate with the Journal Mailbox, possibly due to issues with Active Directory.

Event ID 6201: Plugin DSScheduler reports exception. ERROR.DS.EWS Exception.
Additional info: The server is not operational.

Common symptoms may include the following:

• *GFI Archiver is not archiving or working intermittently
• *Emails are not pulled from journal mailbox
• *Unable to login to the Archiver UI (Authentication issue)

We must take a look at the Archiver logs and Event logs to determine the issue. Here are some error in Archiver logs that suggests a communication error with the domain controller. 

2018-01-25,09:31:06,427,1,"#00000DD4","#0000001D","error ","EWSProvider","error:Process The server is not operational.
;Name: 'associatedsteel.com' --> customer's domain

2018-01-25,09:30:53,036,1,"#00000DD4","#00000005","error ","UMPollRem","error:LM::RefreshUserList..cannot retrieve GC root"

2018-01-25,09:30:23,473,1,"#00000dd4","#000010f8","error ","usercntmaad","Call to CountActiveDirectoryUser fails. Returns 0x80004005"

2018-01-25,09:32:36,521,1,"#00000DD4","#0000001E","error ","AdaEngineADDSHost plugin 2","ERROR: ResolveUser: failed while searching for the user[cannot retrieve GC root]"

2018-01-25,09:30:52,973,1,"#00000DD4","#00000005","info ","AdaInformation","ExecuteFilter: Executing with filter [(&(objectClass=User)(mail=*)(mailnickname=*)(!(userAccountControl:1.2.840.113556.1.4.803:=2)))] and properties [mailnickname,objectGuid,msExchHomeServerName,mail]>>"
2018-01-25,09:30:53,036,1,"#00000DD4","#00000005","error ","AdaInformation","Error: ExecuteFilter: failed with [System.ApplicationException: cannot retrieve GC root --->

And a sample error in Event Logs

Event ID:      1030
Level:         Error
Description:
The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful.

Resolution: 

Troubleshooting will start in their AD. Have the customer check the domain controller for any issues.