STA Server bind to a Citrix NetScaler Gateway cannot be used as a domain name based server for load balancing services

Marcel Meurer's picture

Error: A STA or WI DBS configuration exists. Unset it first

If you bind a specific server as STA to a Citrix NetScaler Gateway, you wont't be able to use the same host/fqdn name to create a "server“ at Traffic Management / Load balancing / Servers:

STA binding to NetScaler Gateway

Bind STA Server to NetScaler gateway

Create Domain Name Server

Create Domain Name based Server

 “A STA or WI DBS configuration exists. Unset it first”

Error: A STA or WI DBS configuration exists. Unset it first

You receive the following error: “A STA or WI DBS configuration exists. Unset it first”

In Citrix NetScaler Versions before 10.5 a workaround was possible if you first created the server for load balancing first and then added the STA server for your gateway (http://www.atumvirt.com/index.php/2013/08/a-sta-or-wi-dbs-configuration-exists-unset-it-first-error-when-adding-load-balancing-server/).

But attention: If you do this your STA bindings to your Citrix NetScaler Gateway will not be persistent! If you reboot your Citrix NetScaler, you will lose this STA binding as well as getting a problem with your connection to XenApp/XenDesktop.

With NetScaler version 10.5 a workaround is not possible (you cannot use one domain name for a "server" and a STA binding).

But what is the reason for this limitation? It’s not logical. Possibly there must be some internal reasons.

Comments
cbove@anetys.com
Each XenApp & XenDesktop STA have a unique identifier, STA must not be Load balanced, Netscaler need to be able to reach each STA directly. So I think this is Citrix trying to "help" you not load balancing the STA.
Marcel Meurer's picture
For sure. In my case I tried
For sure. In my case I tried to load balance a webservice which co-exist on the STA Servers.
Add new comment
By submitting this form, you accept the Mollom privacy policy.