Jump to content

Kirill Tsapovsky

Members
  • Posts

    7
  • Joined

  • Last visited

    Never
  1. Добрый день. По итогам исследования проблемы разработчиком сбой вызван ошибкой драйвера YandexDisk3ShellExt-1511.dll. Похоже, что он имеет проблемы совместимости с диалоговыми окнами Проводника, которые использует консоль KSC. Для решения проблемы необходимо выяснить причину возникновения ошибки shell extension Яндекс.Диска при открытии диалоговых окон Проводника, либо отключить его. Спасибо.
  2. Hello. Developers have built a private fix to address this issue: pf5364. Please create an incident in CompanyAccount in order to obtain it, specifying a link to this thread and requesting the patch. Unfortunately, we are restricted from uploading it to the forum directly. Thank you.
  3. I have come across a similar case, where the same error occured after upgrading KSC from 10.5 to 11, due to specifics of that version. RnD suggested installing patch B on all the servers, after which the error was fixed and the hierarchy worked. Do the servers in question have patch B installed? https://support.kaspersky.com/15293 Please let us know the result. Thank you.
  4. Доброго времени суток. Я так понимаю официального решения от Касперского нет ? И разъяснения причин и как решить нет :( Кто то может писал в тех поддержку ? Я написал, жду ответа уже неделю. Добрый день. Пожалуйста, сообщите номер созданного инцидента; в этом случае мы сможем подробнее узнать о его состоянии. Спасибо!
  5. Hello. Was the master server the only one reinstalled, or the entire infrastructure? I.e. are the slave servers working properly on their own? Can they be directly connected to? Error 0x4E5 is typical for trusted connection issues. Were the slave servers re-added after the old master server was taken down? In which order were the actions made between the former and current state? Thank you.
  6. Hello. The attached GSI lists a number of Fortinet drivers as potentially incompatible software present on the host. While it has not been confirmed as incompatible by RnD, there are known occuring issues between Fortinet and KES. According to existing investigated cases, such issues are resolved by installing pf7501 or a corresponding newer private fix for KES 11.1.1. Please install the private fix on affected hosts and provide feedback if possible. The fix can be obtained via CompanyAccount, mentioned earlier. Thank you.
×
×
  • Create New...