Jump to content

Miami

Members
  • Content Count

    30
  • Joined

  • Last visited

Profile Information

  • Location
    European Union
  1. Our tempDB was configured with a size limit and It looks like the last module update was the reason why tempDB has grown to it's maximum size. Everything is working fine after size limit of tempDB was increased.
  2. Looks like issue was in the tempDB configuration within MSSQL.
  3. Has anyone experienced issues after last ESMC module updates? When update was finished, I was asked to reload the console. After doing that, error messages appeared in every "window" or dashboard. One hour later, ESMC console is just loading and loading. Any suggestions? Is there something still running in the background? Version details: ESET Security Management Center (Server), Version 7.2 (7.2.1266.0) ESET Security Management Center (Web Console), Version 7.2 (7.2.221.0) Update module1021 (20200218) Translation support module1805 (20200619) SysInspector module1278 (20200609) SSL module1048 (20200608) Push Notification Service module1064 (20200625) Configuration module1822.4 (20200505)
  4. This is a problem of DB design and it should be solved. It is also not possible to combine reports like in V5. @ Failed / Trace message - some trace messages like "Task failed in the security product" are not telling us why this task failed. You should take more closer look on this. I will add also something: Description: LOG deletion uppon Computer deletion Detail: When I delete computer from ERA console, all coresponding logs in "Threats" are deleted too. This is a "no way" for security product.
×
×
  • Create New...