6/19/2026 10:26:44 AM
|
| |
| 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.
|
|
|
|
What would cause a LAN user to have to re-start the Saleslogix System Service on their local PC/laptop
Posted: 05 Jun 09 5:16 AM
|
I am just asking the above question as we recently had a incident where some LAN users managed to log into saleslogix and a number of users could not.
I am not sure if the Server that contains the salelogix database and saleslogix system, enviroment was changed. But the only way the problem was resloved was by re-starting the Saleslogix System Servive on the users local PCs. Or the user had to re-start their PCs or laptops.
Any ideas what might cause this type of problem?
Thank you |
|
|
|
Re: What would cause a LAN user to have to re-start the Saleslogix System Service on their local PC/laptop
Posted: 09 Jun 09 2:41 PM
|
Typically lost connectivity would do this.
If your network goes down, or the server is unavailable/unaccessible, you may have to restart the SLX System.
I have seen this issue many times, and you typically would find entries on the Event log indicating timeouts (CB Mediator timeout.....)
When that is the case, the advise for an regular end user is would be to "restart" their machine, whereas for a power user you could walk them through the process of restarting the service (or killing the process and restarting the app)
Also, as stated above, I would recommend that you always run the SLXSystem as a service.
|
|
|
|
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!
|
|
|
|
|
|
|
|