Qlik Community

QlikView Management

Discussion Board for collaboration on QlikView Management.

mountaindude
Contributor III

No connection error in Access Point when opening document

During past month or so, pretty much since upgrading to 11.2 SR1, we get sporadic "No Connection" error dialogs when trying to open documents (AJAX client) from the access point.

This is a two server setup, one load server (directory service, distribution service, management service) and one access point (QV server, QV web server). The Windows event log on the access point server shows two entries for the QV web server when someone tries to access a document (and get the error dialog), both with the same time stamp and contents:

Failed to get client: Object reference not set to an instance of an object.

Or it's XML representation:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

  <Provider Name="QvWebServer" />

  <EventID Qualifiers="0">0</EventID>

  <Level>3</Level>

  <Task>0</Task>

  <Keywords>0x80000000000000</Keywords>

  <TimeCreated SystemTime="2013-05-13T12:34:26.000Z" />

  <EventRecordID>1048507</EventRecordID>

  <Channel>Application</Channel>

  <Computer>xxxxx-servername-xxxxxx</Computer>

  <Security />

  </System>

- <EventData>

  <Data>Failed to get client: Object reference not set to an instance of an object.</Data>

  </EventData>

  </Event>

Plenty of RAM in both servers, but most of it is used all the time on the access point.

What could be causing this?

Low RAM?

Bugs in QV web server?

Something else?

2 Replies
Employee
Employee

Re: No connection error in Access Point when opening document

Have you checked the QVS event log and the QV webserver logs to see what they might show?

Bill

mountaindude
Contributor III

Re: No connection error in Access Point when opening document

Yes, I did check those logs, and it seems memory is kind of low, but not

all gone. However seems that those services eat lots of memory even with no

users on and preloading turned off... Something is fishy there.

This might be the reason needed to prioritize that move from qvws to IIS..

Community Browser