Home > All, Citrix, CloudGateway, StoreFront > #Citrix #StoreFront Slowness, Join and Replication issue – check list!

#Citrix #StoreFront Slowness, Join and Replication issue – check list!

Ok, I guess that you may have seen issue with StoreFront before… and it you have not then good for U!

But in the case that you have experience it here are a couple of things that you can do and hopefully it solves your issue with slow StoreFront console startup, server join issues or replication issues. Sometimes I’ve seen that the join, replication and slowness is ok and the process goes through. But then all of a sudden you get an error and the propagation fails… and this can be because of a timeout in the StoreFront process that you’ve initiated.

I already assume that you’ve checked the basic stuff.. that the servers can reach each other (ping server name and FQDN etc. and that there are no FW issues)….

You may have an issue because you/your server cannot reach the Internet, and some of the components of the product is signed with SSL certificates and StoreFront will try to perform a check whether the publishers certificate is ok or not. So if your servers are behind a proxy serevr that you usually configure in your browser to be able to connect from your companies internal network to the Internet then you should do the following.

1. Log on to your first StoreFront server and create a copy of the original aspnet.config file under C:\Windows\Microsoft.NET\Framework\v2.0.50727 (verify which framework version that your app is using in IIS and modify that appropriate aspnet.config file, more info about this change can also be found here and is for Web Interface but is also applicable to StoreFront)

2. Open Notepad as an Admin (if you have UAC of course enabled) and open the asp net.config file

Citrix_StoreFront_aspnet_config_file

It will have the content as described by the picture above,  add this line to it:  <generatePublisherEvidence enabled=”false”/>

The file should not look something similar to this:

Citrix_StoreFront_aspnet_config_file_after_modification

3. Save the file

4. Perform an IISRESET

5. Perform step 1-4 on all your StoreFront servers

6. Ensure that you’ve closed the StoreFront console

7. Open Internet Explorer, go to: Internet Options and find the setting shown in the picture below and ensure that Check for publisher’s certificate revocation is UNCHECKED!

IE-Check-For-Publishers-Revocation

8. Start the StoreFront console on server 1 (it should be quicker now if you had the issue that the certificate couldn’t be checked)

9. (Thanks Mathew Allen for this tip) Turn on Socket Pooling for the store.  Per Citrix eDocs:  Socket pooling is disabled by default in stores. When socket pooling is enabled, Receiver Storefront maintains a pool of sockets, rather than creating a socket each time one is needed and returning it to the operating system when the connection is closed. Enabling socket pooling enhances performance, particularly for SSL connections. Socket pooling should not be used for stores that contain applications hosted on XenApp for UNIX.

To enable socket pooling, edit the store configuration file.

On the Receiver Storefront server, use a text editor to open the web.config file for the store, which is typically located in the C:\inetpub\wwwroot\Citrix\storename\ directory, where storename is the name specified for the store when it was created.

Locate the following element in the file.
<farmset … pooledSockets=”off” … >
Change the value of the pooledSockets attribute to on to enable socket pooling for the store.

10. Propagate your changes and it should now hopefully go through! 😉

//Richard

  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: