The issue is not specific to PolySpace. This issue is due to the fact that you are accessing a network folder by its mapped drive letter. When a Windows service starts, the network drives are not mounted and the services can not access them. This is the reason why the Remote Launcher daemon does not start.
To work around this issue, use the whole UNC path (\\network\location\) instead of the mapped drive (R:\). If you use the UNC path, the daemon will start properly.
Note that it is not recommended to use a network drive as the data directory due to following reasons:
1. Performance : Using a network drive will slow down the verifications
2. Stability : Networks are often unstable and suffer from micro-cuts. This may cause some sporadic I/O failures
Best Answer