Jump to content

Error "Login Failed, Connection has failed with the state of 'Not connected'


mayowa
 Share

Recommended Posts

Just now, mayowa said:

Dear All,

A client called to inform us that he couldn't access ESMC console ,after troubleshooting we were faced with this pop error 

Leadway_log_2.zipUnavailable

 

For your perusal please kindly find attached document 

Regards Leadway_log_2.zip

image.png

 

Leadway_log_2.zip

Link to comment
Share on other sites

  • ESET Staff

In ESMC's log one can found:

2020-01-13 14:24:35 Error: Service [Thread 35c0]: [Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space for object 'dbo.tbl_logbackup_prevlogs'.'PK__tbl_logb__3213E83FAA0C3AA4' in database 'era_db' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

which is considered as fatal error during startup. It indicates that either database got really corrupted, or more probably that there is no space on disk where database is located. Could you please verify it?

Error on screenshot indicates there might be problem also with local system service account - if something in system went wrong, it might happen that database is not able to write data because of missing permissions instead of insufficient space ...

EDIT: seems that upgrade of database is failing and it is very space consuming -> during upgrade almost all data is duplicated, which means that there must be enough free space on disk where whole database will fit.

Edited by MartinK
Link to comment
Share on other sites

16 hours ago, MartinK said:

In ESMC's log one can found:


2020-01-13 14:24:35 Error: Service [Thread 35c0]: [Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space for object 'dbo.tbl_logbackup_prevlogs'.'PK__tbl_logb__3213E83FAA0C3AA4' in database 'era_db' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

which is considered as fatal error during startup. It indicates that either database got really corrupted, or more probably that there is no space on disk where database is located. Could you please verify it?

Error on screenshot indicates there might be problem also with local system service account - if something in system went wrong, it might happen that database is not able to write data because of missing permissions instead of insufficient space ...

EDIT: seems that upgrade of database is failing and it is very space consuming -> during upgrade almost all data is duplicated, which means that there must be enough free space on disk where whole database will fit.

Thank you for your response 

Quick one is there anywhere/how we can retrieve Peer certificates (Agent,proxy,server,or CA) from the ESMC server without accessing the ESMC web-console 

Regards  

Link to comment
Share on other sites

  • ESET Staff
7 hours ago, mayowa said:

Thank you for your response 

Quick one is there anywhere/how we can retrieve Peer certificates (Agent,proxy,server,or CA) from the ESMC server without accessing the ESMC web-console 

Regards  

It is not documented but I would recommend to check tables tbl_certification_authorities and tbl_certificates.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...