Tuesday 15 March 2011

Citrix Web Interface errors: Some of your resources have not been reconnected…

We had an annoying message suddenly appear this morning for all web interface users on logging in and out.  When they logged in they were told “Some of your resources have not been reconnected.  Try reconnecting to your resources again and, if the problem persists, contact your system administrator”:

image

And when they logged out, they were told “Some of your resources have not been logged off.  Ensure you have shut down all your active resources.  If this message does not usually appear at the end of your sessions, contact your system administrator”

image

Turns out the users were quite willing to contact their system administrator as well!  Repeatedly.  I especially like the way the second message assumes you might just always see this message and that this would be okay.

A bit of Googling turned up that we would get rid of this be turning off Workspace Control.  This is in the Citrix Web Interface Management console – right click your websites, select Workspace Control and uncheck the first checkbox…

image

This removed the message – and also the Reconnect and Disconnect buttons.  Not the end of the world, but not the intention either. 

Then I noticed in the event log on the web interface box lots of Application errors of ID 31003 and 30015.  These had messages of…

  • All the Citrix XML Services configured for farm Test XenApp Farm failed to respond to this XML Service transaction.
  • The Citrix XML Service at address http://xensvr01:80/scripts/wpnbr.dll [com.citrix.xml.NFuseProtocol.RequestAppData] is not able to process requests

It was just a test farm with one server which was set up in the web interface, and I was installing updates on it and rebooting repeatedly.  Every time it was unavailable the website was giving the message to users logging in and out as a farm was offline – even though none of the users would be logging into that farm.  Once the work was completed the error stopped coming up.

A good lesson that when you ignore some errors they fix themselves!

2 comments:

Anonymous said...

Thanks, lead me right to my problem.

KyleB said...

I am having same issue, except it is only 2 people. A global change shouldn't be needed. Any thoughts ?

Post a Comment