Hello Community, For only one document I am getting the below QMC error and for rest of them no failures.
Error: The task "Dashboard" failed. Exception: || QDSMain.Exceptions.TaskFailedException: Task execution failed with errors to follow. ---> QDSMain.Exceptions.WritePermissionkException: Failed to get write permission for file: \Dashboard.qvw ---> System.IO.IOException: The process cannot access the file '\Dashboard.qvw' because it is being used by another process. || at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) || at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) || at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access) || at QDSMain.AbstractReloadTask.CheckWritePermissionForFile(String fileName) || --- End of inner exception stack trace --- || at QDSMain.AbstractReloadTask.CheckWritePermissionForFile(String fileName) || at QDSMain.AbstractReloadTask.Reload(String fileName, IExecutingTaskResult executingTaskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) || at QDSMain.DistributeTask.PerformExecute(IExecutingTaskResult executingTaskResult) || --- End of inner exception stack trace --- || at QDSMain.DistributeTask.PerformExecute(IExecutingTaskResult executingTaskResult) || at QDSMain.Task.AbstractTask.TaskExecution(CurrentExecutionArgs args)
I don't see how any bookmarks could cause a reload failure.
Did you say that it works in the client or not, sorry i can't see a reply for that.
If it does, does it work all the time or is it the same as the QMC and fails a handful of times?
Because reloads from the QMC do actually work and just fails sometimes, it does suggest the file is being locked by something. I am not good enough on this subject to know what logs you could check at the time of a failure but I'm sure whoever your Qlik support agreement is with (Whether its Qlik them selves or a partner) would be able to help you if it comes to it escalate the problem if not resolved efficiently.
I work for a partner and my experience with Qlik Support has always been very good.
Sorry i couldn't help anymore, maybe someone else can chip in.
Also, Brett's suggestion on bumping up the reload tries could be a work around whilst investigating the issue.
I did have this issue with one of my clients in the past and we bumped it up to 5 (if i remember correctly) and we very rarely seen the issue occur again. obviously the issue was still there, it was just being hidden. as long as the reloads work within those 5 times then thats all that matters for the users.
Investigation could carry on between you/IT/Qlik support in the mean time.
