Qlik Community

QlikView Deployment

Discussion Board for collaboration related to QlikView Deployment.

lfholland
New Contributor III

Failed to send response: The I/O operation has been aborted because of either a thread exit or an application request

Almost every morning, my users try to get into Qlikview, the access point comes up and it says: "Message: no server".  We restart the server and it works again.  On the mornings it breaks, I seem to see these two errors in the event viewer:

both have the source of QvWebServer:

Failed to send response: The specified network name is no longer available

Failed to send response: The I/O operation has been aborted because of either a thread exit or an application request

The version of QV we have is 12.20.20500.0 and I've googled these messages to no avail.

And please be patient with me, I am new to this server stuff... Thank you in advance.

1 Solution

Accepted Solutions
lfholland
New Contributor III

Re: Failed to send response: The I/O operation has been aborted because of either a thread exit or an application request

Incase anyone has this issue, we had just upgraded not only our software, but also our server.  The old production server was still running but not available to anyone.  I don't know why we didn't have this issue from the very beginning of using the upgraded server (issue didn't start until a couple weeks after) but once we shut down the original production server, the issue stopped occurring...

View solution in original post

1 Reply
lfholland
New Contributor III

Re: Failed to send response: The I/O operation has been aborted because of either a thread exit or an application request

Incase anyone has this issue, we had just upgraded not only our software, but also our server.  The old production server was still running but not available to anyone.  I don't know why we didn't have this issue from the very beginning of using the upgraded server (issue didn't start until a couple weeks after) but once we shut down the original production server, the issue stopped occurring...

View solution in original post