SLXKeepLoggedInThread

[mtamborini]

Sage told us Hot Fix 6 for 7.5.2 should be for this issue:

Defect Description
1-72683 Varnumeric not supported in an Oracle 10g 64-bit environment.
1-72848 Join conditions ignored by provider.
1-73053 SLXSystem will hang under heavy loads due to an abandoned critical section.
1-74731 A change to the currency field is not handled properly by the provider when
building up the deleted recordset for the provider triggers.

SLX_v752_Lan_HF06.zip SLX_v752_Lan_HF06.exe
SLX_v752_Lan_HF06.exe SLXDBEngine.dll, SLXEventMessage.dll, SLXOLEDB.dll,
SLXPROFILING.dll, SLXServer.exe, SlxSL.dll, SLXSystem.dll,
SLXSystem.exe, SLXTriggers.dll

[aimar]

We have similar error SLX 7.5.1.1742 (with HF48). Windows 2003 Terminal Server. SalesLogix have HotFix 48 for that. We installed that to that machine, but no changes. SLXSystem.exe still crashing about every 1-2 hours and mainly on working hours.

Event Type: Error

Event Source: SLXKeepLoggedInThread

Event Category: None

Event ID: 4

Date: XXX

Time: XXX

User: N/A

Computer: XXXXX

Description:KeepLoggedIn: System Object has no connection.

thanks,

Aimar

[twalker]

Aimar,

I had a that same issue with a client.  The client had upgraded from 6.2.x to 7.5.1.  As part of the upgrade they got a new SalesLogix server and that server had a different server name than the old one.  After the upgrade SLXSystem would crash on both terminal servers several times a day once we shut the old server off.  Someone at Sage recommended going through the registry and deleting all the connection references to the old SalesLogix server.  There were several references in the registry and after that was done I don't think we had any more problems.

Not sure if that exactly applies to your situation but it seemed to work for me.

Trevor

[TitansNFL]

Having the same issue.  The users was had clicked the Contact Quick Search when the

[EmmaNixon]

Application: SalesLogix Client

Version Reported: 7.5.x, 7.2.x, 7.0.x, 6.2.x

Description:

The full error appears as:

Event Type: Error
Event Source: SLXKeepLoggedInThread
Event Category: None
Event ID: x
Date:  x/x/xxxx
Time:  x:xx:xx
User:  N/A
Computer: XXXXX
Description:
The description for Event ID ( 0 ) in Source ( SLXKeepLoggedInThread ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: System Object has no connection.

SLXSystem is a self-recovering system.  The error could be caused by either:

1. SLXServer shutdown (server computer restart, crash, DNS issue)
2. Network connectivity lost between client and server computer

Possible Resolution 1:

If using 6.2 SP3 or higher, ensure that the SLXSystem.exe is installed as a Service.  For more information, review How to install SLXSystem.exe as a service.

Possible Resolution 2:

This error can occur if Window's Power Saving settings are hibernating or interfering with the workstation's power state. For more information, see Microsoft.

Possible Resolution 3:

Due to the unique nature of Terminal Services, there is a specific method that gives the highest probability of success when installing SalesLogix in this type of environment. 

1. Verify the Terminal Services box is isolated and no terminal services instances are or will be started on this machine during the installation process
2. Verify the install and uninstall is being done from the Terminal service box, not through a terminal services session 
3. On the machine:
1. Uninstall all Saleslogix applications through Add/Remove Programs
2. Run REGEDIT and delete SalesLogix registry keys from HKLM and HKCU
   
   HKLM\Software\SalesLogix  (Local Machine Hkey)  HKCU\Software\SalesLogix (Current User Hkey)
3. In Windows Explorer, if present, delete the following Saleslogix folders
   
   C:\Program Files\SalesLogix
   C:\Documents and Settings\All Users\Application Data\SalesLogix  
4. Reboot the machine
5. Install all of the SalesLogix applications that were removed by using the Add/Remove Programs application
6. Add new programs NAV button (choose multi-user install)
7. Follow the instructions for installing SalesLogix on the computer (review the SalesLogix Implementation Guide that is supplied with SalesLogix on CD1)
8. Restart the computer

[TitansNFL]

Thanks Emma, we found this article too. There have been a couple of instances of this error in the past few weeks on a V7.5.3 Windows Client system running on Citrix. The system had been running fine since the upgrade to 7.5.3 about 6 months ago. Nothing has changed (except Citrix and Windows Server patches) since then. The last occurrence of the error was after clicking on the Quick Search for Contacts. Much of the KB addresses an install and that is not this situation. Also SLXServer is running as a service. Thus the KB solutions do not appear to apply. To temporarily get the users (has happened to 3 out of 80) back in SLX we deleted their Citrix profile and recreated it. Not sure this is the solution. Anyone seeing this error after recent Windows Server updates? Thanks, Bruce Pershke

[TitansNFL]

Got the KeepLoggedIn Event Log errors again yesterday with a client where we had upgraded from V7.2.2 to V7.5.4 and moved the SalesLogix server to a new server.  This was over 3 weeks ago and everything ran fine.  Yesterday they retied the old server and the SLXService on the Citrix servers immediately started shutting down.  The solution was as suggested above, to go into each Citrix serve and delete all references to the "old" server.  We found registry settings for the SLX users with reference to the Data Link Manager where the server was the old server.  We actually edited the setting to the new server name.  Haven't had a problem since. This should be created as a KB article. 

Bruce Pershke

[EmmaNixon]

Hi Bruce

Quick question, when you moved the SLX Server did you reset the Connection Manager connection and then update the Datalink on all your citrix servers as that should have updated the registry?

If it didn't I will scope out a KB article as it might be useful for others.

Thanks, Emma

[TitansNFL]

Yes all the user Data Manager connections were revised to the new SLX Server about 4 weeks ago and worked fine. The connections in the "old" SLX server Connection Manager were deleted so the users could not use the "old" server. The were working fine on the "new" server until the "old" server was taken down.

[EmmaNixon]

Thanks for the additional information Bruce.

I'll put something together for the KB.