STA Server Binding Fails with ctxsta.dll Path

book

Article ID: CTX696395

calendar_today

Updated On:

Description

In the current build, STA server binding does not handle the explicit "ctxsta.dll" path correctly during configuration processing.

Applicability: 

  • NetScaler builds 14.1-66.54 and 14.1-66.59 only
  • Applies to both global STA binding and VPN vserver STA binding.

Cause

The STA server configuration fails when either of the following commands is used:

(1) bind vpn vserver <vserver name> -staServer https://<staserverfqdn/ip>/scripts/ctxsta.dll

image.png

[or]

(2) bind vpn global -staServer https://<staserverfqdn/ip>/scripts/ctxsta.dll

image.png

Resolution

As a workaround, bind only the STA server using the FQDN or the IP address without the /scripts/ctxsta.dll path.

Use the following format:

(1) bind vpn vserver <vserver name> -staServer https://<staserverfqdn/ip>

image.png

[or]

(2) bind vpn global -staServer https://<staserverfqdn/ip>

 

image.png

 

Issue/Introduction

A known issue exists in the build 14.1 66.54 and 14.1 66.59, where STA server binding fails if the STA server is configured with the full ctxsta.dll path.

Example of the configuration that fails:  

  • bind vpn vserver vpnvserver -staServer https://example.com/scripts/ctxsta.dll

Additional Information

Scope of Workaround:

  • This workaround applies only when the intended STA endpoint is the default scripts/ctxsta.dll
Powered by Wolken Software