Qlik Community

QlikView Deployment

Discussion Board for collaboration related to QlikView Deployment.

Announcements

Breathe easy -- you now have more time to plan your next steps with Qlik!
QlikView 11.2 Extended Support is now valid through December 31, 2020. Click here for more information.

bnichol
Not applicable

Prevent Server Restart when Corrupt Document loaded

Is there a way to configure the Qlikview Server to prevent the Server from restarting when a corrupt document is loaded?

I have 75+ application running on a Qlikview version 9 SR4 server, and I don't want all my clients impacted if only one of the applications is experiencing problems.

Here's what was recorded in the server event log when the issue occured...

110 Warning The document failed to load because of an I/O error or a corrupt document.

131 Error DOC loading: Exception -2 while loading document

120 Error Server aborted trying to recover by restart. Reason for restart: Internal inconsistency, type D, detected.

Any suggestions would be appreciated?

B

8 Replies
Not applicable

Prevent Server Restart when Corrupt Document loaded

The inconsistency error can happens some time but it is hard to find why (as far as I know).

I'm not very confident in SR4 so I would, if this is possible install SR5 and test again.

If problem still happens on this specific document I would check the document Log, and server events logs.

I would also try to reload the document using Qlikview Developper.

Hope this will give you some clues

Sébastien

bnichol
Not applicable

Prevent Server Restart when Corrupt Document loaded

The question was...

Is there a way to configure the Qlikview Server to prevent the Server from restarting when a corrupt document is loaded?

Not applicable

Prevent Server Restart when Corrupt Document loaded

The server is not supposed to restart when a document is corrupted. And As I said this error is normally rare.

This is why I would suggest to install the SR5 because I saw some strange behavior with SR4. But now I cannot guarantee you that it will solve the issue.

bnichol
Not applicable

Prevent Server Restart when Corrupt Document loaded

Thanks.

ggg
Not applicable

Prevent Server Restart when Corrupt Document loaded

Hi B,

If you still encounter internal inconsistencies in SR5 (reload the document with SR5 as well) please get in touch with QlikView Support so that we can help you in setting up crash logging.

Type-D is most likely related to an issue with document but it can only pin-pointed if captured properly. This can be something very simple such as a corrupt object in the layout but the best outcome is usually achieved via crash logging.


Regards,

Gustav

lhr
Not applicable

Prevent Server Restart when Corrupt Document loaded

this is a bug. the corrupted document is not unloaded properly which in turn can cause the internal inconsistency. not loading corrupt documents is one workaround Wink

bnichol
Not applicable

Prevent Server Restart when Corrupt Document loaded

Is there a way to not load corrupt documents automatically? Or is there a way to automatically test for corrupted applications?

These documents are reloaded automatically, and the corruption occurs sporadically, but there is no visibility in the log?

lhr
Not applicable

Prevent Server Restart when Corrupt Document loaded

unfortunately nothing that i know of. isn't there any errors/warnings in the distribution service log related to the tasks that ends up with a corrupted document?