Error: The Source Document was NOT reloaded successfully(QMC).

[SNR1]

HI Team,

Please could you be so kind and explain me what could be possible reason of not reloading QV apps by server? and ITS successfully completed on manual reload.Please help ASAP

The task "SAP.qvw" failed. Part of the log file
follows:

11/15/2018 6:08:08 PMErrorThe Source Document was NOT reloaded successfully.
DocumentPath=C:\ProgramData\QlikTech\SourceDocuments\QVD
Datawarehouse\SAP.qvw.
11/15/2018 6:08:08 PMErrorThe task "SAP.qvw"
failed. Exception:
QDSMain.Exceptions.TaskFailedException: Task execution failed with errors to
follow. ---> QDSMain.Exceptions.ReloadFailedException: Reload failed --->
QDSMain.Exceptions.LogBucketErrorException: The Source Document was NOT
reloaded successfully.
DocumentPath=C:\ProgramData\QlikTech\SourceDocuments\QVD
Datawarehouse\datawarehouse - USI SnapShot.qvw.
at QDSMain.ReloadTask.VerifyConditions(TaskResult taskResult)
at QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult,
String sectionAccessUserName, String sectionAccessPassword, eReloadOptions
reloadOption, String variableName, String variableValue, Boolean
moniterCpuUsage)
--- End of inner exception stack trace ---
at QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult,
String sectionAccessUserName, String sectionAccessPassword, eReloadOptions
reloadOption, String variableName, String variableValue, Boolean
moniterCpuUsage)
at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult)
--- End of inner exception stack trace ---
at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult)
at QDSMain.Task.AbstractTask.TaskExecution(ILogBucket logBucket,
TaskResult taskResult)

ISE Labs Confidentiality Notice:
The preceding message (including any attachments) contains proprietary
information that may be confidential, privileged, or constitute non-public
information. It is to be read and used solely by the intended recipient(s)
or conveyed only to the designated recipient(s).
If you are not an intended recipient of this message, please notify the
author or sender immediately by replying to this message and delete this
message (including any attachments hereto) immediately from your system.You
should not read, retain, disseminate, distribute, copy or use this message
in whole or in part for any purpose, not disclose all or any part of its
content to any other person.

Thanks In ADvance

[shiveshsingh]

Can you share the log file?

[SNR1]

HiSivesh 

curently i don't have the log file for this app

is there any other way to get the error reason

please help me

Thanks InAdvance

[avinashelite]

The QMC log won't record the actually issue , we need to get the document log only . Th app might get failed for multiple reason so it would be to hard to guess without the document logs ...

To get the document to log go to > document location > appname.qvw.log 

[sasis551]

Hi,

can you enable this ...it will generate log file.

[SNR1]

Yes Sasi,

i did  and now i don't have access of file and its handling by higher level they just provided above info only.
but my issue is here in QMC task  failed with above error and manually reloaded its success-ed i want to know the main reason for that and 

also in which cases /what are the possibilities for this  type of error in QMC
have any idea please inform me guys

how we can easily identify and resolve those  issues.

Thanks In Advance

[marcus_malinow]

The reason for your reload failure could be one of many - some general issues, and some specific to your environment. Without looking into the document log only a clairvoyant will be able to help you

[SNR1]

Thanks sasi

For your support 
is there any other process to know more about  qmc issues with examples

like general/generic issues  what we need to follow.

Once again Thanks  Guys 

[Chip_Matejowsky]

As stated previously, the only way to know for sure of the root cause of the reload failure is to review the Document log of the reload.

Often times if a QVW can be reloaded successfully using QlikView Desktop, but fails when run from QlikView Server/Publisher, a permissions issue is the cause. When running a reload from QV Desktop, the logged in user's permissions are used. When running a reload from QlikView Server/Publisher, the service account running the QlikView Distribution Service (QDS) permissions are used. 

Other instances where reload is successful from QV Desktop but not from Server/Publisher include database driver issues, STORE to QVD calls near end of load script, etc. Without the Document log, it is extremely difficult to guess as to what the actual cause for reload failure is.

One test you can try is to log on to a computer with QV Desktop installed using the QDS service account, open the script editor, click the Debug icon and run the reload in debug mode. This should return an error with greater information as to what is occurring to cause the reload to fail at the document level.