Jump to content
Welcome to our new Citrix community!

Failed to Fetch StorePath from StoreFront FQDN


peizhi yu

Recommended Posts

Actually, you don't have to wait. If the retrieve stores fails, it gives you a text field to manually specify the store path that you need/want to use instead of pre-configured drop-down list.

If you know the storefront path you plan to use you can configure it manually OR use a placeholder value and update it after the fact.  But you would have to remember this value is not right at this point.

 

Or you can build a session policy manually without using the wizard at all.

 

If you don't have storefront built yet and don't want the gateway deployed without the storefront in place, then you can wait.

 

But in general, you should know your intended storefront fqdn, single sign on domain, store path, and STA list you would want to use prior to running the wizard or building a policy. If you know the values, but they don't exist yet, you can configure them manually and they will be in a DOWN state until they resolve.  If these values aren't known yet and you don't want to use placeholders that will have to be updated later, then you should wait on the config.

  • Like 1
Link to comment
Share on other sites

On 1/18/2020 at 4:37 AM, Rhonda Rowland1709152125 said:

Actually, you don't have to wait. If the retrieve stores fails, it gives you a text field to manually specify the store path that you need/want to use instead of pre-configured drop-down list.

If you know the storefront path you plan to use you can configure it manually OR use a placeholder value and update it after the fact.  But you would have to remember this value is not right at this point.

 

Or you can build a session policy manually without using the wizard at all.

 

If you don't have storefront built yet and don't want the gateway deployed without the storefront in place, then you can wait.

 

But in general, you should know your intended storefront fqdn, single sign on domain, store path, and STA list you would want to use prior to running the wizard or building a policy. If you know the values, but they don't exist yet, you can configure them manually and they will be in a DOWN state until they resolve.  If these values aren't known yet and you don't want to use placeholders that will have to be updated later, then you should wait on the config.

I hava storefront and that is working.

I can using the storefornt connection to virtual desktop.

I cannnot find it on web admin page, but I can find it on shell of netscaler.

Link to comment
Share on other sites

On 1/16/2020 at 3:02 AM, peizhi yu said:

But, I can ping it in shell of netscaler cateway.

 

Ok, if the issue is that your ADC can't reach your storefront, but you can from shell...there may be some other considerations.

 

Now, are you pinging a storefront VIP (load balanced on this ADC) or are you pinging a specific storefront address from the ADC (like stf1 and stf2).  The other thing to remember, if this is the storefront lb vip, ADC by default always responds to pings VIPS regardless of the up/down state of the vserver using the vips (Unless the behavior is modified). So a ping may work, but the vserver is down for some reason.

 

Also, pinging from shell OR cli sources from the NSIP by default. Use the ping -S <source ip> <targetname> and specify the SNIP to use to reach the destination. This will allow you to test the SNIP to storefront communication and it may reveal if you have a firewall rule or acl or some other restriction preventing access. 

 

Then, if necessary, run a nstrace to look for communication failures between the ADC and storefront.

 

Finally, you can check nslog to see if gateway is having trouble resolving or reaching the specified storefront address (whether hosted on a vserver on this ADC or externally.)  Look to see if any events related to the <storefront fqdn> you've specified are being listed or not.

shell

cd /var/nslog

nsconmsg -K newnslog -d event

or

nsconmsg -K newnslog -d consmsg

 

 

 

Link to comment
Share on other sites

  • 10 months later...
  • 2 months later...
  • 7 months later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...