Error StdServer: void CStdServer::DoMsgReceived

Error StdServer: void CStdServer::DoMsgReceived is being logged in the QlikView Event log files and Windows Event log file.

• What is the message mean?
• What is the cause to log the message?

In the QlikView Event Log

Error StdServer: void CStdServer::DoMsgReceived (CQvMsgActiveProtocol*, CConstQvMsg): pContext->AuthenticatedUser.IsEmpty () && ServerSettings::AuthenticationLevel == 2, will throw EQ_LOCERR_FILE_CORRUPT

In the Windows Event Log

- System
  - Provider
   [ Name]  QlikViewServer
  - EventID 300
   [ Qualifiers]  0
   Level 2
   Task 0
   Keywords 0x80000000000000
  - TimeCreated
   [ SystemTime]  2017-10-25T08:26:59.000000000Z
   EventRecordID 279734541
   Channel Application
   Computer
   Security
- EventData
   StdServer: void CStdServer::DoMsgReceived (CQvMsgActiveProtocol*, CConstQvMsg): pContext->AuthenticatedUser.IsEmpty () && ServerSettings::AuthenticationLevel == 2, will throw EQ_LOCERR_FILE_CORRUPT
 

The first question to ask would be: Are users seeing issues accessing the system? 
The particular user with the issue would then need to be investigated, as this error indicates an authentication error or security violation, leading the QlikView Server to deny the current session and to throw an exception.

! QlikView does not carry out authentication and the error is being returned by the Windows System. 

A review of the Windows Event Security log or System log at around the same time of the issue can help identify Microsoft Active Directory or Windows related authentication issues. Look for logon failures or other security alerts that terminate existing sessions. 
 
Some common causes of the issue: 

• The QlikView Server is set to allow only authenticated named users to log in but cannot retrieve authenticated user names from Windows (Service account may not have permissions to do so)
• System authentication processes are failing or users cannot authenticate against the Windows Active Directory (Review Windows Event logs and Active Directory logs)

It is important to understand that the root cause of the issue is with the system carrying out authentication and therefore the Windows server or Active Directory log files need to be reviewed. Assistance from the local network and security administrator may be necessary.