5/1/2024 6:30:00 PM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss networking and miscelleanous technical topics. View the code of conduct for posting guidelines.
|
|
|
|
Citrix/Load Balancing oddity
Posted: 06 Jan 08 6:48 PM
|
SLX 7.0.1
SQL Server 2005 sp2
DB server recently moved from same box as App server to different box with san config
3 Load Balanced Citrix boxes: Citrix0, Citrix1, Citrix3
Some user log on as Published app, some to desktop config – same symptoms – sometimes they
get into SLX, sometimes not. Users are accessing other apps through the same Citrix servers with no problems. Users not using citrix connect with no issues.
The error that gets thrown when a connection cannot be made is :
[Database login failed: Failed to connect to SLXServer. Check if server is running and is compatible with the current provider version]
It is a bit of a moving target – I tried logging into SLX on each machine at the console level. I always seem to be able to get into Citrix0 – which is the listening machine for citrix load balancing. I was able to consistently log onto Citrix1 and not log onto Citrix2 – getting the error above.
We took Citrix2 offline, thinking we had narrowed it down. After that Citrix1 would fail consistently and Citirx2, now out of the load balancing, would log on everytime.
From an end user perspective, some people seem to get into SLX on all machines sometimes. No apparent pattern as far as which users to which machine they directed to. I also believe that Citrix0 consistently logs user on – but cannot be 100% sure of that.
We have reinstalled SLX and sp1, reinstalled the SQL native provider and set SLXSystem.exe to run as a service.. Not sure what to try next.. I am suspecting something with new SAN configuration as we believe the problem started when that was implemented last Monday. Any suggestion appreciated. Thanks
|
|
|
|
Re: Citrix/Load Balancing oddity
Posted: 07 Jan 08 6:14 AM
|
It's not that the SLXSystem Service is shutting down is it? Not sure if this happens on 7.0.1 but on our 6.2.6 we needed to do this (from one of the implementation guides):
"To set a specific amount of time for the service to remain
open, add the registry key HKEY_LOCAL_MACHINE\SOFTWARE\SalesLogix\ShutdownDelay(DWORD). The key
accepts values 1 through 1440, where the value indicates the number of minutes the service will run before shutting
down (after it detects no activity). Setting the value to 0 indicates the service never shuts down."
|
|
|
|
Re: Citrix/Load Balancing oddity
Posted: 07 Jan 08 7:07 AM
|
| Stuart, That was one of my first thoughts also. I had previously added the Reg Key and set SLXService to run as a service. Problem persists. |
|
|
|
Re: Citrix/Load Balancing oddity
Posted: 07 Jan 08 9:34 AM
|
| I would be interested to hear what the problem is if you find it. We're having similar problems with a new cluster of Terminal Servers. |
|
|
|
Re: Citrix/Load Balancing oddity
Posted: 07 Jan 08 10:23 AM
|
Hi Stuart,
So at any time, only one machine from the cluster can access SLX?
You may have tried this already, but if not: Try shutting down all Citrix access to SLX , then bring one machine up and try logging into SLX, then being up the second and try to log on. Then reverse it. I think this may at least let you know if the issue is in the SLX Provider (Security or bouncing of the connection) or if the issue is directly with Citrix.
In the past I have used Sysinternals Filemon (free tool) to see if/where the "denied" was happening. In my set up (not as complicated as yours) I had to apply explicit permissions to my SLXService User to access the folder containing the SLX OLEDB files; even though it was a full Administrator of the box.
Carla
|
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|