Tag Archives: Netscaler

Article: SSL 38 Error when Launching Applications via Citrix NetScaler

[NOTE: I recently ran into this issue and the webinterface.conf changes mentioned in this Citrix forum post solved my issue. I’m also re-posting a Citrix article that covers the same problem.]

SSL 38 Error is Displayed when Launching Applications

Document ID: CTX128812   /   Created On: Apr 26, 2011   /   Updated On: Aug 24, 2011
Average Rating: not yet rated


When trying to launch an application using ICA Proxy to XenApp via Access Gateway Enterprise the following error message is displayed:


Cause 1

This is possibly because of licensing restrictions as indicated in the article CTX119980 – SSL Error 38 when Launching Applications using Access Gateway Enterprise Edition

Cause 2

This issue can also be because of problems with Domain Name System (DNS) name resolution. When launching an application, the Access Gateway Enterprise Edition appliance uses the method specified in the WebInterface.conf file for name resolution. The Web Interface generates the ICA file. If the WebInterface.conf file is set to dns-port and DNS resolution is not possible, either because no DNS server is specified in the Access Gateway Enterprise configuration or the appliance being in a DMZ where no DNS server is reachable, then the launch of the application fails with the preceding error message.


Option 1

The first option to resolve this issue is to specify a DNS server in the Access Gateway Enterprise Edition appliance within the Name Servers pane as shown in the following screenshot:

Option 2

The second option is to edit the WebInterface.conf file on the Web Interface server for that site, to resolve through ipv4-port rather than dns-port. The default location of the WebInterface.conf file is C:\inetpub\wwwroot\Citrix\sitename\conf\. Replace the sitename with the name of your site; the default sitename for a Web site on Web Interface is /Citrix/Xenapp. The following screenshots are sample screenshots of the WebInterface.conf file:



Restart the IIS Web Server after saving the WebInterface.conf file.

This document applies to:


Article: How to Configure a NetScaler Appliance for EdgeSight for NetScaler

EdgeSight for NetScaler relies on HTML injections to gather user data. NetScaler 9.3 has a built-in wizard that you can run to configure it to work with EdgeSight for NetScaler. For previous versions of NetScaler, refer to the following CTX article:

CTX126862 – How to Configure a NetScaler Appliance for EdgeSight for NetScaler – Citrix Knowledge Center.


EdgeSight for NetScaler 2.1 Prerequisites

I’m finally getting around to installing the new EdgeSight for NetScaler version 2.1.  Here are the prerequisites you will need to get started.

NOTE: I’m installing this on a Windows 2008 64-bit server updated with August 2011 updates

From the documentation


  • CPU: 2GHz (or better)
  • Memory: 2GB of RAM recommended, 1GB of RAM required
  • Disk: 2GB free space


  • Windows Server 2008 or Windows Server 2003 SP1 or later. Both 32-bit and 64-bit systems are supported on all platforms
  • Internet Information Services (IIS) 7.0 for Windows Server 2008
  • Microsoft Message Queuing (MSMQ)
  • Microsoft Distributed Transaction Coordinator (MSDTC)
  • Microsoft XML Parser 3.0
  • Windows Script 5.6 or higher
  • .NET Framework 2.0 SP1
  • SQL Client Add-On Tools, including SQL-DMO objects.(if Web server and database server are on different machines)
Reported by the Installer
  • SQL Server Client Tools Requirement
  • Operating System Requirement
  • IIS Feature Requirement
    • Role Services
      • Static Content
      • Default Document
      • ASP.NET
      • ISAPI Extensions
      • ISAPI Filters
      • Windows Authentication
    • Ensure that the following Management Tools are selected under Role Services for the Web Server:
      • IIS 6 Management Compatibility
      • IIS 6 Metabase Compatibility
      • IIS 6 WMI Compatibility
      • IIS 6 Scripting Tools
      • IIS 6 Management Console
  • Microsoft .NET 2.0 SP1 Runtime Requirement
  • MSMQ Requirement
    • Add Features: Message Queuing -> Message Queuing Services
  • MSXML Requirement
  • Windows Script Host Requirement
After adding the above components…