On our Windows 2012 R2 Remote Desktop Collection, We were receiving the following error: could not create a published application instance on the server
Log Name: Microsoft-Rdms-UI/Admin
Source: Microsoft-Windows-Rdms-UI
Date:
Event ID: 16393
Task Category: Publishing
Level: Error
Keywords:
User: domain\user
Computer: server.domain.suffix
Description: Publishing Failed for RDSH Collection - RemoteApp name: Sage 50 Report Designer Collection name: QuickSessionCollection Failure: Could not create a published application instance on the server server.domain.suffix.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Rdms-UI" Guid="{GUID}" />
<EventID>16393</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>30</Task>
<Opcode>0</Opcode>
<Keywords>0x2000000000000000</Keywords>
<TimeCreated SystemTime="2017-04-19T07:26:59.337215000Z" />
<EventRecordID>7</EventRecordID>
<Correlation ActivityID="{ActivityID}" />
<Execution ProcessID="4996" ThreadID="5604" />
<Channel>Microsoft-Rdms-UI/Admin</Channel>
<Computer>Copland.sircles.net</Computer>
<Security UserID="UserID" />
</System>
<EventData>
<Data Name="arg1">RemoteApp name: Application Name Collection name: Collection Name Failure: Could not create a published application instance on the server server.domain.suffix.</Data>
</EventData>
</Event>
Our issue was expired certificates in the RD server set-up which were interfering with the system even though in IIS they were all up-to-date and the server was working fine.
So under server manager we went into the RD settings and then highlighted the deployment and under tasks chose 'edit deployment properties' and went to the certificates page:
Here we chose the new certificate, one-by-one, to replace the expired certificates:
And then applied each certificate replacement before attempting the next.
Once all the certificates were showing as status OK, we re-published the RemoteApp settings:
And the publish now suceeds:
