Skip to main content
Announcements
See what Drew Clarke has to say about the Qlik Talend Cloud launch! READ THE BLOG
cancel
Showing results for 
Search instead for 
Did you mean: 
Ankit1988
Contributor III
Contributor III

QlikView QMC Application Failed

QlikView Application failed Due to Following Log Reason

Error: Cannot open file: '\\10.100.8.5\e$\Q-Insure\Data\Stage1\QVDs\Operation\Stage1_gen_prop_information_tab.qvd'

please can any one can give me the brief Explanation regarding this issue and how to resolve this issue.

Labels (1)
  • QMC

4 Replies
Vicky_Z
Support
Support

Usually it is not recommended use "$" in the path in Qlik products though it might work sometimes.  Try to make a shared folder on that drive and use its UNC path, similar to \\10.100.8.5\<Shared folder>\Q-Insure\Data\....

Ankit1988
Contributor III
Contributor III
Author

Path is correct . similar path of another application is run completely  on same path but this application is shown 

Error: Cannot open file: '\\10.100.8.5\e$\Q-Insure\Data\Stage1\QVDs\Operation\Stage1_gen_prop_information_tab.qvd'

NadiaB
Support
Support

Hi @Ankit1988 

Does your other app has a path including 'e$' as well?

it is suggested to use UNC path and verify the service account has access to the folder. 

Hope it helps. 

Don't forget to mark as "Solution Accepted" the comment that resolves the question/issue. #ngm
marcus_sommer

Login with the QMC user on the machine which runs the QlikView services. Open the Windows explorer and copy & paste there the mentioned path: \\10.100.8.5\e$\Q-Insure\Data\Stage1\QVDs\Operation\

If you couldn't reach the path - the path is wrong and/or there aren't proper access rights. If you could see the qvd then try to rename the file maybe by adding an xyz to the end. If the measure failed the file might be locked from any process and/or again the necessary access rights aren't there.

In all cases you should get any error-message with information why it happens which should simplify further investigations.

Beside of this it's usually helpful to restart all QlikView services and the server-machines as well as the machines/servers which run your storage - which would exclude to look for any temporary issue.