Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Everyone
All of a sudden none of my Qlikview documents that use an OLEDB connector will reload anymore from QVS. In the log file, I get the following error:
QVX_PIPE_ERROR:
20/01/2014 10:49:19: Error: OLEDB read failed
I am not using QVX at all I just use the OLE DB connection string (which I have re-created and still get the same error). The reloads work perfectly fine when I do them on my laptop but when I try to run them on the server (either using reloads on QMS or using the client I have installed on the server) they just stop with the error message above.
Any ideas?
For what it's worth the system info (Qlikview server) is below:
ReloadEngine@virapps1 at http://virapps1:4720/QDS/Service | |||
Product Information | |||
Product name | QlikView Distribution Service x64 | ||
Client Build Number | 11.0.11154.0 | ||
Target Platform | x64 | ||
Machine Information | |||
Computer Name | VIRAPPS1 | ||
Operating System Version | Win32_OperatingSystem=@ X64 (Microsoft Windows NT 6.0.6002 Service Pack 2) | ||
.NET Version | 4.0.30319.1008 | ||
Physical Memory | 12286Mb | ||
Available Memory | 7512Mb | ||
CPU Information | |||
CPU 0 | Intel(R) Xeon(R) CPU X5550 @ 2.67GHz | ||
CPU 1 | Intel(R) Xeon(R) CPU X5550 @ 2.67GHz | ||
CPU 2 | Intel(R) Xeon(R) CPU X5550 @ 2.67GHz | ||
CPU 3 | Intel(R) Xeon(R) CPU X5550 @ 2.67GHz |
Hi Michael
I can't seem to be able to view that thread I'm afraid - I get an "Unauthorized" message saying the content is restricted.
Thanks
Stu
Sorry, it is in a group.
In essence, I had the same problem. It's gone now. The changes I've made:
- Upgraded QV Server to 11.20 SR2
- Increased number of tries for each production task from 1 (default) to 2. It is on the "Triggers" tab.
Besides, there was a recommendation to use CONNECT statement before every new SQL SELECT, and DISCONNECT statement before every new CONNECT, but I didn't have to do it.
Regards,
Michael
Michael,
This problem occures on my system occasionally (I am running v. 11.2 SR2 and I have modified the Attempts count to 2). Looks like this issue was resolved in v.11.0 SR3 (bugID 62361), but I could not find any references about similar issue resolved in v. 11.2.
It seems to be a resource allocation issue (occurs on DEV server with less RAM and never occurs on PROD server), so I hope it is resolved in one of recent 11.2 updates.
Did not try the CONNECT/DISCONNECT combination yet, but it might be a solution for me.
Thanks for the reference.
Regards,
Vladimir
The issue is most likely systems resources. Check the QVS.exe process to see if it consumes a large amout of the CPU or Memory. A Qlikview server service restart may help, but a actual Windows Server restart should fix it for a week or so depending on your qvd reload size.
This link below may be helpful as well.
http://www.qlikisrael-support.com/Knowledgebase/Article/GetAttachment/142/2093344