Go Back

What Is the Root Cause Of xfServerPlus 1355: The specified domain either does not exist or could not be contacted?

As we've moved to faster and faster hardware we have noticed that several xfServerPlus Services will fail to start after a restart with the following error:

The TIMSxfServerPlus service terminated with the following error:
The specified domain either does not exist or could not be contacted.

The Windows Error Code is 1355

The Event ID is 7023 and comes from Service Control Manager.

The services are set to "Automatic" Start and use the Local Service as the Logon for the Service.

xfServerPlus is configured to use a network account for its xfServerPlus Processes

Restarting the services after a time seem to fix the problem.

2 Answers
0   | Posted by Ace Olszowka to xfServerPlus on 11/16/2018 4:21 PM
Best Answer chosen by Ace Olszowka
Ace Olszowka
Previously (In releases of Synergy Prior to 10.3.3a) this would cause a segmentation fault. That issue was corrected under Trackers 36577 and 36571 when it was originally reported. However the behavior of failing to start will still persist in 10.3.3f, but at least it will not crash.

The root cause of this failure is the fact that xfServerPlus is being configured to use a Network/Domain Account and the "Server" (LanmanServer) service has not been started (or is stopped).

There are a couple of fixes to this:
  1. The most correct fix: If your xfServerPlus instance is configured to run with a Network/Domain Account there should be an explicit dependency upon the Server/"LanmanServer" Service. You can perform this process via the command line as documented here https://serverfault.com/questions/24821/how-to-add-dependency-on-a-windows-service-after-the-service-is-installed on ServerFault. Doing it this way allows Windows to properly determine the correct startup order
  2. The hacky fix: If you set your xfServerPlus Processes to "Automatic (Delayed Start)" the service will start up after some undocumented time (seems to be about 5 minutes) which by this point most services that are depended upon will start properly https://docs.microsoft.com/en-us/windows/desktop/services/automatically-starting-services

I am submitting a feature request such that when rsynd detects that a Network/Domain Account is being used that it automatically add this explicit dependency to help be setup correctly "out of the box".

11/16/2018 4:30 PM   0  
Ace Olszowka
Now that I have written this out I am not so sure that it is because of a dependency on the Network/Domain Account. There is a possibility that, due to legacy licensing this is actually attempting to access the Named Pipe of the license server prior to using TCP. If LanmanServer is not started this will fail. I will update my ask to just explicitly add this.

The long story short is that rsynd has an explicit dependency upon LanmanServer and should be clear about it.

11/16/2018 4:39 PM   0  
Please log in to comment or answer this question.