Custom directory groups get lost

[michael_klix]

Hi everybody,

we have an Enterprise Server running and increasingly find out that groups from the custom directory get lost.

Usually we realize this only, when users complain that they do not have access to a qvw any more. Investigating the case, it turns out that the qvw is distributed to a group (still configured and visible in the task)   that does not exist. Older backups from the CustomDirectoryData.XML file show that this group indeed did exist and included the user who complained.

This happened about 5-10 times during the last 6 months. and we solve it by redoing the lost group.

Did anyone have the same issue with the custom directory?

Here our system info for reference. This is the server for the QEMC and webserver only, not the application server.

Product Information
		Product name	QMS Backend Core x64
		Client Build Number	11.20.12664.0
		Target Platform	x64
		Publisher License Key	xxxxxxx
		Number of Distribution Services Allowed	1
		PDF Distribution Allowed	Yes
		Service authentication	AD groups
	Machine Information
		Computer Name	xxxxxxx
		Operating System Version	Win32_OperatingSystem=@ X64 (Microsoft Windows NT 6.1.7601 Service Pack 1)
		.NET Version	4.0.30319.1026
		Physical Memory	4095Mb
		Available Memory	2915Mb
	CPU Information
		CPU 0	Quad-Core AMD Opteron(tm) Processor 8360 SE

Product Information
		Product name	QlikView Directory Service Connector x64
		Client Build Number	11.20.12664.0
		Target Platform	x64

Hope someone can share experience.

Keep Qliking

Michael

[marcus_sommer]

Hi Michael,

I use usergroups within the custom directory since several years and have never had any issue with them and I have never noticed similar topics here in the community. Maybe bbt could give some hints.

- Marcus

[Anonymous]

I have observed this problem in version 11.20.12860.0

Here is what I think is happening.

When you open the management Console I believe it is caching a version of this file.

C:\ProgramData\QlikTech\DirectoryServiceConnector\CustomDirectoryData

This file holds all custom users and groups.

The problem arrises when you have multiple administrators.

When they open the management console and add users.

Then they are updating a cached version of this file(CustomDirectoryData) which may have been updated by another administrator.

As a workaround, I ensure that I kill all IE sessions on my server before I add users. Ive not seen the problem since.