Skip to main content
Announcements
July 15, NEW Customer Portal: Initial launch will improve how you submit Support Cases. IMPORTANT DETAILS
cancel
Showing results for 
Search instead for 
Did you mean: 
daniel_dalnekoff
Contributor III
Contributor III

Access denied for service account

Hi,

I've noticed recently that our service account (that runs all of the Qlik services) has been showing up constantly in the logs with this error:  "Access was denied for User: <service account> with AccessID <...>; SessionID <...>, SessionCount:5, Hostname...OperationType:'UsageDenied'.

I understand the limitation on 5 sessions/user, but in this case this is our service account - not an actual user in the application.  Is there something going on when we have multiple reload tasks running (or something similar)?  Does anyone have any insight into what is going on here?

1 Solution

Accepted Solutions
Levi_Turner
Employee
Employee

Hey Dan,

Does this thread clarify some things: Re: Qlik Sense Windows authentication redirect port changed June 2018 ? Basically it is caused by the Monitoring Apps.

It can be ignored. Or, like the person in the other thread, you can also switch the monitoring apps' data connections to make direct QRS API calls (reference https://qliksupport.force.com/articles/000048247 for guidance there).

Hope that helps.

View solution in original post

5 Replies
arvind_patil
Partner - Specialist III
Partner - Specialist III

Hi Dan,

It may because of internet speed . Sometimes we are also facing same issue .

Thanks,

Arvind Patil

balabhaskarqlik

May be restart the proxy services, seems to work.

OR

From AD reset all the Passwords of the USERS and Configure with new passwords. Restart all the QLIK Services. Now you may got the access for all Users and test it through all the browsers.

Levi_Turner
Employee
Employee

Hey Dan,

Does this thread clarify some things: Re: Qlik Sense Windows authentication redirect port changed June 2018 ? Basically it is caused by the Monitoring Apps.

It can be ignored. Or, like the person in the other thread, you can also switch the monitoring apps' data connections to make direct QRS API calls (reference https://qliksupport.force.com/articles/000048247 for guidance there).

Hope that helps.

pwagner
Partner - Creator III
Partner - Creator III

Hello @Levi_Turner 

I am facing the same issue like @daniel_dalnekoff  at the moment.

Can the error be ignored? Or do have another solution (except changing to direct QRS API calls)?

 

Thank you.

Best regards, Patrick

Levi_Turner
Employee
Employee

I've not seen any other options in the intervening years, so it's still ignore or switch the apps to not going over the Qlik Proxy Service.