none
Problem with publishing remote APPs in server 2012

    Pertanyaan

  • Hello,

    First sorry for my bad english :)

    I have a problem with my server 2012 when publishing remoteapp program. This error shows with every program i want to publish? Can you please help me.

    Error when trying to publish remote app: Failed: Coul not create a published application instance on the server: ......

    error in event viewer under Microsoft\windows\RDMS-UI\ Admin log

    Event ID 16393

    Publishing Failed for RDSH Collection - RemoteApp name: Excel 2013  Collection name: ........ Failure: Could not create a published application instance on the server .......

    Please i googled it and didnot find any solutions can someone help me?

    Kamis, 30 Mei 2013 06.46

Jawaban

  • Hey all...

    Had this same error and this is the first thread that came up on my searches, which is about as useful as a fart in the wind, given our situation. I'm not sure if the below will be any more helpful, but I've been scratching my head for a week trying to find out a solution without booting everyone out (users are connected around the clock) or recreating the collection (same reason again). This is the only thing I have done this morning after testing unsuccessfully again, and now it's working and I can publish and unpublish apps as necessary.

    2012 RDS server with about 20 users, some using RemoteApp and Desktop Connections. Everything worked fine until I went to publish Quickbooks for one of the users and got this error. For some reason the app would still show in the list of RemoteApp programs (in Server Manager) even though the wizard had failed - however the apps wouldn't show up in RDWEB, nor would they get published via RemoteApp and Desktop Connections.

    Anyway, all I did was go to Server Manager > Remote Desktop Services > Collections > select the collection > click on Tasks > select Edit Deployment Properties > select Certificates – and I noticed the certificate assigned to the roles there was still the old (expired) wildcard cert.  I just updated this to the current wildcard certificate and next time I tried the publishing it worked first time.

    Again, not sure if this will be relevant for 95% of cases, but if it even helps 1 person it’s worth me typing this out :)

    Selasa, 01 Juli 2014 03.07

Semua Balasan

  • Are you publishing apps to a session collection or a virtual desktop collection?

    If it is a session collection, I assume the server in question is one of your RDSH servers? A good first step would be to check the Windows Event Log on the server in question to see if there are any suspicious errors.


    Travis Howe | RDS Blog: http://blogs.msdn.com/rds/default.aspx

    Kamis, 30 Mei 2013 22.42
    Moderator
  • hello thank you for your answer

    I am publishing on session collection. I have just one RDS server on that server i have all services installed...

    I check the event viewer system and application. there where no such errors about this. There where just errors in application log about user profile services: event ID 1530: Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. i checked Some of the remote desktop event viewers there is just one error about RemoteFX module envent id 101: The network characteristics detection function has been disabled because of Client not supported..

    In System log it says something about terminalservices printers but that is just about driver.

    In event log for: Microsoft\windows\RDMS-UI\ Admin log i saw error which i posted in my first post.

    Could you be more specific where should i also look in event viewer for some error? Or where could i get some other info about this problem. i am unexpiriend about solving errors like this so i am where thankfull for any help you gave me...

    Jumat, 31 Mei 2013 06.45
  • Hello i found another thing... When i publish APPs such as Excell it appers on my rdweb session and i can open it. But when i want to change user assigment settings on the excell app this error appears :Could not create a published application instance on the server ..... I checked in event viewer no new errors...
    Jumat, 31 Mei 2013 15.53
  • That is... very odd. When apps are published or modified, changes are written to some WMI objects on the RDSH server. It seems like for some reason that is succeeding when you publish the apps, but is failing when you try to update the user assignment settings. I don't understand why that would happen.

    I suggest filing a bug on this with Microsoft. Sorry I couldn't be of more help.


    Travis Howe | RDS Blog: http://blogs.msdn.com/rds/default.aspx

    Jumat, 31 Mei 2013 18.39
    Moderator
  • Any updates?  I'm having the same problem.  Server was fine for about 3 months until one day I went to publish a new remote app.  Now it fails with the error you describe.
    Kamis, 08 Agustus 2013 14.11
  • I deleted the collection and created a new one that was my solution. Luckly i didnt have much programs in this collection so i didnt have much work for publishing them again... Hope you resolve your problem....
    Jumat, 09 Agustus 2013 08.04
  • That worked for me too.  My Remote App connection files didn't seem to need updating after trashing it and re-creating.  

    Well, they did work, now they seem to be broken.

    Thanks!


    • Diedit oleh Spames Jumat, 09 Agustus 2013 19.14
    Jumat, 09 Agustus 2013 19.10
  • Any news about this error? Today I started to get the same error from two separate Windows 2012 servers.
    Jumat, 02 Mei 2014 09.00
  • Hey all...

    Had this same error and this is the first thread that came up on my searches, which is about as useful as a fart in the wind, given our situation. I'm not sure if the below will be any more helpful, but I've been scratching my head for a week trying to find out a solution without booting everyone out (users are connected around the clock) or recreating the collection (same reason again). This is the only thing I have done this morning after testing unsuccessfully again, and now it's working and I can publish and unpublish apps as necessary.

    2012 RDS server with about 20 users, some using RemoteApp and Desktop Connections. Everything worked fine until I went to publish Quickbooks for one of the users and got this error. For some reason the app would still show in the list of RemoteApp programs (in Server Manager) even though the wizard had failed - however the apps wouldn't show up in RDWEB, nor would they get published via RemoteApp and Desktop Connections.

    Anyway, all I did was go to Server Manager > Remote Desktop Services > Collections > select the collection > click on Tasks > select Edit Deployment Properties > select Certificates – and I noticed the certificate assigned to the roles there was still the old (expired) wildcard cert.  I just updated this to the current wildcard certificate and next time I tried the publishing it worked first time.

    Again, not sure if this will be relevant for 95% of cases, but if it even helps 1 person it’s worth me typing this out :)

    Selasa, 01 Juli 2014 03.07
  • Do you have SQL DB on same box by any chance ?


    Sanket. J Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Selasa, 01 Juli 2014 04.33
  • Do you have SQL DB on same box by any chance ?


    Sanket. J Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    I do.  Does this make a difference?  Just started to get this type of error relating to publishing a new app.
    Rabu, 23 Juli 2014 10.13
  • Renewing the certificate resolved the problem for us.  As this is the only hit on Google for that literal error message, "Error when trying to publish remote app: Failed: Could not create a published application instance on the server", I'm replying just to help get this post more Google-love.
    Jumat, 25 Juli 2014 13.53
  • Anyway, all I did was go to Server Manager > Remote Desktop Services > Collections > select the collection > click on Tasks > select Edit Deployment Properties > select Certificates – and I noticed the certificate assigned to the roles there was still the old (expired) wildcard cert.  I just updated this to the current wildcard certificate and next time I tried the publishing it worked first time.

    You saved my day!
    Had exactly the same issue and this was the solution.

    Thanks a lot!

    Kamis, 02 Oktober 2014 08.07
  • worked for me too. Thanks
    Jumat, 10 Oktober 2014 12.36
  • Thanks - this fixed for us as well.
    Kamis, 19 Maret 2015 18.28
  • Hi Travis Howe,

    Thanks for your contribution its works for me..

    Regards,

    Thiyagu


    Rabu, 06 Mei 2015 07.25
  • worked for me too...thanks for the guide..
    Selasa, 16 Februari 2016 02.23
  • Worked for me also! Thanks for the information.
    Selasa, 21 Juni 2016 17.18
  • Absolutely relevant in my case. Thank you!!
    Selasa, 21 Juni 2016 19.14
  • solved my issue :)
    Rabu, 09 November 2016 20.36
  • This nailed it for me! Great work, Andrew. Saved me a lot of time troubleshooting.
    Jumat, 25 November 2016 11.33
  • Excellent work, this seems like the only page with a solution on the entire internet!
    Jumat, 27 Januari 2017 10.53
  • I actually have this exact scenario happening, but my certificate recently expired and I updated it. Has anyone seen this issue after updating their existing certificate? My certificate is currently valid, but was updated since the last time I've tried to publish anything new.
    • Diedit oleh dvosbury Kamis, 09 Maret 2017 21.22
    Kamis, 09 Maret 2017 21.21
  • I am having this issue today.  I deployed about 6 RemoteApps.  Everything went smoothly.  Then I tried to do a few more and I get the error "Failed: Could not create a published application instance on the server".

    My certificates are all valid until 2018, so I am not sure where to go from here.  Did you find a solution?

    Selasa, 23 Mei 2017 18.41
  • Sometime also farting can be useful, can prevent you to have a bad pain.

    Your solution worked for me so... thank you very much!!

    Selasa, 02 Januari 2018 19.44
  • Thanks, it works for me
    Jumat, 02 Maret 2018 13.14
  • Today I faced this issue and it got resolved via below method:

    After unpublishing the app, I went to RemotApp folder on Connection Broker server:

    C:\Windows\RemotePackages\CPubFarms\CCEP-APPS\CPubRemoteApps

    There I can see some files were still there related to application (icon etc). I manually deleted the files and tried republishing. It worked for me.

    • Disarankan sebagai Jawaban oleh Vive Mishra Selasa, 24 April 2018 07.28
    Selasa, 06 Maret 2018 12.16
  • this one works for me. thanks much.
    Kamis, 15 Maret 2018 00.53
  • Thank you! Saved me today when trying to configure a new app into a previously known-working collection. I had updated an SSL Certificate recently in IIS Manager on the same server, and didn't realise it had to be updated in the Collection as well.
    Jumat, 18 Mei 2018 04.13