ErrorThe ticketing feature is disabled on one or more MetaFrame server

[yambag]

I have two citrix servers in my Xpa/Win2k Server/Nfuse17/CSG farm. Something happened one day this week where I can no longer open any applications published on one of the servers. I'm connecting through the web client. After successfully Logging into NFUSE, I click on the application I want to open that is only on the problem server, and the message center displays the following:

"The ticketing feature is disabled on one or more MetaFrame servers. Please make sure the Citrix XML service is running on all MetaFrame Servers in the farm and that all are listening on the same port number."

When trying to open the applications from the problem server using the PNA, I get the following error:

"Unable to launch applications. The remote server may be down the launch.asp file location maybe invalid, or the launch.asp file contains errors."

Opening applications published from the other Citrix server works fine.

Any assistance would be greatly appreciated,

Thank you,
Brian

 

[CitrixEngineer]

If this has suddenly come about where it was working before, it has the hallmarks of a corrupt LHC. Try running dsmaint recreatelhc and see if that fixes it.

Hope this helps

CitrixEngineer@yahoo.co.uk

 

[BeerGood]

As the STA service runs on port 80, if you are running it on the same server as one that's also running the XML service you need to make sure that XML is running on a different port as the default for that is *also* port 80. To change it you can modify it via the management console (right click on the server and check the properties) but the easiest is probably the command line option "CTXXMLSS /R[port]" eg drop to a command prompt and type "CTXXMLSS /R8081" to move the XML service to port 8081. Oh, of course you will need to stop/restart the XML service for this change to take effect.

If you have already done this, just check via the management console to make sure it's still running on the port you originally set it to - I've seen some servers change the XML service *back* to port 80 for some unknown reason......

Finally, if none of the above helps - check to make sure that nothing else has been installed onto the server that might be binding either to the port being used by STA or XML. Eg, some sort of server management utility. To do this, stop the XML/IIs/STA services and then from a command prompt type "netstat -a -n". If you see anything lurking/listening on port 80 and/or the port you are running XML on, then you have discovered the culprit!

Cheers