When external users attempt to access a Receiver for Web store through NetScaler, the following
error message is displayed:
Cannot complete your request.
You can log on and try again, or contact your help desk for assistance.
What is a possible cause of this error?
A.
The user licenses on the NetScaler have expired.
B.
The SSL certificate on the NetScaler has expired.
C.
The StoreFront server CANNOT resolve the callback FQDN.
D.
The Secure Ticket Authority has been configured incorrectly on the StoreFront server.
Explanation:
The following are the different issues causing this error and their solutions.
Notes:
If you see “Cannot complete your request”, it is possible that the StoreFront URL might be different from the certificate bound in IIS. When you make a certificate match the StoreFront URL and bind it, you will be able to log into StoreFront.
It has been reported that using Microsoft “NLB” type load balancing with unicast mode. Switching to multicast mode may help resolve.
It has also been reported when SQL mirroring was enabled on the XenDesktop database.
http://support.citrix.com/article/CTX133904
0
0
Awnser C seems to be right
http://support.citrix.com/article/CTX133904
Issue – 7
If the callback URL configured on StoreFront is wrong.
Note: The behavior can be caused by the callback URL resolves to the wrong IP or the entered FQDN does not match the certificate installed on Access gateway Enterprise Edition.
0
0
Option C is correct:
http://support.citrix.com/article/CTX133904
Error: “Cannot complete your request” in StoreFront
—
Issue – 2
The StoreFront server cannot resolve the StoreFront FQDN.
User-added image
Solution – 2
In a multi-server deployment, the StoreFront server must resolve the configured StoreFront URL (Server Base URL) to the Load Balancer VIP. For more information on how to configure a Load Balance VIP on a NetScaler for StoreFront multi-server groups, see CTX133185 – Citrix StoreFront – Implementation Guide.
In a single-server deployment, the Server Base URL must resolve to the StoreFront’s server local IP address.
0
0
C is fine.
I actually came across this issue once.
0
0
C
0
0
I agree with the answer. C
0
0