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!
|
|
Connection failure in 7.2
Posted: 16 Jun 08 7:31 AM
|
Hi.
I have several users who frequently have such an error as: Connection Failure, Error in SalesLogix.exe
I've seen application logs on their pc and considered that some users have in this period of time the same errors
They are:
Source: SLXKeepLoggedInThread
Category: None
Event ID: 4
Description:
Error in KeepLoggedIn Thread: Line 3 OLE error 80041005
Source: SLXSystem.EXE
Category: None
Event ID: 3
Description:
W-CBMediator request timed out (CLI 8, LID 53, RID 59).
Type: 6881396, OLen: 6750318, Dump: 73005C0041006C006C002000550073006500720073005C004100700070006C00690063006100740069006F006E00200044006100740061000000000000000000
Can you give some advice to solve this problem?
|
|
|
| |
| |
|
Re: Connection failure in 7.2
Posted: 19 Jun 08 12:46 AM
|
| But we do not have interface updowns and network errors in error log. Other networking applications are available in the moment of saleslogix connection failure. |
|
|
|
Re: Connection failure in 7.2
Posted: 19 Jun 08 2:05 AM
|
You wouldn't get an i/face up/down error in the syslog anyway. Never does.
What's the situation with servers etc. what's connected, how's it connected, what SQL vsn, TermServer etc?
|
|
|
|
Re: Connection failure in 7.2
Posted: 19 Jun 08 2:09 AM
|
for saleslogix we use 1 application server (virtual) and 1 sql server 2005 9.0.1399 (virtual)
what do you mean asking how it's connected? |
|
|
|
Re: Connection failure in 7.2
Posted: 19 Jun 08 2:14 AM
|
If you are using SQL2005 - are you using Native Client as the connection of MS OLEDB ?
In terms of connection - *you* need to provide as much information as possible so we can help - otherwise, it's like pulling teeth ! We can't just guess what the issue is - as there could be many !! This error is *not* normal - and only normally occurs when the connection is dropped. You see this a lot with Terminal Server if the session is disconnected and eventually times out. As SLX is continually checking to see if a client is connected (for license purposes) then if it can't ping the client then this error occurs on a disconnected session (as TS shut it down). But, on a normal LAN client, with normal networking, this error shouldn't occur. It could be something as simple as a dodgy network hub/switch with a "chatty" port. |
|
|
| |
| |
|
Re: Connection failure in 7.2
Posted: 19 Jun 08 2:21 AM
|
| U see, the problem is that we already checked all the "problem" users network routes and tried to switch them to different ports and also different switches, but tje problem on their workstations still persist |
|
|
| |
|
Re: Connection failure in 7.2
Posted: 19 Jun 08 2:31 AM
|
| Is it possible to get acknowledged how the "cheking client availability" procedure is happening? Which level it uses? Which port pings? |
|
|
|
Re: Connection failure in 7.2
Posted: 19 Jun 08 2:35 AM
|
| It's a low level IP socket call - across ports 1706 & 1707. SQL is on 1433 and 1434 (both by default, unless modified) |
|
|
|
Re: Connection failure in 7.2
Posted: 19 Jun 08 2:45 AM
|
How version can be a reason if the problem occurs only on several workstations (less than 3% of users)
What else can u advice to check? |
|
|
|
Re: Connection failure in 7.2
Posted: 03 Dec 08 8:07 PM
|
Originally posted by Mike Spragg
If you are using SQL2005 - are you using Native Client as the connection of MS OLEDB ?
In terms of connection - *you* need to provide as much information as possible so we can help - otherwise, it's like pulling teeth ! We can't just guess what the issue is - as there could be many !! This error is *not* normal - and only normally occurs when the connection is dropped. You see this a lot with Terminal Server if the session is disconnected and eventually times out. As SLX is continually checking to see if a client is connected (for license purposes) then if it can't ping the client then this error occurs on a disconnected session (as TS shut it down). But, on a normal LAN client, with normal networking, this error shouldn't occur. It could be something as simple as a dodgy network hub/switch with a "chatty" port. |
|
Hi Mike,
I also have this kind of problem in one of my terminal server. But it only happens lately for the last 2 months. Yes we put some session policy, that the TS will disconnect if the user is idled for 15minutes, and then after that, end the session after 15 minutes the session was disconnected.
I've tried to restart the slx service, restart the server, reinstall the SLX client, but the problem persists. What makes me confuse is that the problem happens in only one of our TS. The others TS are running well.
Windows 2003 Server
SQL Server 2005
SLX 6.2.6
Is there any thing you can sugest me....? any comments, are welcomed.
Thx in advanced.
*fajar |
|
|
|
Re: Connection failure in 7.2
Posted: 04 Dec 08 3:44 AM
|
| This isn't an error per se - it's just a natural occurence of the policy you have put in place. When you end the session that's what TS does - it doesn't shut down SLX cleanly - it just terminates it and it is this action that causes the issue. There isn't anything you can do short of changing the policy or, as I do, just ignore the "error". |
|
|
|
Re: Connection failure in 7.2
Posted: 04 Dec 08 4:37 AM
|
Thx for your quick reply. I can't just ignore the error message, because it really makes error not just warning.
When the user tries to log on using SalesLogix Client. The SLX client can't connect to application server by displaying message box:
"Database login failed: Failed to connect to SLXServer. Check if server is running and is compatible with the current provider version"
My temporer solution, I ask my user to restart the SLX System service before they try to log on to SalesLogix. *bad decision though*
Meanwhile, i add them some remote desktop access to another well working TS.
Is there anything that i missed... Damn it only happened on that TS for the last 2 months. 
Regards,
*fajar |
|
|
| |
|
Re: Connection failure in 7.2
Posted: 04 Dec 08 4:46 AM
|
Originally posted by Mike Spragg
Are you sure you are running the slxsystem.exe as a service on this server ?? |
|
Yes, I'm definitely sure...
I also already check it through the task manager. |
|
|
|
Re: Connection failure in 7.2
Posted: 30 Jun 09 12:24 PM
|
Hello,
I have the same issue on my Citrix server ps 4.0 with the SLX cleint 7.5.0.14.84.
Impossible to connect to SLX client on Citrix...
That's fixed when I kill the process slxsystem.exe and restart it. My slx's users are able to launch SLX client in their Citrix session.
any idea?
Regards,
|
|
|
|
Re: Connection failure in 7.2
Posted: 30 Jun 09 12:24 PM
|
Hello,
I have the same issue on my Citrix server ps 4.0 Win 2k3 US without SP with the SLX cleint 7.5.0.14.84.
Impossible to connect to SLX client on Citrix...
That's fixed when I kill the process slxsystem.exe and restart it. My slx's users are able to launch SLX client in their Citrix session.
any idea?
Regards,
|
|
|
|
Re: Connection failure in 7.2
Posted: 30 Jun 09 12:25 PM
|
Hello,
I have the same issue on my Citrix server ps 4.0 Win 2k3 US without SP with the SLX cleint 7.5.0.14.84.
Impossible to connect to SLX client on Citrix...
That's fixed when I kill the process slxsystem.exe and restart it. My slx's users are able to launch SLX client in their Citrix session.
any idea?
Regards,
|
|
|
|
Re: Connection failure in 7.2
Posted: 30 Jun 09 12:25 PM
|
Hello,
I have the same issue on my Citrix server ps 4.0 Win 2k3 US without SP with the SLX cleint 7.5.0.14.84.
Impossible to connect to SLX client on Citrix...
That's fixed when I kill the process slxsystem.exe and restart it. My slx's users are able to launch SLX client in their Citrix session.
any idea?
Regards,
|
|
|
|
Re: Connection failure in 7.2
Posted: 30 Jun 09 12:31 PM
|
Have you configured it to run as a Service?
And, if so, did you configure it to run with an account that has enough Access to SLX / Network /SQL ?
This may be why it runs for users, because it gets instantiated under their profile and it runs fine, but maybe when the first person that runs it doesn't have enough rights it then fails (and would fail to everyone as it is a shared service). |
|
|
|
Re: Connection failure in 7.2
Posted: 01 Jul 09 4:06 AM
|
hello,
You're right, it was started with local system, I changed.
To be continued,
thank you,
|
|
|
|
Re: Connection failure in 7.2
Posted: 01 Jul 09 7:22 AM
|
This is a typical misconfiguration. If the service is not configured with an account that has enough rights to connect to SLX and SQL (depending on the Library chosen for the SQL Client) you will run into issues.
When troubleshooting this type of problems, the very first thing I look at is the credentials of SLX System as running on Task Manager.
Also, make sure that the service is set to Automatic, having it there but set to Manual also defeats the purpose of it running as a Service. |
|
|
|
Re: Connection failure in 7.2
Posted: 23 Jul 09 8:46 AM
|
| I've gone back and forth with this. We us a TS for clients and I am now using logon local system account. But sometimes that stops working and I use a logon I created called slxservice with admin rights. But then I went back to local system account and it works again. I believe I have traced it back to my App server (SLX Server) getting out of sync with the TS. After I restarted both servers everything is fine. |
|
|
|