Information: Memory Allocation Delta for this file=1682.58 Mb. Available Physical Memory Before Reload=6783.28 Mb. Available Physical Memory After Reload=5097.39 Mb. Total Physical
Memory=5097.39 Mb.(2015-05-20 14:13:32) Information: The Source Document was reloaded successfully.(2015-05-20 14:13:32) Information: Reload finished successfully(2015-05-20 14:13:32)
Error: Exception in save source file: Could not find file 'C:\QLIK\3 LOAD\a42ad856-54bf-4849-8022-e6f3208a700b_xxxxxxx.qvw.tmp'.(2015-05-20 14:13:36)
Error: File is not ok. Target file was not saved.(2015-05-20 14:13:36) Information: Found 1 messages from QlikView. Following below:(2015-05-20 14:13:36)
Information: Disk full while accessing C:\QLIK\3 LOAD\a42ad856-54bf-4849-8022-e6f3208a700b_xxxxxxxxx.qvw.tmp.(2015-05-20 14:13:36) Information: Closing the document.(2015-
05-20 14:13:37) Information: Closed the QlikView Engine successfully. ProcessID=3788(2015-05-20 14:13:37) Error: The task "Load/xxxxxxxx.qvw" failed. Exception: ||
No you're right, it isn't memory. But the QMC doesn't think it is either. The log says that the C:-drive of the server is causing trouble.
Normally if you drop a new document in a directory on the QlikView server, the document will inherit the permissions from the directory. It those permissions do not grant the service account any write access, the reload engine will gladly reload the document in memory and try to save the result to disk in a temporary file. At that moment, something goes wrong.
If you have access to the server (or the folder where the server picks up your document), check whether the document lists the service account in File Properties->Security.
If you are working over a Windows share, the share must provide R/W-access on its own.
