Hi,

We have a rather annoying problem. We are running 7.5.4 LAN as a published application on a 4 server Xenapp 6 Citrix farm.

We are using windows authentication for the SLX login. Sometimes the users can launch SLX and are logged right into SLX without problems. Other times, the same users will instead get a SLX login prompt, and when they enter their credentials, will get the  "Database login failed: Unspecified Error" message.  Sometimes, if the user cancels here and tries a second, third, or fourth time, they get logged right in. Sometimes they will try for 45 minutes to an hour and continue to be denied access to SLX. 

Checkng the Citrix Server the user is connected to, we find that it happens regardless of the Citrix server they happen to be connected to when they log into Citrix.

Checking the data connection for the session when they are prompted to login, after selecting the SLX server from the dropdown, when I click the database dropdown, it is empty.   From a cmd prompt at the users own PC, they can ping the SLX server with no problems.

Seems kind of random.  Any thoughts?

My first thought is some sort of firewall issue between the SLX Server and the CTX Servers (or a poorly configured managed switch). If you don't see anything in the drop-down then that means it [CTX Server or SLXServer] cannot communicate with each other. This occurs over port n+1 of whatever you configured the SLXServer to operate on (default = 1706+1 so ports 1706 & 1707 need to be open). I'd check the traffic if you can. The fact that it sometimes works and sometimes doesn't means that the SLX Server and CTX Servers are ordinarily fine. erhaps this occurs during high network loads (again, points to switch, firewall/hops). So, basically, ensure basic connectivity is OK especially under load (check packet size, bonded nics, jumbo frames etc.) 

BTW Who is your business partner? - I know I originally spec'd your system and we have other customers on this platform with no issues. So, this is configuration/setup rather than a problem with SLX.

A trick I've use for years on installations via novell or in farms/terminal servers is to force a reg file with the datalink information to auto load on login.

This does a few things, first in a new rollout it means everyone gets in without my needing to look at the settings

Second, we had a production Service provider box fry and it took less than 10 minutes from slx failure to to have everyone back up by adding a connection manager entry on the test server and then updating a reg file. Then the users just reconnected. 

[HKEY_CURRENT_USER\Software\SalesLogix\ADOLogin\Connection1]

"Alias"="SalesLogix"

"Data Source"="SLXAPPSERVER"

"Extended Properties"="PORT=1706;LOG=ON"

"Initial Catalog"="SALESLOGIX"

"Provider"="SLXOLEDB.1"