Store a QVD created by another developer?

[#1]

I can execute a qvw and create the qvd.

Then logoff and login as another user and execute the same qvw.

The script fails and the qvd is not overwritten.

Repeat as the first user and it works.

Both developers have full admin rights on the development server.

I did this test with no other developers in the building.

Any ideas how to allow the full admin to work?

Conclusion

A team member helped, by removing the share from the root of the drive.

Then reset the permission and ownership to the Administrator Account.

This is the same one the services run on and then we re-applied the user groups we wanted in the folder structure.

Then set the share on the folder below the root of the drive.

After that the behaviour stopped.

Thank you for your advice.

Regard

[Miguel_Angel_Baeyens]

Hi Jonathan,

How are you reloading the file, using Desktop or Server? Where does the script crash? Can both users delete the file manually? Is there any chance that the QVD is still in use by another scheduled reload?

Regards.

Miguel Angel Baeyens

BI Consultant

Comex Grupo Ibérica

[#3]

I am using the QV Client V10 SR3 on the server.
I have used the QEMC to run the and store the file.

The script fails at the store command.

Both users have full admin rights - delete, rename, copy etc.

I am the only person on the server - it is late here.

It is an odd fault/safe guard. If only there was a switch off?

I think it is a function of the store command or QV Client.

[Miguel_Angel_Baeyens]

Hi Jonathan,

Note that if you run the reload task from the QEMC, it's the user that runs the QlikView Services the one with permissions. Is that correct? That sounds really strange.

If you rename the QVD file and let the QEMC recreate it, does it work for both users? Is there any chance that one of the users has been added to a group but not logged in so the membership doesn't apply yet? Or that the user belongs to a more restrictive group so effective permissions are not full access?

Hope that helps.

Miguel Angel Baeyens

BI Consultant

Comex Grupo Ibérica

[#5]

I ask a colleague to check the permissions and both developers are in the Administrators Group with full permissions.

We checked the folders to clear any explicit names. So just the Administrators on the security tab.

The owner on the QVD files has been changed to Administrators.

The qvw just run and failed for developer1. Executed Reload via QEMC service running as developer1 - passed.
Run the Client reload for developer1 - failed.

Login with developer2 Client ran and passed

I will have another look tomorrow - Hopefully this nice ability to block file generation on file creater is known.

[#6]

QlikView will honour Full Administrator Permissions for the named developers when you explicitly stating it within the folder structure.

This is not what I want to have to do.

[Miguel_Angel_Baeyens]

Hi Jonathan,

Do you mean QlikTech says both developers need full control in that folder? If the QVD file has been created by one of them, and using the right click on the QVD file, does the second user have effective permissions to modify (at least) that file?

Regards.

Miguel Angel Baeyens

BI Consultant

Comex Grupo Ibérica

[#8]

Hi

My last post was how I personally got around the problem. So your first question is not appropriate.

Summary

Developer 1 creates a qvw and stores a qvd by running the reload script.

This developer is a member of the administrator group.

Developer 2 opens the qvw, Developer 1 does not have the qvw open, and runs the reload script.

This developer is a member of the administrator group.

The script fails and the qvd file in not overwritten. Also the qvw files can not be saved.

By using the last post method the script reloads and saving of the qvw works.

I do not know why this is the case. However the save and store commands are done in the QVW Application.

One last point; the names are present in an AD group and that is placed within the local administrator group.
The named developers are not explicitly in the local administrator group.

[Miguel_Angel_Baeyens]

Hi Jonathan,

The names within a group should not be a problem, provided they both have logged onto the local computer to get full membership and provided this membership does not conflict with any other more restrictive policy in that computer or the domain.

If that's the case, opening a support ticket would be a good idea, just to know if that is what is expected to behave or it might be a bug or something.

Regards.

Miguel Angel Baeyens

BI Consultant

Comex Grupo Ibérica

[#10]

Hi

'more restrictive policy' I was told that permissions work the other way round.

There developers are also in 'QlikView Administrator' Local Group.
They need to be there so they can use QEMC.

The group has more restrictive permissions.