SE_LOG: CQvXmlInterfaceRequestHandler - Catch: errId(36). Ino(-1). Fno(90)

[AliAzizi]

Hi guys

Using QV 11.2 SR11 on a Win 2012 server and get the following error message:

SE_LOG: CQvXmlInterfaceRequestHandler - Catch: errId(36). Ino(-1). Fno(90)

in the Event log. Any idea about what it means?

regards and thank you for helping

[Bill_Britt]

HI,

This could be cause by the QMC trying to get the Admin Doc List (GetAdminDocList) from the QVS.

Bill

[AliAzizi]

Hi Bill

We have a clustered environment consisting of two QV frontend servers (with QVS) and a backend server with QMC. Every time the server vendor (who is hosting the servers) patches the servers with Microsoft windows updated in a closing window, we are experiencing that all QV servers are rebooted and all QV services on all three servers are running, but the whole system is not working:

1- Accesspoints are not available (error message: No server)

2- scheduled tasks are not running (error message: SE_LOG: CQvXmlInterfaceRequestHandler - Catch: errId(36). Ino(-1). Fno(90))

In QMC we see the "Off duty" message for QVS servers in the Services tab.

It seems that all servers and services are running, but servers are not communicating to each other or cannot find each other!

We are running: Windows 2012 R2 and QlikView 11.2 SR11

[Anonymous]

aliazizi

We are observing this error two under similar circumstances.

Our Windows SAs perform a routine reboot of the servers at weekend and these messages appear after that.

Fortunately, we have scheduled task to restart all QlikView services in time for the start of the working week. This seems to clear the problem. Perhaps you could try a restart of all QlikView services sometime after the server rebooting is all clear and validated.

We will continue to research the underlying cause and how to configure a clean server reboot that leaves QlikView functioning.

[AliAzizi]

Hi Paul

Thank you for your reply. We have changed the configuration of the QV services: Startup type is changed to "Automatic (Delayed Start)" and it's working properly now. Maybe you should try it.

We did it based on a tip from QlikTech support.