We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you a podcast all about Citrix Workspace, moving to the cloud, and analytics & intelligence. Episode 2 coming soon!Listen Now

x

Netscaler/Storefront Configuration Issue with Secondary Store in StoreFront

Medium Priority
568 Views
Last Modified: 2020-02-14
Environment:        Netscaler in front of StoreFront 3.15 on Windows 2012.
Backend:              XenApp 7.15  (2 Delivery Controller & 2 XenApp Servers on Windows 2016, so 4 VM’s)

Summary: We are currently using the Netscaler/Storefront configuration to front-end our XenApp 6.5 Server farm and IS working properly.
We are setting up a NEW backend XenApp 7.15 farm to replace the existing 6.5 farm.  We will continue to use the same Netscaler’s & StoreFront Systems.  We will need to run parallel for a short time.

Recommendation:  It was recommended to just provision a second Store on the StoreFront systems to point to the new XenApp 7.15 servers – done.  Once tested, we just remove the old 6.5 store and wolla.  So, this is the direction we are trying to setup, but not working.  Explaining what is happening below:

In Netscalers, we have added the following under Netscaler Gateway for the 2nd Store:
1.      Configure NetScaler Gateway Session Policy
2.      NetScaler Gateway Session Policies and Profiles
3.      STA to the New Delivery Controller under VPN Virtual Server under Netscaler Gateway

Question: Do I need to setup a secondary Virtual Server with a new VIP on the Netscaler under Traffic Management, Load Balancing, Virtual server?  From the recommendation I have not done this.

The XenApp 6.5 Farm is using port 8080 to talk to it’s STA’s.  

Question:, we’ve tried both port 8080 and port 443 for the new Store to talk to the 7.15 Delivery Controller’s – doesn’t work and they can’t use the same port, so what is the recommend port for 7.15?
Error is the same both ways:

If I put in the URL for the second site, it gives me a prompt to detect Receiver.
  (Image 1)

You select Detect Receiver, and then it loops on this:
 (Image 2)

Logging – Not really finding my attempts.  The IIS Logs are the same with the repeating entries which flag success and failure.  Though not sure why this shows the 300 and 401 errors, but is the same in a fully functioning state.

2019-07-28 23:59:58 10.25.234.88 GET /Citrix/CitrixStore_cwsfctt/discovery - 443 - 10.25.x.x libwww-perl/6.05 - 200 0 0 4
2019-07-28 23:59:58 10.25.234.88 POST /Citrix/CitrixStore_cwsfcttAuth/auth/v1/token - 443 - 10.25.x.x libwww-perl/6.05 - 401 0 0 2
2019-07-28 23:59:58 10.25.234.88 POST /Citrix/CitrixStore_cwsfcttAuth/auth/v1/protocols - 443 - 10.25.x.x libwww-perl/6.05 - 300 0 0 6

In the Citrix Delivery Services Event Log, seeing discovery errors but not sure this correlates to my login attempts.
Failed to run discovery
Citrix.Web.DeliveryServicesProxy.ConfigLoader.DiscoveryServiceException, ReceiverWebConfigLoader, Version=3.15.0.0, Culture=neutral, PublicKeyToken=null
An error occurred while contacting the Discovery Service
   at Citrix.Web.DeliveryServicesProxy.ConfigLoader.Discovery.AppendConfigurationFromDiscoveryService(WebReceiverConfigSection section, DiscoveryClient client)
   at Citrix.Web.DeliveryServicesProxy.ConfigLoader.Discovery.RunDiscovery(WebReceiverConfigSection configSection, DiscoveryClient discoClient, EndpointsClient endpointsClient)
   at Citrix.Web.Proxy.Filters.DiscoveryComplete.OnAuthorization(AuthorizationContext filterContext)


Any help is appreciated as we need to move to the 2nd 7.15 Store.

Thanks in advance for your help and insight.
Image2.png
Image1.png
Comment
Watch Question

Sam JacobsCitrix Technology Professional / Director of TechDev Services, IPM
CERTIFIED EXPERT

Commented:
If you are operating the systems in parallel, then you need to set up a separate FQDN for the new environment on the NetScaler. If so, you need to create another NetScaler instance within your StoreFront configuration to point to the new FQDN.

Author

Commented:
Ok thanks, makes sense was just not sure.

As far as the ports from StoreFront to the Delivery controllers, looks like 443 and 80, or can I continue with port 8080?  

Thanks
Sam JacobsCitrix Technology Professional / Director of TechDev Services, IPM
CERTIFIED EXPERT

Commented:
You would use whatever port your Delivery Controllers are listening on.
So if they are listening on 8080, you would continue to use that.

Author

Commented:
Ok great, Thanks Sam.  Hope this is all we need to do :)
Sam JacobsCitrix Technology Professional / Director of TechDev Services, IPM
CERTIFIED EXPERT

Commented:
If you are still having issues, please post back.

Author

Commented:
Thanks - Looks like actually need 2 new IP's to setup the VIP as I need to define the Gateway address as well as another endpoint for StoreFront under the Traffic management/Virtual Server to be able to define the new server group to point to the new store.  Noting for anyone else looking for info.

Author

Commented:
Ok, I've split out the two store sites with separate IP's on the Netscaler.  One for the Netscaler Gateway, one for the StoreFront Virtual Server.

I am using the same port 8080, have that defined within StoreFront.  Checking the FW rules, but still hitting the loop when I try to launch the new URL to the XenApp 7.15 site.

I still am not seeing any useful logs either, how can I see if there is an error code being produced?  Or is everything reliant on a packet capture for troubleshooting?

Thanks in advance
Sam JacobsCitrix Technology Professional / Director of TechDev Services, IPM
CERTIFIED EXPERT

Commented:
Check the Citrix Delivery Services event log on the StoreFront server:
Citrix-Delivery-Services-Event-Log.jpg

Author

Commented:
Ok, thanks, looks like a certificate problem,

A CitrixAGBasic Login request has failed.
Citrix.DeliveryServicesClients.Authentication.AG.AGAuthenticatorException, Citrix.DeliveryServicesClients.Authentication, Version=3.15.0.0, Culture=neutral, PublicKeyToken=null
Authenticate encountered an exception.
   at Citrix.DeliveryServicesClients.Authentication.AG.AGAuthenticator.Authenticate(HttpRequestBase clientRequest, Boolean& passwordSupplied)
   at Citrix.Web.AuthControllers.Controllers.GatewayAuthController.Login()

System.Net.WebException, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
The remote server returned an error: (403) Forbidden.
Url: http://127.0.0.1:8080/Citrix/CitrixStore_cwsf7cttAuth/CitrixAGBasic/Authenticate
ExceptionStatus: ProtocolError
ResponseStatus: Forbidden
   at System.Net.HttpWebRequest.GetResponse()
   at Citrix.DeliveryServicesClients.Utilities.HttpHelpers.ReceiveResponse(HttpWebRequest req)
   at Citrix.DeliveryServicesClients.Authentication.TokenIssuingClient.RequestToken(String url, RequestToken requestToken, String primaryToken, String languages, CookieContainer cookieContainer, IEnumerable`1 acceptedResponseTypes, IDictionary`2 additionalHeaders)
   at Citrix.DeliveryServicesClients.Authentication.AG.AGAuthenticator.Authenticate(HttpRequestBase clientRequest, Boolean& passwordSupplied)



Thanks, I'll take a look in that direction.

Author

Commented:
Awe, thanks for the tip.  I changed the certificate in IIS on the StoreFront server to a wildcard cert instead of a named cert, that got me further, but same error.  So, will keep digging on the cert end.

Thanks
Sam JacobsCitrix Technology Professional / Director of TechDev Services, IPM
CERTIFIED EXPERT

Commented:
All on the StoreFront server:
Did you set up another NetScaler instance on StoreFront?
Are you using a callback? If so, can you browse to it without any warnings?
Did you add it under Configure Remote Access Settings?

Author

Commented:
Awe - found a potential issue.  I've defined port 8080 to continue to use that like the existing farm.  However; I noticed on the Netscaler's that when I define the Delivery Controllers under the STA and use port 8080 it fails.  It is likely failing because port 8080 is not listening on the new DC's.  So, in looking, it seems there is not actually an XML broker on the new DC's either.  So this seems to be a missing component.  

So there is either a piece I didn't install or the Delivery Controller's are not handling this function.
Sam JacobsCitrix Technology Professional / Director of TechDev Services, IPM
CERTIFIED EXPERT

Commented:
Try executing this from a PowerShell session on your Delivery Controller:
# Load the Citrix PowerShell module
Add-PSSnapin Citrix*
 
# Get DDCs and XD versions
get-brokercontroller | select DNSName, ControllerVersion

Open in new window

Author

Commented:
DNSName             ControllerVersion
-------             -----------------
ctxdctst1a.domain.local 7.15.3000.350
ctxdctst1b.domain.local 7.15.3000.350
Sam JacobsCitrix Technology Professional / Director of TechDev Services, IPM
CERTIFIED EXPERT

Commented:
The XML service should be running on your DDC's.
Try changing the XML port in StoreFront to 80.

Author

Commented:
Hmm... Ok, I changed the XML port to 80 for the new farm. Set on Storefront within the Delivery Controller area and under the Store Settings changed the http loopback to 80.   Updated the Netscaler STA's defined under the Netscaler Gateway Virtual Server.  Still get the same error "Cannot complete your request".  

Under Event log:

Failed to run discovery
Citrix.Web.DeliveryServicesProxy.ConfigLoader.DiscoveryServiceException, ReceiverWebConfigLoader, Version=3.15.0.0, Culture=neutral, PublicKeyToken=null
An error occurred while contacting the Discovery Service
   at Citrix.Web.DeliveryServicesProxy.ConfigLoader.Discovery.AppendConfigurationFromDiscoveryService(WebReceiverConfigSection section, DiscoveryClient client)
   at Citrix.Web.DeliveryServicesProxy.ConfigLoader.Discovery.RunDiscovery(WebReceiverConfigSection configSection, DiscoveryClient discoClient, EndpointsClient endpointsClient)
   at Citrix.Web.Proxy.Filters.DiscoveryComplete.OnAuthorization(AuthorizationContext filterContext)

System.Net.WebException, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Unable to connect to the remote server
Url: http://127.0.0.1/Citrix/CitrixStore_cwsf7ctt/discovery
ExceptionStatus: ConnectFailure
   at System.Net.HttpWebRequest.GetResponse()
   at Citrix.DeliveryServicesClients.Utilities.HttpHelpers.ReceiveResponse(HttpWebRequest req)
   at Citrix.DeliveryServicesClients.Discovery.RequestHandler.DiscoveryHttpRequestHandler.GetDocument(String url)
   at Citrix.Web.DeliveryServicesProxy.ConfigLoader.Discovery.AppendConfigurationFromDiscoveryService(WebReceiverConfigSection section, DiscoveryClient client)

System.Net.Sockets.SocketException, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
No connection could be made because the target machine actively refused it 127.0.0.1:80
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
Sam JacobsCitrix Technology Professional / Director of TechDev Services, IPM
CERTIFIED EXPERT

Commented:
Exactly where are you changing the loopback on StoreFront?
Sam JacobsCitrix Technology Professional / Director of TechDev Services, IPM
CERTIFIED EXPERT

Commented:
Ok ... that's a Web Receiver Setting.
Anyway, the error you are receiving looks like StoreFront is unable to connect to itself.
Can you browse via HTTPS to the StoreFront server's base URL?
StoreFront-Base-URL.jpg

Author

Commented:
Sam,

No, I am unable to reach the StoreFront URL's for the existing of new site.  I'll take a look there to see if something is getting blocked.

Thanks
Sam JacobsCitrix Technology Professional / Director of TechDev Services, IPM
CERTIFIED EXPERT

Commented:
It might be something as simple as needing to create an internal DNS entry.

Author

Commented:
DNS is already setup, but it is pointing to a VIP, I'll change to local and test that out tomorrow.  Thanks

Author

Commented:
I updated DNS with the local IP, but the behavior is the same.  I don't see anything getting logged on the Netscaler or StoreFront system other than in IIS which isn't logging anything more than the general events, 200, 401, 300.  Though in the Event logs, getting the same errors, still investigating, but here is what is getting logged.

Failed to run discovery
Citrix.Web.DeliveryServicesProxy.ConfigLoader.DiscoveryServiceException, ReceiverWebConfigLoader, Version=3.15.0.0, Culture=neutral, PublicKeyToken=null
An error occurred while contacting the Discovery Service
   at Citrix.Web.DeliveryServicesProxy.ConfigLoader.Discovery.AppendConfigurationFromDiscoveryService(WebReceiverConfigSection section, DiscoveryClient client)
   at Citrix.Web.DeliveryServicesProxy.ConfigLoader.Discovery.RunDiscovery(WebReceiverConfigSection configSection, DiscoveryClient discoClient, EndpointsClient endpointsClient)
   at Citrix.Web.Proxy.Filters.DiscoveryComplete.OnAuthorization(AuthorizationContext filterContext)

System.Net.WebException, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Unable to connect to the remote server
Url: http://127.0.0.1/Citrix/CitrixStore_cwsf7ctt/discovery
ExceptionStatus: ConnectFailure
   at System.Net.HttpWebRequest.GetResponse()
   at Citrix.DeliveryServicesClients.Utilities.HttpHelpers.ReceiveResponse(HttpWebRequest req)
   at Citrix.DeliveryServicesClients.Discovery.RequestHandler.DiscoveryHttpRequestHandler.GetDocument(String url)
   at Citrix.Web.DeliveryServicesProxy.ConfigLoader.Discovery.AppendConfigurationFromDiscoveryService(WebReceiverConfigSection section, DiscoveryClient client)

System.Net.Sockets.SocketException, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
No connection could be made because the target machine actively refused it 127.0.0.1:80
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
Sam JacobsCitrix Technology Professional / Director of TechDev Services, IPM
CERTIFIED EXPERT

Commented:
I noticed that the Store name immediately above has the number 7 in it ... is that correct?
http://127.0.0.1/Citrix/CitrixStore_cwsf7ctt/discovery

In the GET in your first post, the store name does not have the 7:
GET Citrix/CitrixStore_cwsfctt/discovery

You should be able to browse to the following location:
http://<StoreFront IP>/Citrix/CitrixStore_cwsfctt/discovery

... and it should attempt to download a .cr file from there.

Author

Commented:
Well, that is the second store.  So, I have the following in StoreFront:
StoreFront_Test_Stores.jpg
Sam JacobsCitrix Technology Professional / Director of TechDev Services, IPM
CERTIFIED EXPERT

Commented:
Okay, so you can get to:
https://<StoreFront IP>/Citrix/CitrixStore_cwsfcttWeb
but your cannot get to:
https://<StoreFront IP>/Citrix/CitrixStore_cwsf7cttWeb  ?

Author

Commented:
Correct, I've confirmed.

I can get here:      https://<StoreFront IP>/Citrix/CitrixStore_cwsfcttWeb

but I cannot get here:    https://<StoreFront IP>/Citrix/CitrixStore_cwsf7cttWeb  ?
Or I can get here, but immediate goes to the "Cannot Complete your Request".  And loops here.

I also wanted to let you know that they are using the same IIS Site, so the same IP.  We had this discussion previously and was determined we could handle the two sites within StoreFront and IIS did not need to be adjusted. This was recommended as this will run parallel while setting up and then the original site be scrapped and users will point to the 7.   Perhaps I missed a step here.  

Thanks
Sam JacobsCitrix Technology Professional / Director of TechDev Services, IPM
CERTIFIED EXPERT

Commented:
What authentication methods do you have checked for CitrixStore_cwsf7cttWeb (the website of the new store)?
StoreFront-Authentication-Methods.jpg

Author

Commented:
I have this for the new store
newstore.png
Sam JacobsCitrix Technology Professional / Director of TechDev Services, IPM
CERTIFIED EXPERT

Commented:
What about the authentication methods for the second store's website?
StoreFront-Website-Authentication-Me.jpg

Author

Commented:
Ok, I need to get back to this.  To answer your last question, yes that is my configuration:

The Second Store is set to use Username and Password, the underlying settings match the First Store
(Under Configure password Validation - I have this set to Validate passwords via Delivery Controllers.  The Delivery Controllers are the Delivery Controllers (Not XenApp ) systems.  These are using FQDN and port 8080.


The Second store is set to use Pass-through from Netscaler gateway with underlying settings math the First Store.
(Under Configure password validation - I have this set to Validate passwords via Delivery Controllers.  The Delivery Controllers are the Delivery Controllers (Not XenApp) systems.  These are using FQDN and port 8080.



I think I have to do a packet capture to see where this is failing.  It seems to be making the first authentication call to get past Netscaler to Storefront, however; once it hits StoreFront this is where this is erroring/looping.  

In the Event Logs I see:
(Event ID 4012) None of the Citrix XML Services configured for farm IowaCityTST7 are in the list of active services, so none were contacted.

(So think the Delivery Controllers aren't listening?)

(Event ID 2) Access is denied. Contact your system administrator.
com.citrix.wing.SourceUnavailableException, PublicAPI, Version=3.15.0.0, Culture=neutral, PublicKeyToken=null
No farms were contactable
   at com.citrix.wing.facadesupport.MultiFarmAuthModeInvoker.Invoke(IEnumerable`1 farms, AccessToken token)
   at Citrix.DeliveryServices.Authentication.XmlServiceAuthenticator.XmlServiceAuthenticator.Authenticate(UserInfo userInfo, Boolean obtainExpiryInformation)
   at Citrix.DeliveryServices.Authentication.Explicit.Core.ExplicitBL.Authenticate(String userName, String domain, String password)
   at Citrix.DeliveryServices.Authentication.CitrixAGBasic.Controllers.CitrixAGBasicController.AuthenticateWithPassword(String username, String domain, String password, AccessInfo accessInfo)
   at Citrix.DeliveryServices.Authentication.CitrixAGBasic.Controllers.CitrixAGBasicController.Authenticate()

com.citrix.wing.SourceUnavailableException, PublicAPI, Version=3.15.0.0, Culture=neutral, PublicKeyToken=null
All the Citrix XML Services configured for farm IowaCityTST7 failed to respond to this XML Service transaction.
   at com.citrix.wing.core.mpssourceimpl.MPSFarmFacade.HandleAllServicesFailed(Exception lastException, Boolean allLeasingFailures, Int32 servicesTriedCount)
   at com.citrix.wing.core.mpssourceimpl.MPSFarmFacade.CheckAccessTokenImpl(MPSAccessTokenChecker checker)
   at com.citrix.wing.facadesupport.MultiFarmAuthModeInvoker.Invoke(IEnumerable`1 farms, AccessToken token)


(Event ID 10)
A CitrixAGBasic Login request has failed.
Citrix.DeliveryServicesClients.Authentication.AG.AGAuthenticatorException, Citrix.DeliveryServicesClients.Authentication, Version=3.15.0.0, Culture=neutral, PublicKeyToken=null
Authenticate encountered an exception.
   at Citrix.DeliveryServicesClients.Authentication.AG.AGAuthenticator.Authenticate(HttpRequestBase clientRequest, Boolean& passwordSupplied)
   at Citrix.Web.AuthControllers.Controllers.GatewayAuthController.Login()

System.Net.WebException, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
The remote server returned an error: (403) Forbidden.
Url: http://127.0.0.1:8080/Citrix/CitrixStore_cwsf7cttAuth/CitrixAGBasic/Authenticate
ExceptionStatus: ProtocolError
ResponseStatus: Forbidden
   at System.Net.HttpWebRequest.GetResponse()
   at Citrix.DeliveryServicesClients.Utilities.HttpHelpers.ReceiveResponse(HttpWebRequest req)
   at Citrix.DeliveryServicesClients.Authentication.TokenIssuingClient.RequestToken(String url, RequestToken requestToken, String primaryToken, String languages, CookieContainer cookieContainer, IEnumerable`1 acceptedResponseTypes, IDictionary`2 additionalHeaders)
   at Citrix.DeliveryServicesClients.Authentication.AG.AGAuthenticator.Authenticate(HttpRequestBase clientRequest, Boolean& passwordSupplied)


These are the 3 events that continually fill the Citrix Delivery Services event log.

Thanks
Sam JacobsCitrix Technology Professional / Director of TechDev Services, IPM
CERTIFIED EXPERT

Commented:
1) Are you sure that the DDCs are using port 8080?
2) http://127.0.0.1:8080/Citrix/CitrixStore_cwsf7cttAuth/CitrixAGBasic/Authenticate is a callback to your StoreFront server. Why is your loopback port set to 8080? Is that what is set on your working website?

Even if the DDCs are listening on port 8080 (the default is 80), the loopback port (on the StoreFront server) should probably still be set to port 80.

Author

Commented:
Hello.  I've confirmed and have been able to validate changing the ports to be either port 80 or 8080 behavior is the same.  It really seems the issue is related to the STA.  I have read that this is by default part of the Delivery Controller.  So I try to enable verbose logging to see if tickets are being generated, but CtxSta.config doesn't exist on the Delivery Controller's or the VDA's (Checked just to ensure this).

So, I think if I figure out the STA piece we'll likely be in business here.  Running a packet capture with network folks tomorrow to ensure we aren't getting blocked somewhere in the transaction.

Any thoughts around the STA are appreciated.  Been looking at docs and it appears this communication/functionality is required and still exists in XenApp 7.15.

Thanks in advance for your wisdom and thoughts.

Author

Commented:
Sorry, after I looked at this again, think I already Found this, https://support.citrix.com/article/CTX224582?recommended, I guess that file ctxsta.config is no longer used.  

Found Scout so trying to find results.

Author

Commented:
I also tried this on a working Storefront system that doesn't have a secondary store defined and adjusted the path for it's config and http://127.0.0.1:8080/Citrix/CitrixStore_cwsf7cttAuth/CitrixAGBasic/Authenticate it is not able to reach this page either, I get a 404 if I try from a browser.

So from the behavior within the routing, issue seems to be the connection from StoreFront to the Delivery Controllers.  Hopefully the packet capture fills in some blanks here as using the tools on the DC aren't providing much to me at this point.  To be fair, just learning how to use them though.
Sam JacobsCitrix Technology Professional / Director of TechDev Services, IPM
CERTIFIED EXPERT

Commented:
I wouldn't think it's related to the STA ... they do not come into the picture until the user clicks on an application/desktop to launch.

Author

Commented:
yeah, doesn't seem like traffic is reaching the Delivery Controller from Storefront.  This is from the BrokerXML Services selected in the CDFControl tool.
Citrix_DeliveryController.jpg

Author

Commented:
Thanks Sam, that makes sense.  I just can't seem to get visibility into this looping.  Found some new tools in the process though ;)

Author

Commented:
Sam - Just thought I'd update here.  We ran the packet capture against the working instance (the original store) and the non-working instance (the new XenApp 7.15 store).  We are not blocking traffic.  However; we did note in the working versus non-working calls that the initial handshake is made to the XenApp DC's, however; the connection is then closed after the line Full request URI: http://ctxdctst1a.domain.local/scripts/wpnbr.dll.

In the working instance, there is a Continue and the call completes.

So, it seems we are either not passing something or something on the DC ?

Found this article, https://support.citrix.com/article/CTX227054, seems to be detailed to the level I need, but is for XenDesktop instead of XenApp.... so not sure if there is one for XenApp but still loking.

Thanks

Author

Commented:
Hello.  Been doing some experimenting.  I took another server that was not configured for Storefront and set it up as a StoreFront server specific to just the secondary store so the only site there.  I am using port 80 like I was on the StoreFront system I am trying to configure with an existing store.   In the Netscaler, I had to change the profile properties to use the new url for the secondary Storefront - so it matched exactly what was there, in other words the first part of the url was unique instead of shared like it is on my original StoreFront server.   This worked as expected with no errors, no "Cannot Complete your Request" message.  

So, my question comes in, now that I've verified the settings, I went back to Netscaler and pointed to my secondary site to the original server and machine, same error.  So is the second store truly supported in this manner, or is there some corruption of some kind on the server as Site #1 works as expected?

Progress, worst case scenario, I setup another set of StoreFront servers for the new Farm.  I guess I'm looking for some confirmation as I will need to obtain and provision new servers if this is the route I have to go. And I was able to see my apps..

Thanks in advance for any additional thoughts.
Sam JacobsCitrix Technology Professional / Director of TechDev Services, IPM
CERTIFIED EXPERT

Commented:
A second store is definitely supported ... I have a number of clients with multiple stores attached to the same NetScaler.

Author

Commented:
Hmm.. so I'm confused why this isn't working then.
Sam JacobsCitrix Technology Professional / Director of TechDev Services, IPM
CERTIFIED EXPERT

Commented:
Do you happen to have a Citrix Support Contract?

Author

Commented:
Yes, ticket? :)

Author

Commented:
I'll open a ticket as well, but maybe I just have a bad StoreFront server, I've read that the StoreFront can get corrupt pretty easy.  I'll do some more testing, but maybe I'll see if I can scarf up another box and redo the config like i need it with both sites.  Having this working one will help work through publishing apps, but I'll ultimately need to get the StoreFront side working.

Author

Commented:
Thanks for all your continued support Sam.  Appreciate your help.
Citrix Technology Professional / Director of TechDev Services, IPM
CERTIFIED EXPERT
Commented:
No problem ... I would tend to agree about the StoreFront corruption.
I've had to rebuild a few StoreFront servers over the years.
Now that you set up the other StoreFront server with the new store, can you add the first store to it as well and test that out?

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts

Author

Commented:
Yes I was thinking that too, I just want to tweak a couple of apps so they launch and then I'll do that to try to keep this moving forward.    At least I can see my new XenApp system is working for a couple of apps, just some tweaks to do for our custom apps.  My timeline is fast approaching as this was put off for a bit too long.

Author

Commented:
My issue was I was missing a secondary Netscaler Gateway for the secondary store in the StoreFront configuration.
Commented:
Closing and will re-open a new ticket once new findings come in if this resurfaces.  Thanks for your input.
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.