9-5-2011 13:31:03.2272633 Information Physical FileSize=1.06 Mb. Memory Allocation Delta for this file=12.36 Mb. Available Physical Memory Before Open=2445.41 Mb. Available Physical Memory After Open=2433.88 Mb. Total Physical Memory=3839.55 Mb.
9-5-2011 13:31:03.2272633 Information The document was loaded successfully.
9-5-2011 13:31:03.2272633 Information Document was opened successfully
9-5-2011 13:31:03.2272633 Information Opened successfully (0)
9-5-2011 13:31:03.2272633 Information Starting reload
9-5-2011 13:31:03.2428886 Information QlikView->Settings->Document Peferences->Generate Logfile in document is not set.
9-5-2011 13:31:03.2585139 Information The Source Document is being reloaded. DocumentPath=D:\QlikView\QvPortal\Docman rappellijst v1 0.qvw
9-5-2011 13:31:03.2585139 Information The Source Document reload complete. DocumentPath=D:\QlikView\QvPortal\Docman rappellijst v1 0.qvw
9-5-2011 13:31:03.2741392 Information Memory Allocation Delta for this file=0.48 Mb. Available Physical Memory Before Reload=2433.87 Mb. Available Physical Memory After Reload=2434.26 Mb. Total Physical Memory=2434.26 Mb.
9-5-2011 13:31:03.4303922 Error The Source Document was NOT reloaded successfully. DocumentPath=D:\QlikView\QvPortal\Docman rappellijst v1 0.qvw.
9-5-2011 13:31:03.4303922 Information Initializing Reload (0), Finished (203)
9-5-2011 13:31:03.4303922 Error Reload failed.
9-5-2011 13:31:03.4616428 Information Closing the document.
9-5-2011 13:31:03.6178958 Information Closed the QlikView Engine successfully. ProcessID=1088
9-5-2011 13:31:03.6178958 Information Initializing (0), Finished (187)
Since it says"The Source Document reload complete" and after that it says "Error The Source Document was NOT reloaded successfully" I don't know what the problem is. The document makes connection to an Oracle database with ODBC.
Re: Reload document fails while scheduled, manual is successful
The Qlikview Server and Qlikview developer are 32 or 64 bits? Client Oracle?
All programs need have some version.
Yes, both are 64 bits.
I am sure the problem is caused by the way I created the odbc connection. Since it is a user dsn the service account does not have privilege on the created user dsn. I asked the server administrator to create a system dsn for me.