Link to home
Create AccountLog in
Avatar of jafrullahm

asked on

Xenapp 6.5 Server

I am getting the following error message ' An error occured while making the requested connection.'   when I try to launch any published application via web interface on one particular Xenapp 6.5 Servers.  

All other servers are alright.  All are upto date with HRP 01.  Logons are enabled on this server.  It has been rebooted but did not make any difference.  

Any idea what else to cheeck ? Nothing in the event logs on this server.
Avatar of hodgeyohn
Flag of United States of America image

1.  can you telnet to port 1494  to the server that is not working.
2.. if you go to the command line on one of your servers issue the command qfarm /load   please post the results..
Avatar of jafrullahm


I can telnet 1494 to the affected server from any other server and to any other server from this server.

The load on this server is 499 , Load Throttling load is 5000 ..... Logons enabled..  File attached. I have highlighed the affected sever with Red line..
check the application and system logs on the web interface server for sta, and xml errors.
Checked them but nothing specific to this server..
are there any STA, or XML errors on the web interface?
Check that the XTE and the IMA service are running.

Also do a qfarm /load from the command prompt and see if the server is showing a full load or not.

Let me know your results.
sorry didnt see that you already read did the qfarm..
Have you done the Qfarm /load repeatedly to monitor the load. If you are at a ltl load of 5000 plus your 499, if another login happens that throws the total load to 10499.

What lb policies do you have in place?
Telnet the server on port 1494 from the user machine and not from the server and check if the port is opened.
I can telnet 1494 from the user machine.

We only have one load balancing policy which is Office 2003 which is filtered for one AD group.
So, if user is a member of that AD group then he goes on to the servers in Office 2003 Worker Group and the rest of the users go to the server in Office 2010 WG.  The problem server is located in Office 2010 WG and the testing user is not in the 2003 AD group.
I have tested this server with the Load balancing for both options but still same error.

  Any more Ideas how to resolve this server.  I dont want to rebuild it if it can be resolved.
Have you tried publishing notepad to that server and seeing if it opens to figure out if it is a xenapp issue or an office 2010 issues?

ok, crazy suggestion but works for a lot of things..

on each of your xenapp servers

1.  stop the ima service
2.  run the command dsmaint recreatelhc
3.  restart the ima, and any services it stopped
4.  restart the Citrix xml service
5.  on your web interface server run the command iireset.

at this point I think something went south on our xml service, and the ima service is where it gets its info.
Its same even with Notepad.

Hodgeyohn,  I have stopped IMA, recreated LHC and started the service but it did not make any difference. Restarted citrix xml service as well...
To be honest I am not sure if I want to do IISreset on production webinterface servers.
It did not affect any other servers at all.
Any other ideas ?
please run a qfarm /load and post the results...
Done it already, please see my initial comments....
I have looked again properly on the Web interface event viewer and this is the event id in application log

event id 30107

description: Site path: C:\inetpub\wwwroot\Citrix\External.

The Citrix servers reported that they are too busy to provide access to the selected resource. This message was reported from the XML Service at address [com.citrix.xml.NFuseProtocol.RequestAddress].  [Unique Log ID: a145d4a]
Any more ideas ?
it is either an ima issue, (recreatelhc usually take care of this), or it is a license issue.
check both the xenapp server and the license server for any errors.
Avatar of jafrullahm

Link to home
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
It is resolved after enabling the connection.