Evosus Mobile Windows Service is not running, therefore preventing successful sync.  

In this particular scenario, the problem will also prevent other services from running as well, such as the Daemon and WebAPI. The cause of the issue has been identified as another windows service, which uses the same registry key noted below, is using up memory (memory leak). 

To verify you are experiencing this particular issue, be sure to check the Event Viewer where the Evosus Services run and check the logs. If this issue is occurring, you will see an error for the Evosus Mobile Windows service with the following information: Error occurred in COMWorkerRunSTA: Retrieving the COM class factory component with CLSID{280105A5-920D-41B2-8DBC-68B8273CEB17} failed due to the following error: 8007000e Not enough storage available to complete this operation.


Do these steps cautiously!  - Temporary fix, need to restart their machine more often.

Step 1: Increase Shared Section Attribute Level

Run: regedt32

Change the SharedSection attribute of the value at this location:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows

Step 2: Reboot the Server

In our experience, updating the shared attribute value will extend the amount of time until the issue occurs again if you cannot ascertain the particular service that is causing the problem. You must reboot the server once the limit is reached or exceeded to restore the services.