Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
cbushey1
Creator III
Creator III

qvw fails to open

Hi there,

Came across an issue I am not sure how to solve (hence this post).

We are in the process of migrating from one server to another for applications. Our apps run in the traditional 3 tier setup (generator, data model, visual layer) and we have setup the same folder structure, same version etc on the new server.

We changed the name of the account that runs the QMC, as well as the active directory since we are moving over to a new one.

The apps have section access code in them but this is control via an If statement and a variable, so if the variable evaluates to 0, the section access logic is skipped in the data model.

The problem is that the data model and then subsequently the visual layer cant be opened by the QMC trying to do the reload. We have made sure the new services name is in the logic and have even turned off the SA code by setting the variable to 0 for this chunk of code.

The generator opens and runs fine.

Other accounts can access the data model QVW without issue.

This is the error we get from the TaskLog:

ErrorDocument open call failed. The document might require username and password.

QV 12.10

Server reload.

2 Replies
maxgro
MVP
MVP

Try to add the service name of the new server in the app (section access) and reload the app in the old server.

Then save the app and move the app to the new server.

Remember the backup when you "play" with section access.

cbushey1
Creator III
Creator III
Author

I am not sure the problem is section access related.

More details -

We found a work around for the data model. Basically, we create from scratch a new .qvw and copy the code over. When this is run by the new server it works fine. The visual layer utilizes a binary statement to load the DM and even after this workaround for the DM, the visual layer still throws the same error even though the new SA name is present in the DM.