Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

License problem and document reload

Dear all,

yesterday I had the following error each time I opened a document:

error.png

This file is recognized as one your own. However we must update the key in the document to reflect changes to your personal edition since you created this document. The document will now be updated and loaded without any data. After the operation coompletes, please SAVE the document and then perform a RELOAD.

This happened with every document I opened.

Moreover, my users couldn't access the documents with desktop nor webclient. And the reload failed. Here is one extract of the log file:

The task "[QVW]" failed. Part of the log file follows:

26/03/2012 16:02:05        Error      The task "[QVW]" failed. Exception:

QDSMain.Exceptions.DistributionFailedException: Distribute failed with errors to follow. ---> QDSMain.Exceptions.WritePermissionkException: Failed to get write permission for file: D:\QlikView\AccessPoint\I-I.4 (qvw)\Punctuality - Analysis 'Gazette'.qvw ---> System.IO.IOException: The process cannot access the file 'D:\QlikView\AccessPoint\[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)

   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)

   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access)

   at QDSMain.ReloadTask.CheckWritePermissionForFile(String fileName)

   --- End of inner exception stack trace ---

   at QDSMain.ReloadTask.CheckWritePermissionForFile(String fileName)

   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)

When I tried a manual reload, it worked without a problem. But I couldn't save the qvw as it was already in use by another service. I had to restart the services "server" and "webserver" to get everything to normal again.

What can I do to prevent this situation? What is the cause of this behavior?

9 Replies
flipside
Partner - Specialist II
Partner - Specialist II

I am assuming you lease a licence from a QV server - has the licence expired and your client reverted to Personal Edition?  Has your named CAL been deleted from the server? Has Allow Licence Lease been unticked in QEMC?

However I too have a similar issue.  It should be possible to lease a licence for 30 days, however my client lasts no more than 24hrs before reverting, and requires an Open In Server action to lease a new one.  Sometimes this just won't work and I have found if I restart the QV Server service, it works again.  I do not have any locations set for the License Lease Server in User Preferences.

If anyone else has experienced this and has a solution, I'd be grateful.  I'm on QV10 SR4.

flipside

Not applicable
Author

We are on QV 11.0.11154.0

I am assuming you lease a licence from a QV server -

That's right

has the licence expired and your client reverted to Personal Edition?

Sometimes that does happen like you describe it. I cannot lease my license much longer than 24hr without reconnecting to the server. I've called the support of QV and they said it is a known bug. I recentely recieved an e-mail notification about an update saying that this bug is resolved. I have yet to install the update though. In this case however, that didn't happen as I was working straight on the server that runs all the QV services.

Has your named CAL been deleted from the server? Has Allow Licence Lease been unticked in QEMC?

No and yes.

flipside
Partner - Specialist II
Partner - Specialist II

Hi bluemtms,

Thanks for the info on the bug - I suspected as much.  Do you have a bug reference in that email, it may be useful?

I have just noticed that when I cannot lease the licence, I am also prevented from opening AccessPoint docs using the plugin (but via AJAX is fine).  Also QEMC shows open document sessions for me, even though I have closed down the browser much earlier. 

Perhaps in your issue the server is keeping the file open in a similar manner and thus preventing the file being written to.

flipside

henry_so
Contributor
Contributor

I am experiencing the same task reload failure and found a solution. We checked out everything. The service account running the services have FULL control for both UNC and NTFS permissions. As it turned out, the qvw had the "Read-only" attribute on (see screenshot). It is working as soon as I remove it. Hope it helps.


Henry

vindhya_giri
Creator II
Creator II

Hi Henry,

I am facing the same issue. Can you please guide me on how do I get to this page which you provided a screenshot in your post?

I am trying to reload around 20 qvw's through QMC but only one qvw is giving this error.  This error message I am getting is through email.But when I reload the qvw manually, no issues.

All the other apps are reloading fine. I am wondering why, only this one particular qvw is giving this error that too only when trying to reload through QMC. It is not a new qvw. It is an existing one and never got this error for this app before.

Please advise

Thanks!

Anonymous
Not applicable
Author

The screenshot is from the Windows file properties of the qvw file Security tab.  Right click the qvw in File explorer to get to the properties.

Tony_Strano
Employee
Employee

Could be that the service account that is running the QDS server doesn't have permissions on the file.   Or if the ODBC or files being access are also not available to the service account.

Tony_Strano
Employee
Employee

Someone may have that document opened in the Desktop client.   If they change permissions on the file,  the service account that is running the QDS  may not be able to overwrite it during the reload and distribution process.   Don't share out the mounted folders.   distribute to a folder instead for power users who use the desktop client. !

vindhya_giri
Creator II
Creator II

Hi Bill, Thanks!

I had the read-only attribute check marked for that particular qvw which was failing. Unchecked it  and the issue was fixed.

Thanks!