Forum Discussion

Jason_19901's avatar
Jason_19901
Icon for Nimbostratus rankNimbostratus
May 13, 2013

Citrix Health Check not correct

Version 11.3 no hot fix (VE) and I built XenApp through iApp. The health monitor keeps taking the application offline. When I remove the Health Check, XenApp works great.

 

 

here is my send string (sanitized):

 

POST /scripts/wpnbr.dll HTTP/1.1\r\nContent-Length: 601\r\nContent-Type: text/xml\r\nConnection: close\r\nHost: ctxwebp10\r\n\r\npermissionsallica30contentus3rnameABC123something.comXenApp_ADM_http_xmlb_monitor0.0.0.0\r\n\r\n

 

 

receive string:

 

Word 2010

 

 

thoughts?

 

citrix
partner

2 Replies

Sort By
  • Michael_Koyfma1's avatar
    Michael_Koyfma1
    Icon for Cirrus rankCirrus
    May 13, 2013

    You should run tcpdump(http://support.f5.com/kb/en-us/solutions/public/6000/500/sol6546.html) and capture the response from the XML broker to see what is being returned.

     

     

    Feel free to post sanitized info here or open a case with F5 support to troubleshoot in depth further.

     

  • Greg_Crosby_319's avatar
    Greg_Crosby_319
    Historic F5 Account
    May 14, 2013
    Is your monitor type appropriate, there is a certain case where the monitor type applied is incorrect when using the Citrix iApp. If your monitor type correctly matches the pool service, I would verify your host settings on your IIS server match up with your monitor host string. When using http service, if you leave the host name blank for the binding on your IIS app server, then the host string in your monitor does not matter. However, if you specify a host name in the bindings setting on your IIS server to a specific host name, then your monitor string has to match. Another item you can test is to leave the application field blank when filling out the iApp, doing so will leave the receive string blank for your XMl monitor. If your monitor shows an up status with a blank receive string, then you may have entered the wrong text for you published app - the monitor is case sensitive. Verify your xml monitor receive string is set as the display name of the application being monitored.