Tuesday, March 24, 2015

Hangs on Setclient?Wica

Issue : Site stuck on /cgi/setclient?wica and does not load further

Background:

I have just installed NS VPX and configured NetScaler Gateway site that should just automatically pass through to Storefront. What I get at the moment is that when I browse to the site  with a URL https://server.fqdn ( https://my.appdc.test.local) it redirects to https://server.fqdn/cgi/setclient?wica  (https://my.appdc.test.local/cgi/setclient?wica ) and it never goes anywhere further than that.









Resolution 2 :

Checked I am able to ping storefront fqdn from Netscaler.

Checked session policy











Checked policy AC_WB_192.168.1.123_S_

Found that Web Interface address its "https"
 












try to launch web site with above mention https url and got below mention error.





Change URL from "https" to "http"














It works fine after URL change.













Resolution 2:

Uncheck use HTTPS option from Enterprise tore settings.



Monday, March 23, 2015

Citrix XenApp 7.6 - Cannot communicate with database. Check that the database is running and that it is not being upgraded. Make sure you have permission to access the database.

Error :- Cannot communicate with database. Check that the database is running and that it is not being upgraded. Make sure you have permission to access the database.

While creating Site on XenApp 7.6 getting below mention error message.

Background :-  Running SQL express edition






















Resolution:

Put "SQL Server Browser"  service in "Automatic" state and start it!

Start creating site again, if you didn't get the option to recreate site then re-install Citrix Xenapp7.6 / XenDesktop 7.6

Note that this is generally only an issue if you're using SQL Express - with full blown SQL Server, the browser service is running by default.




Saturday, March 21, 2015

Http/1.1 Internal Server Error 29

Error :
Getting the error message “Http/1.1 Internal Server Error 29″ on a NetScaler page soon after authentication.

Resolution :

The issue will go away if you will replace the FQDN of the StoreFront server with the IP address of the SF server.

From










To