Error: "[published_app_name] failed to start. The Citrix server is unable to process your request to

Citrix states in their article: CTX996187

CTX996187 - Error: "[published_app_name] failed to start. The Citrix server is unable to process your request to start this published application at this time. Please try again later. If the problem persists, contact your administrator." when Connecting to a Published Application

This document was published at: http://support.citrix.com/kb/entry.jspa?externalID=CTX996187

Document ID: CTX996187, Created on: Jun 6, 2001, Updated: Jul 15, 2003

Products: Citrix MetaFrame XP 1.0 for Microsoft Windows 2000, Citrix MetaFrame XP 1.0 for Microsoft NT 4.0 Server Terminal Server Edition, Citrix MetaFrame 1.8 for Microsoft Windows 2000

Follow instructions below.
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Make sure you back up the registry before you edit it. If you are running Windows NT, also update your Emergency Repair Disk (ERD).

When trying to connect to a published application, the published application will not launch. If you check the active processes in the Task Manager of the server, you will see Icast.exe as one of the active processes. Two minutes after launching the published application, the following error message may appear:

"[published_app_name] failed to start. The Citrix server is unable to process your request to start this published application at this time. Please try again later. If the problem persists, contact your administrator."

If you try to connect to the desktop (instead of the published application ), Wfshell.exe is not one of the active processes, so the session could lose device mapping settings; for example, clipboard mapping or sound mapping.

The problem may be that the registry entry for Cmstart.exe is missing or corrupt. To correct this problem, run Regedt32.exe and go to

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogon

AppSetup:Type = REG_SZ:

Data = USRLOGON.CMD,CMSTART.EXE

These values are the default values for the AppSetup entry. If Cmstart.exe is missing, add it manually and attempt to reconnect to the published application.

NOTE: Icast.exe (application launcher) waits for Wfshell.exe to complete before launching the initial program for the published application. If Cmstart.exe is not listed under AppSetup value, Wfshell.exe is not launched and Icast.exe will timeout (after two minutes by default), generating the error message mentioned above.



Primary links

Custom Search

Who's new

  • Cachleferah
  • Weedbacuupe
  • vororourn
  • vDonellaCandrah
  • SnnaSusi

Who's online

There are currently 0 users and 6 guests online.

KrissysCorner.com RuthSwensonLaw.com CreativeLizardProductions.com

DISCLAIMER:

None of this has anything to do with us, someone else is responsible for the entire thing, and we have no idea who or why. We do not know anything about it. It may be alien life forms for all we know: we haven't a clue. You cannot blame us for anything that may result from your visit. That was entirely your own personal choice, made by you of your own volition, and without our knowledge. We do not, after all, have any control over you and cannot by any stretch of the imagination be expected to accept or acknowledge, be it legally or morally, any accountability for decisions made by you on an independent basis, utilizing your own free will, and without our intervention. We are therefore in no way, shape, or form answerable to anyone for any consequences arising from the aforementioned or indeed any other actions, similar or otherwise, because it was not us that did, or did not do anything. It is not even remotely our fault, and we are in no way prepared or willing to accept any liability, not even slightly, ever. We are, in fact completely and utterly blameless, in that it is definitely not our concern, and no blame can possibly be laid at our doorstep, even if we had one, the possession of which we hereby reserve as being entirely our own free choice. The onus is not on us at all, and furthermore, never has been. The entire matter is wholly beyond our control, and completely out of our hands, each of which are washed scrupulously clean of the whole business. We are not accountable for anything at all, and we hereby categorically deny all responsibility for all that has ever, or will ever happen. Our innocence is therefore wholly beyond doubt and absolutely unimpeachable, and so cannot, under even the remotest or unlikeliest circumstances, be brought into question. By clicking either on a link on this site, clicking on a link that leads to this site, or by arriving at this site by natural or supernatural means, you are in effect accepting responsibility for the fact that it is all entirely your own fault, down to the most miniscule detail, and that you are wholly accountable for whatever outcome may arise as a consequence of the aforementioned action or actions insofar as they were undertaken personally by you on an entirely voluntary basis and without any persuasion, coercion or influence from any party or parties other than yourself. Don't come sniveling to us, we are only figments of your imagination. I also agree that if I am ever with a contributor to this website during mealtimes I agree to pay for any super-sizing of their meal, or at least a nice dessert or one of those foo-foo drinks with an umbrella or a monkey. By admitting to have seen the worthless spineless drivel on this website (also known as content)

I Agree Wholeheartedly and Without Reservation to the above. (Except maybe for that part about the monkey.)

All Your Base Are Belong To Us.

Soylent Green Is People!

Never make a bet with a Sicilian when Death is on the Line!

No. Really, I do agree.