This article describes the error and its resolution when MailArchiver fails to query Active Directory.
The issue is observed in larger environments only. GFI Archiver services start and GFI Archiver runs smoothly for some hours/days.
However, at some point, users cannot log into the web page anymore. They are presented with a login screen, but even when entering the correct username and password, the login fails. Restarting the GFI Archiver Core service resolves the issue for a while.
The error is logged in one of the following debug log files beginning at the same time when the issue starts:
2012-11-17,20:05:31,129,1,"#000015B0","#0000000D","warning","DirectoryEngineAD","Warning: GetDomainsList: The server is not operational.
- GFI Archiver 2013, 2012, 2011
- Active Directory
GFI Archiver cannot successfully connect to the Active Directory domain.
Note: This procedure requires to edit files manually. If edited incorrectly it can leave the server in a non-operational state. Please keep backups of any file which is edited throughout this article before saving any changes to them.
This solution is only available in GFI Archiver 2013 R2 build 20131111 or newer. Ensure that this or a newer build is installed before applying this solution:
- Stop the GFI Archiver services.
- Open the folder ..\InstallationFolder\Core\Data
- Open the following file in Notepad: product.config
- Add the following line after the line that reads
<add key="DomainCacheTTL" value="-1" />
- Save the file.
- Start the GFI Archiver services.
- The error can also be due to network issues itself. Please ensure that there are no Active Directory or network issues which cause this and refer to: Error: 'The Server Is Not Operational' and Server Not Operational Error. If there are no AD/network issues causing this, escalate with a set of TS files showing the above error.
- When upgrading to a newer version of GFI Archiver, installation files mentioned in this procedure will be overwritten with default versions making the changes void and ineffective. It is therefore suggested to keep a record of this procedure and follow it once again directly after upgrading to keep this functionality intact.