FAQ
Response 404 - UPNNotFound
It may not really be caused by UPNNotFound, but most caused by StoreFront™ authentication for various reasons:
- Communication error between Session Remote Start and StoreFront:
- Open
Web.config
, double confirm the StoreFrontServer option. A recommended practice is to set StoreFrontServer by copy from Receiver from Web Sites in StoreFront UI. Please note that the StoreFront store name is case-sensitive.
- Try to open StoreFrontServer by browser, check if there is a connection or certificate error. (Do not need to login, just check if the web page can be visited normally.)
- Open CDF trace tool or enable Session Remote Start log file, check if there is any error detail.
- StoreFront issue:
Open Event Viewer > Applications and Services Logs > Citrix Delivery Services to check StoreFront log
- FAS issue:
For step 2, the error may be related to FAS, please refer to the FAS section of the checklist above.
Request Timeout
- Session Remote Start has a RequestTimeoutSeconds option in
Web.config
. When request duration reaches the timeout, Session Remote Start will respond with status code 408 and body content.
- Session Remote Start will never terminate http connection without response. Please check if there is any timeout related setting in the caller.
- For the LaunchResource API, there is an optional parameter
WaitForLogonNotification
recognized as true
by default. For the VDAs really take a long time for launching, WaitForLogonNotification
can be set to false. API will respond immediately and execute the launching process in the backend.
Remain in ‘Connected’ State
If a session remains in the Connected state, there may be an authentication issue.
- Please review the FAS configuration and check the Session Remote Start logs.
- In the DaaS environment, please check if the Cloud Connector is working properly. Pay special attention to whether the firewall is configured correctly and does not block traffic from StoreFront.
Remain in ‘Active’ State
If a session remains in the Active state, the logon script configured in the Group Policy on AD may have failed to trigger the disconnect operation. Verify the Group Policy configuration, especially whether it has been successfully applied to the VDA.
Double Hop Scenario
SRS functions as expected in a double hop scenario without requiring any additional configuration.
However, if domain pass-through is enabled in the double hop setup, features like HTTP Basic Authentication should be avoided on the second hop, as they can cause unexpected behavior.
The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.
DIESER DIENST KANN ÜBERSETZUNGEN ENTHALTEN, DIE VON GOOGLE BEREITGESTELLT WERDEN. GOOGLE LEHNT JEDE AUSDRÜCKLICHE ODER STILLSCHWEIGENDE GEWÄHRLEISTUNG IN BEZUG AUF DIE ÜBERSETZUNGEN AB, EINSCHLIESSLICH JEGLICHER GEWÄHRLEISTUNG DER GENAUIGKEIT, ZUVERLÄSSIGKEIT UND JEGLICHER STILLSCHWEIGENDEN GEWÄHRLEISTUNG DER MARKTGÄNGIGKEIT, DER EIGNUNG FÜR EINEN BESTIMMTEN ZWECK UND DER NICHTVERLETZUNG VON RECHTEN DRITTER.
CE SERVICE PEUT CONTENIR DES TRADUCTIONS FOURNIES PAR GOOGLE. GOOGLE EXCLUT TOUTE GARANTIE RELATIVE AUX TRADUCTIONS, EXPRESSE OU IMPLICITE, Y COMPRIS TOUTE GARANTIE D'EXACTITUDE, DE FIABILITÉ ET TOUTE GARANTIE IMPLICITE DE QUALITÉ MARCHANDE, D'ADÉQUATION À UN USAGE PARTICULIER ET D'ABSENCE DE CONTREFAÇON.
ESTE SERVICIO PUEDE CONTENER TRADUCCIONES CON TECNOLOGÍA DE GOOGLE. GOOGLE RENUNCIA A TODAS LAS GARANTÍAS RELACIONADAS CON LAS TRADUCCIONES, TANTO IMPLÍCITAS COMO EXPLÍCITAS, INCLUIDAS LAS GARANTÍAS DE EXACTITUD, FIABILIDAD Y OTRAS GARANTÍAS IMPLÍCITAS DE COMERCIABILIDAD, IDONEIDAD PARA UN FIN EN PARTICULAR Y AUSENCIA DE INFRACCIÓN DE DERECHOS.
本服务可能包含由 Google 提供技术支持的翻译。Google 对这些翻译内容不做任何明示或暗示的保证,包括对准确性、可靠性的任何保证以及对适销性、特定用途的适用性和非侵权性的任何暗示保证。
このサービスには、Google が提供する翻訳が含まれている可能性があります。Google は翻訳について、明示的か黙示的かを問わず、精度と信頼性に関するあらゆる保証、および商品性、特定目的への適合性、第三者の権利を侵害しないことに関するあらゆる黙示的保証を含め、一切保証しません。
ESTE SERVIÇO PODE CONTER TRADUÇÕES FORNECIDAS PELO GOOGLE. O GOOGLE SE EXIME DE TODAS AS GARANTIAS RELACIONADAS COM AS TRADUÇÕES, EXPRESSAS OU IMPLÍCITAS, INCLUINDO QUALQUER GARANTIA DE PRECISÃO, CONFIABILIDADE E QUALQUER GARANTIA IMPLÍCITA DE COMERCIALIZAÇÃO, ADEQUAÇÃO A UM PROPÓSITO ESPECÍFICO E NÃO INFRAÇÃO.