Решение: пересоздать профиль Outlook (оказалось самое быстрое!).
Я просто переименовал папку C:\Users\Username\AppData\Local\Microsoft\Outlook) и заново добавил IMAP аккаунт. Также пришлось экспортировать локальные контакты в csv файл при помощи стандартного диалога Файл - Открыть/Экспорт.
Судя по всему, это было некоторое повреждение pst файла. Зацепок/кодов ошибок/исключений нет, но т.к. пересоздание профиля помогло - скорее всего, причина в нём(вероятно поэтому нет и ошибок/таймаутов).
Пробовал (не помогло):
* Выключать фаервол (встроенный в Windows и Norton Security)
* Выключать антивирусы (Windows Defender/Norton Security)
* Перезагружать почтовый сервер(Zimbra)
* Переподписываться на подписанные папки
* Включать в разделе Параметры - Дополнительно - приём только заголовков
* Включать режим отладки и смотреть debug логи Outlook (там нет полезной информации)
* Смотреть логи на почтовом сервере Zimbra (mailbox.log)
Потратил прилично времени на это, решил поделиться.
Wednesday, December 13, 2017
Wednesday, November 15, 2017
[SOLVED]: error 1355 - Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355
A Good Time Server could not be located.
It turned out that actually there were no problems with the time server in my case.
All these messages were misleading!! It cost me a whole day! So I hope this solution will be helpful for other people.
The actual reasons were:
1. Unavailable SYSVOL share
2. Unavailable NETLOGON share
How to restore it?
1. To recreate SYSVOL
net stop ntfrs
REG ADD "HKLM\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup" /v BurFlags /t REG_DWORD /d 212 /f
net start ntfrs
Origin https://support.microsoft.com/en-us/help/316790/the-sysvol-and-netlogon-shares-are-missing-after-you-restore-a-domain
2. To recreate NETLOGON - just type in these two commands:
net stop netlogon
net start netlogon
3. Test it:
dsquery server
netdom query fsmo
dcdiag /test:fsmocheck
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355
A Good Time Server could not be located.
It turned out that actually there were no problems with the time server in my case.
All these messages were misleading!! It cost me a whole day! So I hope this solution will be helpful for other people.
The actual reasons were:
1. Unavailable SYSVOL share
2. Unavailable NETLOGON share
How to restore it?
1. To recreate SYSVOL
net stop ntfrs
REG ADD "HKLM\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup" /v BurFlags /t REG_DWORD /d 212 /f
net start ntfrs
Origin https://support.microsoft.com/en-us/help/316790/the-sysvol-and-netlogon-shares-are-missing-after-you-restore-a-domain
2. To recreate NETLOGON - just type in these two commands:
net stop netlogon
net start netlogon
3. Test it:
dsquery server
netdom query fsmo
dcdiag /test:fsmocheck
Wednesday, August 9, 2017
SOLVED: "TLS init def ctx failed" -1 (Ubuntu)
# Disable AppArmor temporarily! - this helped me!
/etc/init.d/apparmor teardown
# Assuming you've already set appropriate rights on the file TLSCertificateKeyFile and others as mentioned http://blog.rot13.org/2016/01/debian-openldap-with-gnutls-and-openssl-certificates.html
# Start OpenLDAP again
service slapd start
/etc/init.d/apparmor teardown
# Assuming you've already set appropriate rights on the file TLSCertificateKeyFile and others as mentioned http://blog.rot13.org/2016/01/debian-openldap-with-gnutls-and-openssl-certificates.html
# Start OpenLDAP again
service slapd start
# Or debug it with (for those who prefer storing config in the plain text file, rather than in LDAP)
/usr/sbin/slapd -g openldap -u openldap -f /etc/ldap/slapd.conf -d -1
Subscribe to:
Posts (Atom)