Qlik Community

QlikView Deployment

Discussion Board for collaboration related to QlikView Deployment.

rospigliosi
Contributor

There is a TicketData.pgo file that can get corrupted

Hello,

i'm on QlikView 11.2 SR12, sometimes I get a "NO CONNECTION" error, and on server log I found:

SE_LOG: SERVER - DMR: Validate and Apply Hex. UsrName()


Searching on the community it seems that there is a TicketData.pgo file that can get corrupted causing this intermittend error.


Is this bug has been solved in a specifice service release? Is this problem has been solved on version 12?


Thanks


Camillo


Labels (1)
1 Solution

Accepted Solutions
Emmanuelle-Bustos
Valued Contributor

Re: There is a TicketData.pgo file that can get corrupted

Hi

this is from Qliktech:

Description

This is a QlikView Server (QVS) error message, indicating that an error occurred during authentication process.

This error message can occur when using IIS_AUTHENTICATION with invalid user information, such as user name and ticket info etc.

Resolution

The issue can only be resolved by enabling proper authentication.

Common causes of the issue are:
  • User’s name is invalid
  • User’s ticket is invalid
  • User’s remote IP does not match
  • User issue related to NT/AD group security policy
Try to identify the root reason of the authentication failure.

Log entries following the error message can help in guiding the troubleshooting to the root cause.
1 Reply
Emmanuelle-Bustos
Valued Contributor

Re: There is a TicketData.pgo file that can get corrupted

Hi

this is from Qliktech:

Description

This is a QlikView Server (QVS) error message, indicating that an error occurred during authentication process.

This error message can occur when using IIS_AUTHENTICATION with invalid user information, such as user name and ticket info etc.

Resolution

The issue can only be resolved by enabling proper authentication.

Common causes of the issue are:
  • User’s name is invalid
  • User’s ticket is invalid
  • User’s remote IP does not match
  • User issue related to NT/AD group security policy
Try to identify the root reason of the authentication failure.

Log entries following the error message can help in guiding the troubleshooting to the root cause.