PeerSync fails to run as a service

Problem

PeerSync fails to connect to the service when launched from the Profiler and starting the service manually results in "Error 1053: The service did not respond to the start or control request in a timely fashion".

Solution

The above conditions can occur if Remote Desktop Services (Terminal Services in Server 2008 and earlier) is installed on the PeerSync server. Before PeerSync is installed, RDS should be placed into Install Mode. This is due to the manner in which RDS handles writes to and reads from the registry when in Install Mode vs. Execute Mode (see https://support.microsoft.com/en-us/kb/186504).

The following steps must be performed before installing PeerSync on a server running RDS:

1. Click Start, and then click Run.
2. In the Open box, type cmd, and then click OK.
3. At the command prompt, type "change user /install", and then press ENTER. The following message appears:
   
   User session is ready to install applications.
    
4. Type exit, and then press ENTER.
5. Install PeerSync normally
6. Launch the PeerSync Profiler and install the user's profile as an NT service
7. Save the profile and close the PeerSync Profiler
8. Click Start, and then click Run.
9. In the Open box, type cmd, and then click OK.
10. At the command prompt, type "change user /execute", and then press ENTER. The following message appears:
    
    User session is ready to execute applications.