Citrix Profile Management is not operating on the VDA because the Citrix Profile Management service failed to start in a timely fashion. This occurs when the “Path to log file” Profile Management policy or PathToLogFile parameter has been set to a remote machine (UNC path).

The event logs may include the following entries:

• Event 7000 appears in the system Event log: “The ctxProfile service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.”
• Citrix Profile Management service startup failure can trigger other Profile Management-related failures:
  • Application Event ID 1534, Citrix Profile Management
  • Application Event ID 3003, Citrix Profile Management
  • Application Event ID 2001, Citrix Profile Management

Solution 1

1. Using a registry editor, locate the following registry key:

2. If the key does not exist, the Windows default value will be used.
3. If the key exists but is set at too low a value, increase accordingly.
   • For most scenarios, it is recommended to set the ServicesPipeTimeout value to decimal 300000 (5 minutes).
4. Reboot the machine and confirm Citrix Profile Management service starts up successfully.

Solution 2 (WEM Agent considerations)
If the Citrix Workspace Environment Management (WEM) Agent will be installed on the machine, be aware that during a default WEM Agent installation, the ServicesPipeTimeout value is set to 60000 (1 minute).

If 1 minute is too low, change accordingly as per the steps shown in Solution 1 above.
To prevent a default WEM Agent installation from changing the ServicesPipeTimeout value to 60000, installation cmdline parameters can be used to set the value to 300000:
”Citrix Workspace Environment Management Agent Setup.exe” /v”ServicesPipeTimeout=\”300000\””

Solution 1 & 2 Notes:

1. If no communications are possible after the timeout value, the Citrix Profile Management service will fail to start.
2. Customers should investigate and resolve any communications issues between the Profile Management service and the remote logging machine, as part of the solution.

---

Problem Cause

On startup, the Citrix Profile Management service writes to the Profile Management logs specified by the PathToLogFile parameter. If the path to the log files have been configured to a remote machine, it is possible that network or other issues may either delay or prevent communications between the Citrix Profile Management service on the VDA and the remote machine. If this occurs the Citrix Profile Management service startup can timeout and fail. The timeout value is controlled by the system registry key: ServicesPipeTimeout

The default ServicesPipeTimeout value for Windows operating systems is decimal 300000 (5 minutes). However some applications like WEM Agent and other third party apps may change the ServicesPipeTimeout value during installation.

Microsoft support article: A service does not start, and events 7000 and 7011 are logged in the Windows event log

Install and configure WEM Agent for on-premise deployments:
https://docs.citrix.com/en-us/workspace-environment-management/current-release/install-and-configure/agent-host.html

Install and configure WEM Agent for Cloud Workspace Environment Management deployments:
https://docs.citrix.com/en-us/workspace-environment-management/service/install-and-configure.html