nick d Posted March 14, 2016 Share Posted March 14, 2016 I keep getting this error message when trying to setup Receiver 4.4 to connect to Netscaler 11 with storefront. Everything works fine using a browser. I have checked that the URL for the store is not reachable from outside as well as the callback URL is correct. Beacons are also correct with Internal not reachable from outside. Any help would be appreciated. I have attached the receiver log file. Thanks, Nick receiverlog.txt Link to comment Share on other sites More sharing options...
CarlStalhood Posted March 14, 2016 Share Posted March 14, 2016 Windows 7? Is TLS 1.0 disabled on the NetScaler? 1 Link to comment Share on other sites More sharing options...
Priya Salwan Posted March 18, 2016 Share Posted March 18, 2016 Hi Carl, Same issue We have TLsv1 enable. Link to comment Share on other sites More sharing options...
nick d Posted March 18, 2016 Author Share Posted March 18, 2016 I have TLSV1 enabled as well. Tried it with Windows 7 8 and 10 same issue. Link to comment Share on other sites More sharing options...
nick d Posted March 19, 2016 Author Share Posted March 19, 2016 If I login to the receiver for web and click on activate, it adds the account to Receiver 4.4. However trying to add it by typing the URL results in the protocol error message. Link to comment Share on other sites More sharing options...
nick d Posted March 22, 2016 Author Share Posted March 22, 2016 No one has any suggestions? It's probably something minor that I missed but can't seem to pinpoint it. Priya did you solve your problem. If so can you let me know how? Link to comment Share on other sites More sharing options...
nick d Posted March 23, 2016 Author Share Posted March 23, 2016 I tried from internal bypassing the Netscaler and going directly to the storefront and I get the same error. So this is definitely a storefront issue. I am using Storefront 3.5. Link to comment Share on other sites More sharing options...
nick d Posted March 29, 2016 Author Share Posted March 29, 2016 Creating a provisioning file from the storefront works internal and through the Netscaler. Only typing the URL in receiver does not work. Anyone have any ideas? Link to comment Share on other sites More sharing options...
nick d Posted March 30, 2016 Author Share Posted March 30, 2016 So I enabled Authentication logging on the client. It is getting an unexpected server response was received Status='404'. It is trying to connect to https://storeurl/Citrix/Authentication/Auth/V1/token. Trying to browse to this also results in a 404 page not found. Looking at my storefront server toke validation service URL, it is listed as https://storeurl/Citrix/storenameauth/auth/V1/token/validate. These are obviously different. I have tried creating a new store and the same thing happens. The Token Validation Service is always created with storenameAuth/Auth/V1/Token/Validate. For some reason the client is being given the incorrect URL. Anyone know how I can change this? Nick 1 Link to comment Share on other sites More sharing options...
Larry Heier Posted April 8, 2016 Share Posted April 8, 2016 Hello, We are seeing the exact same issue with NetScaler 11 and StoreFront 3.5 as Nick documented in this thread. The activation .cr file works fine but you got receive the protocol error when typing in the FQDN into Citrix Receiver. Is this a bug? thanks, Larry Link to comment Share on other sites More sharing options...
nick d Posted April 8, 2016 Author Share Posted April 8, 2016 I have opened a case with Citrix support. So far they have determined that this is a Netscaler issue and not StoreFront as I previously thought. Waiting to hear back from them today. So far they have been unable to duplicate the issue in their environment. Nick Link to comment Share on other sites More sharing options...
Larry Heier Posted April 8, 2016 Share Posted April 8, 2016 We're trying to get single sign on working and its affecting this setup too. So weird that the .cr file works fine but typing in the fqdn (which is probably how SSON works and part of setup with GPO) doesn't work. thanks for logging the call. So if it helps you, you can share I have the latest netscaler 11.65 release and storefront 3.5 with xenapp 7.8 I see others with this problem from time to time too in the forums. This is a new install. Larry Link to comment Share on other sites More sharing options...
Forrest Blair Posted April 10, 2016 Share Posted April 10, 2016 Exact same issue here also. Anyone find a solution? Link to comment Share on other sites More sharing options...
nick d Posted April 10, 2016 Author Share Posted April 10, 2016 So far Citrix support has not been able to figure it out. They want to recreate my Netscaler virtual server from scratch without using the wizard. They think that the wizard may have some kind of bug that is causing this. I will let you know if this fixes it. Nick Link to comment Share on other sites More sharing options...
Larry Heier Posted April 11, 2016 Share Posted April 11, 2016 Hello, We built out our virtual server WITHOUT the wizard and have the same issue at a couple installs so I don't think the wizard has anything to do with it Nick. Feel free to have Citrix reach out to me to look at my install to gather any information on this issue. LHeier@decisvieitsolutions.com or I can open up my own ticket on this issue and try to link it to your case #. Let me know offline if you want. Larry Link to comment Share on other sites More sharing options...
nick d Posted April 11, 2016 Author Share Posted April 11, 2016 I just got off the phone with them. That did not fix the problem. They now think it is a storefront issue and are escalating the case. Link to comment Share on other sites More sharing options...
Larry Heier Posted April 12, 2016 Share Posted April 12, 2016 Are issues are occurring on StoreFront 3.5 and 3.1. It sounds like a StoreFront issue. Let me know if any info from my end will help determine the root cause for us and others. thanks, Larry Link to comment Share on other sites More sharing options...
nick d Posted April 12, 2016 Author Share Posted April 12, 2016 Hi Larry, What is the token validation service URL on your Storefront 3.5 and Storefront 3.1 stores? Is it https://baseurl/citrix/authentication/ or https://baseurl/citrix/storenameauth/ My 2.6 store that works fine has https://baseurl/citrix/authentication while the 3.5 is the other way and does not work. Link to comment Share on other sites More sharing options...
Larry Heier Posted April 13, 2016 Share Posted April 13, 2016 Mine's the same setup as you Nick. But interestingly IOS Mobile receiver also doesn't work with FQDN and we get a "Could not add account". This seems like a similar issue and people say its a Mobile receiver issue fixed in 6.1.5 but I think these are related..read more here: http://discussions.citrix.com/topic/376233-cannot-add-account/ Link to comment Share on other sites More sharing options...
nick d Posted April 13, 2016 Author Share Posted April 13, 2016 I have figured out what the problem is. (No thanks to Citrix support). Its a bug. Just waiting to get a fix from them. The issue is that if you delete the default store that is created when you install Storefront, it breaks authentication. If you edit the default store or leave it as is and add your own store, everything works fine. Once you delete the default store, Authentication is broken. You can fix this by uninstalling Storefront and reinstalling it but I want a fix as I have already customized this store. I figured this out by installing a new Storefront server that worked fine until I deleted that default store called "Store Service" Nick 3 Link to comment Share on other sites More sharing options...
Larry Heier Posted April 13, 2016 Share Posted April 13, 2016 Nick, That makes complete sense and we thought it had something to do with a fresh install. The places where its working are on Storefronts that were upgraded from V2.x (think the issue exists on 3.0x too in some fashion). We deleted the default store on the earlier version then upgraded. These two cases where we have issues it was a new install of Storefront 3.5. When did Citrix say a new StoreFront release or bug fix would be released?? thanks again, Larry Link to comment Share on other sites More sharing options...
nick d Posted April 15, 2016 Author Share Posted April 15, 2016 They have no current fix for this issue. Only fix is to uninstall Storefront and then reinstall and reconfigure. I have already done this and it resolves the problem. Link to comment Share on other sites More sharing options...
Larry Heier Posted April 15, 2016 Share Posted April 15, 2016 Nick, Here's what we learned leveraging your earlier advice. Remove StoreFront from add/remove programs on new installs of XenApp 7.8 that install StoreFront automatically on the packaged install. Then install StoreFront 3.5 manually and you can create your own store cleanly in that manner. The issue seems to be caused by the automatic Storefront install and configure via the XenApp 7.8 media. -Larry 1 Link to comment Share on other sites More sharing options...
Greg Steer1709154185 Posted May 26, 2016 Share Posted May 26, 2016 Hi, Has there been update to this issue?, We have run into this problem and would prefer not to have to uninstall\reinstall Storefront. The servers aren't in production yet so can wait for a fix if its coming soon. ThanksGreg Link to comment Share on other sites More sharing options...
Larry Heier Posted May 26, 2016 Share Posted May 26, 2016 Not that I know. As you're not in production I'd simply uninstall and reinstall. Storefront 3.6 should be out fairly soon and maybe that will resolve this issue if anyone else creates this issue with the deletion of the default site. Larry Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now