Common Citrix StoreFront errors and how to avoid them in a Login VSI test
The first step in setting up Login VSI tests in a Citrix environment is to know which Login VSI Citrix connector to use. This is pretty simple. If you are using Citrix StoreFront, you will use SFConnect. If you have Citrix Web Interface, you will use CTXConnector.
This blog focuses on errors and troubleshooting issues relating to SFConnect and StoreFront setup. My other blog will discuss errors and troubleshoot using CTXConnector.
Citrix StoreFront is a versatile management tool to enable enterprise mobility, improve IT security and simplify XenDesktop deployments. For the many wonderful things Citrix StoreFront can do, you will find almost as many things that can be set up wrong for a Login VSI test. In this blog, I will go through a short summary of what occurs during a Login VSI test and how to avoid Citrix StoreFront setup problems.
As I mentioned, the connector that Login VSI uses for StoreFront is called SFConnect.exe. When a test is run, this connector boots off and connects directly to the API of StoreFront (your Storefront URL), creates a token for it, and inputs the test user credentials. After this, SFConnector then downloads the ICA and executes it on the Login VSI Launcher. The Citrix Receiver then takes over and makes a connection to the target machine, allowing the Login VSI test to boot off.
As you can see there are a number of things that can go wrong, such as the following:
1. The remote server returned an error: (404) Not Found
The first and most commonly seen issue is something like the picture above. Here, the main problem is that the URL is pulling up a “404 Not Found.” The reason for this is that the wrong StoreFront URL was used. There are actually two different Storefront URLs available: 1. the one set up specifically for StoreFront, and 2. the user interface. The two cannot be interchanged, and trying to add in the user interface URL (the one specifically with “web” at the end), will yield the 404 message. Did you get an error message like this in the Launcher? If so, remove the word “web” from the URL and try again.
You can test to see which is the web interface URL and which is the Storefront URL by manually going to each URL. The one that brings up a “403” error is the one you will want to put in the Login VSI Management Console command line.
2. Error getting authentication token for resources
This is the next most common type of error I see. An error like this one can be attributed to many things, the most common being the credentials added in were incorrect. A commonly overlooked credentials issue is the domain is not predefined. (To get around this, you would need to define the domain as something like “domain\LoginVSI1”). Another issue is the URL, which is case sensitive. You will get an error if you try to use “https:\\StoreFront.com\example” whereas your StoreFront is “https:\\StoreFront.com\Example”. The same case sensitivity goes for the Delivery Group name! As you can see, it is very easy to mess up something in this section but easy enough to get set straight.
The best way to check to see if the information is correct is to manually open up the web interface and use the same credentials as the Login VSI management console to sign in. If it fails, check your AD test group and re-enter the information. At the same time, you can check the URL and the Delivery Group name. What you see, the launcher sees as well.
Update March 16, 2016: This error can also be caused by the "trusted domains” setting.
3. No published resources found
This one is simple. The Login VSI Active Directory test group has not been given access to the Delivery Group in StoreFront. So you would just make sure to give the test group access within StoreFront.
4. ICA content status “Failure”, failed to get ICA file content
In this case, the ICA files aren’t getting transferred from StoreFront to the SFCconnect.exe. Check your credentials and your URL. Can you actually connect to the Desktop Pool that you want? Follow the similar steps from step #2 above.
A common reason for failure to get ica content are unavailable desktops. Either because there aren't enough desktops in a pool or because a desktop is unregistered. Make sure that you have enough desktops available before you begin a test.
5. Trying to run StoreFront with NetScaler?
Please read this blog from Citrix. They provide a script on how to run StoreFront with NetScaler.
As you can see by the summary of errors above, the best way to avoid common Citrix StoreFront problems during a Login VSI test is to make sure that you enter the right StoreFont connect information in the Login VSI Management Console. I hope that this blog helped you to run a successful Login VSI test with StoreFront, but if you aren’t able to solve your Citrix StoreFront errors, you can always send an email to firstname.lastname@example.org.