We have a development server which we recently upgraded to 9.0. We have a handful of scheduled reloads on this server, and they are generating Warnings that don't make sense to me. We don't want to upgrade our production server to 9.0 until we get a satisfactory answer to this issue, and I hope the community can help me.
Here is the log entry I'm getting:
Initializing save (0), Copying permissions to new file (0), Saving C:\QvDocs\ServerDocs\IS General\008be9bb-ef76-4137-8e44-047f396d0e1f_Physician Prompt.qvw.tmp (0), Moving temp file to new file (1063), Deleting old file (1063)
Closing the document.
Closed the QlikView Engine successfully. ProcessID=6088
Initializing (0), Finished (219)
The task "QVDocuments/ServerDocs/IS General/Physician Prompt.qvw" finished with warnings. WarningCount=1
I don't see a warning in this. Any ideas?
I occasionally see a similar log message on one of my scheduled reloads. This doesn't appear to cause any issues as the load completes succesfully and the data seems to be consistent.
In our case it doesn't seem to be a memory or processor issue as it occurs on our main Qlikview server, with 4 * Quad core CPU's and over 90 Gb RAM.
It seems to be intermittent, some days everything will run fine, other days we get the warning, however it seems to occur more often on one particular reload than on other reloads.
I've just raised this with support so hopefully they'll be able to shed some light on why it's happening for us.
Warning: Can't set CPU Affinity of "No Cores", ignored!
This is the warning in the log. Took me a bit of clicking to find it, but this seems to be the problem.
Now, in the Enterprise Manager: System tab, QlikView Servers: Performance menu, there's a way to set CPU Affinity. It is defaulting to none checked, for both CPU and Reload Limits. I've changed this to all checked, and some checked, and different ones checked for CPU and Reload, all with the same results.
Does this jog any memories for people out there? As usual, any help would be greatly appreciated.
Warning The QlikView Engine working with document "document.qvw" is not responding.
Theese warnings are counted on end of log.
If QVB in not responded too long in some manier to server it will be killed.