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,

In Windows, as a general rule both shared resources and folder permissions work in the most restrictive permissive applies, meaning that if a user belongs to two different security groups, the one with the most restrictive permissive rights applies (N.B.: if they are denied explicitly, then the most restrictive applies over the less restrictive). That might be happenning in your case. To check which effective permissions a user has on a folder or a file, right click on it, go to Properties, Security, Advanced, Effective Permissions and click on Select. Select both users and see if both can modify or higher.

Besides, when a user is added to a local group (and sometimes, to domain or universal security groups) the new membership does not apply until the user has logged on to the computer where the security group is. In your case, is a group within a group, so both users will need to log on to that computer where QlikView Server is to take full membership of the groups they belong to in that computer.

In regards to the QlikView Administrators, as you well say, it's only to use the Management Console and related services, and you can add any user to that group as an administrator to, say, perform reload tasks, even if they don't have a license assigned.

Hope all the above makes sense and help.

Miguel Angel Baeyens

BI Consultant

Comex Grupo Ibérica

[#3]

Too conclude this discussion.

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.

Regards