Skip to main content
Announcements
Qlik Introduces a New Era of Visualization! READ ALL ABOUT IT
cancel
Showing results for 
Search instead for 
Did you mean: 
ikomlyakov1929
Partner - Contributor III
Partner - Contributor III

Qlik Sense Server Error Form Engine (RPCSession, RPC)

I've got the following error while apply filters in my app on server.

Error.JPG

The browser displays the message as a warning, but it's actually an error.

My app consists of extensions and it looks like extensions cause this error.

Does anybody know, what exactly could cause this error?

1 Solution

Accepted Solutions
ErikWetterberg

Hi,

I get something like this too:

Capture.PNG

What you could do is find the RPC ID in the web socket log:

Capture.PNG

In my case it is the GetAppLayout call. The error is 'Request aborted', which the client should handle (and handles) by reissuing the same call (id 4), so everything is OK.

Seems like the client framework looses track of the original call, but there is no real problem, only an annoying error message.

Hope this helps

Erik Wetterberg

View solution in original post

4 Replies
ErikWetterberg

Hi,

I get something like this too:

Capture.PNG

What you could do is find the RPC ID in the web socket log:

Capture.PNG

In my case it is the GetAppLayout call. The error is 'Request aborted', which the client should handle (and handles) by reissuing the same call (id 4), so everything is OK.

Seems like the client framework looses track of the original call, but there is no real problem, only an annoying error message.

Hope this helps

Erik Wetterberg

ikomlyakov1929
Partner - Contributor III
Partner - Contributor III
Author

Hi, Erik

Hope you're right and those errors won't cause any unexpected behavior.

ErikWetterberg

Hi,

'Request aborted' is perfectly normal, but should cause the client to reissue the call. You should be able to find the call causing the error in the log and verify that it is reissued..

Erik

sebastian_serva
Partner - Contributor III
Partner - Contributor III

Eric,

What log would contain that error trace with the ID? And can this be avoided? Why did it occur since the June 2017 upgrade?

Thanks,

Seb