Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi everyone,
I have an issue with Timout and I don't know what exactly the problem is...
When running on test server, the QVW works just fine and takes less than 5 minutes to reload.
While running on production (I have no publisher license), it is running forever (more than 3 hours) and fails at last, with the following log:
The execution had started at :09:00:00.
6/24/2013 14:13:40.3214661 | Information | Reloading......... |
6/24/2013 14:28:40.3560261 | Information | Reloading.......... |
6/24/2013 14:43:40.3905861 | Information | Slowing down logging. LoggingSeconds=1200 |
6/24/2013 14:43:40.3905861 | Information | Reloading |
6/24/2013 15:00:01.4438821 | Error | Aborting Reload. Error=QDSMain.TaskResult |
6/24/2013 15:00:11.7411525 | Warning | The QlikView Engine is Reloading, it will be killed (Please ignore logged warnings/errors about the kill). |
6/24/2013 15:00:11.7411525 | Information | Killing the QlikView Engine. ProcessID=5084 |
6/24/2013 15:00:11.8661573 | Information | Closed the QlikView Engine successfully. ProcessID=5084 |
6/24/2013 15:00:11.8661573 | Information | Initializing Reload (0), Initializing (21603500), Finished (21603656) |
6/24/2013 15:00:11.8817829 | Error | Task aborted. |
6/24/2013 15:00:11.9442853 | Error | The task "XXXX_Dashboard.qvw" failed. ErrorCount=3 |
6/24/2013 15:00:11.9599109 | Error | Exception=System.ObjectDisposedException: Safe handle has been closed |
at System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext)
at QVBWrapper.Document.ReadDocumentLogThread(ILogBucket i_LogBucket, DateTime i_ReloadStartTime)
6/24/2013 15:00:12.0692901 | Information | Reload was aborted. |
All posts I am reading are talking about an issue with OLE DB connection, but in this case, The loading process becomes heavy only after all server data was loaded.
What I mean is, the problem seems to happen on within the QlikView application, and not related to data connectivity.
Does anyone has an idea??/
Thanks, Ido.
We're having a similar issue.
While our reloads are timing out for different reasons (yet to be determined), the reason that Qlikview is killing the reload is due to the "Timeout seconds" in the Documents -> QVS@... -> Reload -> Reload Schedule page in the Management Console.
In lieu of understanding why Qlikview is taking so long, you could try increasing the timeout.
Adam
Hi, look at the below updated error codes.
0 No error
1 General error
2 Syntax error
3 General ODBC error
4 General OLE DB error
5 General custom database error
6 General XML error
7 General HTML error
8 File not found
9 Database not found
10 Table not found
11 Field not found
12 File has wrong format
13 BIFF error
14 BIFF error encrypted
15 BIFF error unsupported version
16 Semantic error
Error Code 3 = General ODBC error.
Or it can be syntax issue, if you use old version of qlik.
You can even check by enabling document log.
It could be due to OLEDB or ODBC connection string you have. Make sure you use same drivers for both environment.
You can try by increasing document timeout. QEMC--> Documents --> User Documents --> Select your Document --> Performance tab --> Document timeout provide a sufficient value here.
Regards
ASHFAQ
Hi,
What is the document log showing? This"Information Reloading" is like a wait state. We are waiting on information from the data source. Might try to do a SQL trace to see what is happing on that side.
Bill
Hi Ido:
In my case, I solved it!, starting qv distribution services with an user with administrative privileges on the server, not on the domain.