XenApp 6 Applications not showing up in Web Interface or PNA
Greetings all,
Last night, a team member and I reconfigured our XenApp 4.5 and XenApp 6.0 servers to migrate from an existing VLAN to a new one. Now that the IP's have been configured and DNS has been verified as updated, all my XenApp 4.5 applications show up and are functional, while all of my XenApp 6 applications do not show up in WI, or in Online Plugin.
On the WI Management console (during the initial change), I had also reconfigured the FARM IP addresses for both Web and Services sites to reflect the new IP's for each respective farm. I also went with FQDN instead of IP for Farm config on WI Management console, but still no dice.
IMA, MFCOM are started, QFARM result shows correct IPs for all XenApp 6 Farm servers, VERIFYLHC returns successfull verification, event viewer doesn't seem to have anything pertinent... i'm running out of options.
So, if the connection to the database server (which is SQL 2005 - and houses both Farm databases) has been verified (qfarm, IMA etc), then it seems there is a step i'm missing in XenApp 6 that isn't required in 4.5, but I haven't found it yet.
Servers are all 2008 R2 STD with all updates.
Someone! Anyone! Please Respond! <RIP Gunny Sgt.>
Thanks - Mike
Last night, a team member and I reconfigured our XenApp 4.5 and XenApp 6.0 servers to migrate from an existing VLAN to a new one. Now that the IP's have been configured and DNS has been verified as updated, all my XenApp 4.5 applications show up and are functional, while all of my XenApp 6 applications do not show up in WI, or in Online Plugin.
On the WI Management console (during the initial change), I had also reconfigured the FARM IP addresses for both Web and Services sites to reflect the new IP's for each respective farm. I also went with FQDN instead of IP for Farm config on WI Management console, but still no dice.
IMA, MFCOM are started, QFARM result shows correct IPs for all XenApp 6 Farm servers, VERIFYLHC returns successfull verification, event viewer doesn't seem to have anything pertinent... i'm running out of options.
So, if the connection to the database server (which is SQL 2005 - and houses both Farm databases) has been verified (qfarm, IMA etc), then it seems there is a step i'm missing in XenApp 6 that isn't required in 4.5, but I haven't found it yet.
Servers are all 2008 R2 STD with all updates.
Someone! Anyone! Please Respond! <RIP Gunny Sgt.>
Thanks - Mike
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
basraj
http://www.brianmadden.com/forums/t/36325.aspx
ASKER
The issue is resolved, but now i'm not sure how this was ever an issue. The change that made it happen was your 1st comment. A cursory check in WI Farm config showed me i missed one of my XenApp servers that was apparently my XML broker. Once added, we were good to go.
What frustrates me about this is I thought that whatever server you add in the WI Farm configuration could be used as an XML broker for said Farm. While all the rest of the servers were in the WI config for their Farm, shouldn't any of them been able to be used by WI as an XML broker for their Farm? I mean, isn't that the point of listing more than one... so that if one goes down, you still have an XML broker telling WI what applications are available and from where?
I'll be giving this much review. We should keep the discussion going even though I'm going to award points.
What frustrates me about this is I thought that whatever server you add in the WI Farm configuration could be used as an XML broker for said Farm. While all the rest of the servers were in the WI config for their Farm, shouldn't any of them been able to be used by WI as an XML broker for their Farm? I mean, isn't that the point of listing more than one... so that if one goes down, you still have an XML broker telling WI what applications are available and from where?
I'll be giving this much review. We should keep the discussion going even though I'm going to award points.
ASKER
Good job. You helped me focus on the right component of the issue. Thanks again.
xml broker service nothing but server has xml service running. when you add xml servers in WI, u can give 2-3 xml servers for load balancing. Like if u select the farm name, u get option to add xml servers, where u can add many. If the first xml server is down, it will go to the second one and so on.
ASKER
That's exactly my point... I had 3 other xenapp servers listed as xml brokers - so why would the absence of this ONE server cause a failure? I didn't add the server earlier because I thought i had xml brokers covered. Makes me want to take a closer look into the xml configs of the 3 servers that were there all along. If they are still no good for xml brokers, then my redundancy is broken...