Если отсутствуют результаты поиска, сперва проверьте, можете ли вы найти сообщения из аккаунта администратора (суперюзера) Архива. Если сообщения нашлись, попробуйте следующие шаги для решения проблемы авторизации через Active Directory или LDAP:
- Для администратора - Результаты поиска не находятся из учетной записи администратора.
- Для пользователей, авторизованных через Active Directory - Администатор находит результаты поиска, но остальные пользователи, авторизованные через Active Directory, не могут их найти.
- Для пользователей, авторизованных через LDAP - Администатор находит результаты поиска, но остальные пользователи, авторизованные через LDAP, не могут их найти.
Учетная запись администратора
Нет доступных томов со статусом АКТИВЕН (active) или ЗАКРЫТ (closed)
Симптом ошибки: Во вкладке Настройка -> Тома должен быть доступен хотя бы один том со статусом АКТИВЕН (active) или ЗАКРЫТ (closed).
Решение: Создайте новый том со статусом UNUSED (неиспользуемый том) в Настройка -> Тома.
Searching Using Wrong Date Criteria Поиск с использованием
Symptom: Emails in the archive are older than three months (the default search time period)
Resolution: Switch the date to "archive date" in Search Options and reattempt the search.
Insufficient Privileges to Read/Write Volume Store/Index
Symptom: Volumes listed in Configuration->Volumes shows a UNMOUNTED. Архива may be running under an account with insufficient privileges to read/write from the directory.
Resolution: Edit the Архива Service in the Windows Services Control Panel applet. Specify a logon account that has rights to read/write to the remote drive. To test access rights: logout of the workstation, and login using the logon account specified, attempt to copy a dummy file to the index and store paths. After the login account has changed, the Архива server must be restarted for the changes to take effect.
Corrupted Volume Indexes
Symptom: In Status->Volumes, confirm that that the doc counts associated with each of the active/closed volumes are greater than zero.
Resolution: If any volume has a doc count of zero, reindex the affected volume/s in Configuration->Volumes.
Corrupted Audit Indexes
Symptom: In Status->Alerts or the Архива debug.log file, errors are appearing indicating that the audit index is corrupted or could not be started. If the audit index is corrupted, it may severely affect the normal operation of the server.
Resolution: From the filesystem, delete the contents of the Audit Log index directory:
Thereafter, start the server and reindex your audit logs in Configuration->Logs
Пользователи, авторизованные через Active Directory
Local Domains Not Specified Correctly
Symptom: Local domains incorrectly specified in Configuration->Domains
Resolution: Check spelling & add all local domains (for example, mailarchiva.com and stimulussoft.com) in Configuration->Domains
Incorrect Email Attribute
Symptom: For MS Exchange users, the email attribute in Configuration->Logins is not set to "proxyAddresses". This is the LDAP attribute used to obtain user email addresses for filtering purposes.
Resolution: if using MS Exchange, edit the email attribute field in Configuration->Logins to be "proxyAddresses".
Incorrect Email Value
Symptom: For MS Exchange users, the email attribute value in Configuration->Logins must be set to "SMTP:(.*)". Архива use this regular expression to parse the value of the email attribute field (specified above). In the default "SMTP:(.*)", Архива will extract the email address from an email value field of (SMTP:test@mailarchiva.com).
Resolution: Edit the email value field in Configuration->Logins to be SMTP:(.*)"
Admin Role View Filter
Symptom: You have the expectation that AD users assigned the Admin Role will be able to see everyone's emails. This is not the case. By default, only users assigned the Auditor Role, can see everyone's emails.
Resolution: In Configuration->Logins, assign the user the Auditor role, or in Configuration->Roles, remove the contents of the user role's View Filter.
User Role Filter Not Defined Correctly
Symptom: In Configuration->Roles, the User Role View Filter does not have the value "%email%". This macro is needed to filter out emails belonging to the logged in user. Архива subtitutes "%email%" with the logged in user's email addresses for search results filtering purposes.
Resolution: Edit the User Role filter in Configuration->Roles to be "%email%".
Пользователи, авторизованные через LDAP
Local Domains Not Specified Correctly
Symptom: Local domains incorrectly specified in Configuration->Domains
Resolution: Check spelling & add all local domains (for example, mailarchiva.com and stimulussoft.com) in Configuration->Domains
Incorrect Email Attribute
Symptom: The email attribute in Configuration->Logins is incorrect. This is the LDAP attribute used to obtain user email addresses for filtering purposes. The require email attribute value is dependent on the specifiic mail server used. It is often "mail" or "email".
Resolution: Edit the email attribute field in Configuration->Logins to be the name of the LDAP attribute where user email addresses are stored.
Incorrect Email Value
Symptom: For on MS Exchange users, the email attribute value in Configuration->Logins is set to something other than "(.*)".
Resolution: Edit the email value field in Configuration->Logins to be "(.*)"
Admin Role View Filter
Symptom: You have the expectation that AD users assigned the Admin Role will be able to see everyone's emails. This is not the case. By default, only users assigned the Auditor Role, can see everyone's emails.
Resolution: In Configuration->Logins, assign the user the Auditor role, or in Configuration->Roles, remove the contents of the user role's View Filter.
User Role Filter Not Defined Correctly
Symptom: In Configuration->Roles, the user role filter does not have the value "%email%". This macro is needed to filter out emails belonging to the logged in user. Архива subtitutes "%email%" with the logged in user's email addresses for search results filtering purposes.
Resolution: Edit the User Role filter in Configuration->Roles to be "%email%".
None of the Above
Enable troubleshoot logging in Configuration->Logs. Perform a search. Send your debug.log file compressed to Архива support.