Oke we Changed the user account for the Server module in the application settings to the SCPServer AD User account and then the server started the installation, only to come to the following error:
[1/13/2017 11:45:15 AM] WARNING: Invoke error: ArgumentNotValid: The role, role service, or feature name is not valid: 'Desktop-Experience'. The name was not found.
[1/13/2017 11:45:36 AM] WARNING: Invoke error: [HOSTNAME] Connecting to remote server HOSTNAME failed with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet. For more information, see the about_Remote_Troubleshooting Help topic.
Oke now I can add the server by changing the AD Connection setting, but now if i try to create a Collection under the Customer i get the following error:
Logged User:
serveradmin
Work on Behalf:
CUSTOMER
Hosting Space:
13
Stack Trace:
System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Error executing 'ADD_RDS_COLLECTION' task on '' REMOTE_DESKTOP_SERVICES ---> System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Collection not created
at SolidCP.Providers.RemoteDesktopServices.Windows2012.CreateCollection(String organizationId, RdsCollection collection)
at SolidCP.Server.RemoteDesktopServices.CreateCollection(String organizationId, RdsCollection collection)
--- End of inner exception stack trace ---
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at SolidCP.Providers.RemoteDesktopServices.RemoteDesktopServices.CreateCollection(String organizationId, RdsCollection collection)
at SolidCP.EnterpriseServer.RemoteDesktopServicesController.AddRdsCollectionInternal(Int32 itemId, RdsCollection collection)
--- End of inner exception stack trace ---
at SolidCP.EnterpriseServer.RemoteDesktopServicesController.AddRdsCollectionInternal(Int32 itemId, RdsCollection collection)
at SolidCP.EnterpriseServer.esRemoteDesktopServices.AddRdsCollection(Int32 itemId, RdsCollection collection)
--- End of inner exception stack trace ---
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at SolidCP.EnterpriseServer.esRemoteDesktopServices.AddRdsCollection(Int32 itemId, RdsCollection collection)
at SolidCP.Portal.RDS.RDSCreateCollection.btnSave_Click(Object sender, EventArgs e)
Hello,
Can you check the windows eventlog for any errors on the RDS Gateway? This will normally give more detailed errors as to the problem.
Kind Regards,
Trevor Robinson
Hi Travor,
Dont know what happened but even though we got that error the collection was actually created, only the Server Manager (in Win2K16 did not show the collection until a reboot) and SCP could not import the Collection, when we deleted the Collection manually and then recreated it and it was no problem.
Thanks you for your support anyways!
Greetz, Kevin
