This article sums up common configuration issues with Royal TS and Royal Server and explains how to fix them.
Unable to connect to remote server.
Royal TS cannot reach Royal Server over the network. Ensure that Royal Server is running (check the Windows Service "Royal Server") and that the configuration is correct (ComputerName, Port and use SSL in the Management Endpoint Configuration of Royal TS). Connecting to remote managed servers might cause some issues too. To rule out these problems, use "localhost" as Computer Name for your connection to test if you can reach Royal Server at all.
Additionally, you can use the "Test" button in the configuration of the Management Endpoint to test connectivity.
Royal Server is configured to require Authentication.
In this scenario, Royal Server has been configured to accept only requests that are authenticated (see Royal Server - Service Configuration - Require Authentication). You need to assign a credential to the Management Endpoint Connection in Royal TS and make sure that this user is also added to the local Windows User Group "Royal Server Users" on the machine Royal Server is running.
In rare cases, internally Windows is throwing the following exception: "Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again". In this case, please reboot the Royal Server machine. We are working on fixing this.
User credentials cannot be used for local connections.
This error comes from a limitation of the operating system feature we use for our modules (WMI): If you specify "localhost" as Computer Name in the connection (which is the Royal Server itself) you can not use Authentication.
The request failed because of a security exception ( 0x80070005 (E_ACCESSDENIED))
In many cases, Royal Server is using Windows Management Instrumentation (WMI) to access the managed servers. WMI itself is using DCOM underneath and this has its own security layer. E_ACCESSDENIED usually means that the specified user (the Credential in the Royal TS Connection) does not have enough DCOM rights. Use a local administrator to ensure the account has enough rights. Another reason is that name resolution is not possible - try an IP.
Also, specify the account using the following syntax: <domain>\<username>, also for local account use .\<name> e.g. ".\testlabadmin"
This error occurs if username has been specified wrongly. Please use the following syntax: <domain>\<username>, also for local account use . \ <name> .e.g. ".\testlabadmin"
Error while impersonating user '...': 1326
Royal Server is using LocalSystem as a service account but for the actual work, it is using a Worker Account. You can and should specify this Worker Account in Royal Server - Service Configuration. If you receive this error, you have not specified a valid username/password combination for the Worker Account. Also, make sure, this account is a local administrator.
Immediately after a Royal Server installation, no Worker Account is configured and Royal Server is using LocalSystem which will not work, since this account does not have network access. If you update Royal Server with a new (beta) msi, the previous configuration is used.
The RPC Server is unavailable (0x800706xx)
This error is internally thrown as 0x800706xx and usually means that the Windows Firewall is blocking the request. Either configure the managed server with prepare_server.ps1 script which can be found in the installation directory in ./scripts/ or you manually enable the following rules in the Windows Firewall: "Windows Management Instrumentation (DCOM-In)" and "Windows Management Instrumentation (WMI-In)"