Wednesday, October 3, 2012

Unable to launch XenApp 6.5 applications through an Access Gateway with event ID 30003 followed by 30205 logged on Citrix Web Interface Server

Problem

You’ve been receiving reports that users are unable to launch XenApp 6.5 applications through an Access Gateway from the web interface or Citrix Receiver and reviewing the logs on the Web Interface server shows that errors with the event ID 30003 followed by 30205 are logged:

Event ID 30003

Site path: C:\inetpub\wwwroot\Citrix\PNAgentExternal.

An error occurred while attempting to connect to the server bda-ham-xa1.someDomain.local on port 80. Verify that the Citrix XML Service is running and is using the correct port. If the XML Service is configured to share ports with Microsoft Internet Information Services (IIS), verify that IIS is running. This message was reported from the XML Service at address . The specified Secure Ticket Authority could not be contacted and has been temporarily removed from the list of active services. [Unique Log ID: b8648df5]

For specific information about this message, see the Web Interface documentation at http://support.citrix.com/proddocs/topic/web-interface-impington/wi-log-messages-event-ids-hardwick.html.

image

image

Event ID 30205

Site path: C:\inetpub\wwwroot\Citrix\PNAgentExternal.

All the configured Secure Ticket Authorities failed to respond to this XML transaction. [Unique Log ID: bfabad68]

For specific information about this message, see the Web Interface documentation at http://support.citrix.com/proddocs/topic/web-interface-impington/wi-log-messages-event-ids-hardwick.html.

image

Solution

The errors logged above usually point to an incorrect port number configured for the Secure Ticket Authority (STA) URL.  Note how the screenshot below has the URL:

http://servername.domain.local/scripts/ctxsta.dll

image

The STA in this environment actually has port 8080 configured and therefore the URL should be:

http://servername.domain.local:8080/scripts/ctxsta.dll

image

The error should go away once the STA URL has been corrected.

1 comment:

Anonymous said...

Thank you very much, this has saved me a lot of trouble. A lot of other articles have mentioned moving the XML service to port 8080 to resolve this issue, but as it was already using port 8080...
I knew it wouls be a simple fix