No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


How to settle the problem that the virtual machine’s policy has been applied failed

Publication Date:  2012-11-12 Views:  93 Downloads:  0
Issue Description
After configuring on the DDC server, we will apply these policies to the user’s virtual machine. If some “dll” files of the operating system are damaged, it will cause the application policies to be unsuccessful. How to locate this kind of problem and how to settle it?

Alarm Information
Handling Process
When the virtual machine’s policy applying failed, check the system logs of the virtual machine, we will find the following information:
1. Prompt alarm about the “policy applying failed”:
The Citrix Workstation Agent service was unable to apply computer policies.
Error Details:
Call to CitrixProcessGroupPolicy failed
2. In front of the above alarm, there is the error information about “Application Error”:
The program name of the wrong application: CitrixCseEngine.exe, version:, timestamp: 0x4e0bc19a.
The name of the wrong module: MSVCR90.dll, version: 9.0.30729.4926, timestamp: 0x4a1743c1
The abnormal code: 0xc0000417
The wrong offset: 0x00066499
The wrong process: 0x17a8
The start time of the wrong application program: 0x01cd17a6eb630f6a
The path of the wrong application program:  c:\Program Files\Citrix\Group Policy\Client-Side Extension\CitrixCseEngine.exe
The path of the wrong module: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4926_none_508ed732bcbc0e5a\MSVCR90.dll
The reporting ID: 34ff7d6b-839a-11e1-998e-c8de8812a076
From the above information we can conclude that is the “MSVCR90.dll” file in the catalog of “C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4926_none_508ed732bcbc0e5a” has error which causes the application policy to be unsuccessful.

Handing steps:
1. We can copy a undamaged “MSVCR90.dll” from another well system to substitute the damaged one in the virtual machine.
2. Reinstall the VDA software in the virtual machine.

Root Cause