What is CServerDocumentEntry and Why is It Erroring?

[#1]

Im receiving hundreds of errors each day due to this error.

Can someone explain it and maybe how to solve it?

CServerDocumentEntry: Could not fetch modified time for [APPID]. Skipping newest check.

[Anonymous]

Which version are you having the issue with?  I'm having it in 3.2 SR4.

[#3]

3.2 as well.  Do you have any ideas?

QlikSenseServer 10.18.1

More info below.

• .NET SDK 12.3.1
• QIX Engine 12.2.1
• Service Dispatcher 13.0.0
• App Migration Service 4.5.1
• Data Preparation Service 2.2.4
• Broker Service 5.1.0
• Proxy 11.11.0
• Repository 12.16.0
• Scheduler 12.0.0
• Printing Service 11.8.1
• Hub Service 0.14.0
• Qlik Sense Browser 4.4.3
• Qlik DataMarket Connector 2.4.1.5
• Qlik REST Connector 1.1.0.2889
• Qlik SalesForce Connector 14.1.0.2304
• Qlik Essbase Connector 1.0.1.2256
• Qlik ODBC Connector 1.2.1.2228
• Client 3.42.5

[#4]

Hi,

I've got the same ERROR in QS_System_Engine log and I've found that investigating an Error in Engine which I receive from time to time working on Hub/QMC.

Did you manage to fix it or find the reason of it?

I also run ver 3.2.4.

Thank you.

[Anonymous]

In my case I used the PostgreSQL to query the Apps table with the ID displayed in the message and found there was a record there that indicated the it was deleted, but was still generating the error.

[Anonymous]

Seeing the same behavior on our Qlik Site cluster 3.2.1 across both production and development nodes

[shaun_lombard]

It looks like this is fixed in September 2017 release. See release note below:

When app is deleted while open on a rim node, an error is placed in the log file

Jira issue ID: QLIK-77860

Description: If an app gets deleted while it is open on a rim node, the “CServerdocumentEntry: could not fetch modified time for [xxx]. Skipping newest check” is added to the log file. This is not an error, and recording the error message in this case is misleading.

[jaisoni_trp]

Actually we are on September release and its not fixed yet. Seems like its fixed in November release.

Note: at some point bug ID QLIK-77860 was shown in release note September 2017 which is not correct and R&D Team can't recall or added to November release note.