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!
|
|
SalesLogix System Logon SLXSERVICE
Posted: 20 Jul 09 5:58 PM
|
| For SalesLogix we use a Terminal Server for the clients and the SalesLogix System Logon we used was local system account. But then after a while that didn't work so we created an account called slxservice and used that. Now when I restart the Terminal Server SalesLogix wont work until I stopped the Service and start it again. Any thoughts? |
|
|
|
Re: SalesLogix System Logon SLXSERVICE
Posted: 20 Jul 09 9:37 PM
|
Hmm, I'm not sure I'm going to say this right.. But make sure the slxservice account has the ability to run as a system account (is this the right term?) on the Terminal Server.
I'm not recalling exactly where this is done either. It might be somewhere in Group Policy.
Am I heading down the right track, anyone?
John G. |
|
|
| |
|
Re: SalesLogix System Logon SLXSERVICE
Posted: 21 Jul 09 8:22 AM
|
We had the same problem on Win2003 and it was all about permissions. Make sure the slxservice is local administrator.
We had further issues and had to go thru all Saleslogix folders and grant full permissions to users. Also had to go thru the registry and grant permssions there as well.
|
|
|
|
Re: SalesLogix System Logon SLXSERVICE
Posted: 21 Jul 09 11:00 AM
|
Question: When you installed the SLXSystem as a service, did you set the machine into Installation mode? (e.g. Change User /install ?)
Other than that, you should follow the same steps as outlined on the Implementation guide, and would indeed pay close attention to the Rights needed by each service account in place.
Also, I recall having read in the past the "Implementing SalesLogix in Terminal Server/Citrix" guide from SalesLogix. I don't know if this is still a valid document and/or where it could be found, but when it comes to Terminal Server, the main items for it where making sure to set the system in Install mode and to run the SLXSystem as a Service. |
|
|
|
Re: SalesLogix System Logon SLXSERVICE
Posted: 22 Jul 09 3:23 AM
|
| Anything post Win2003 you don't need to use the InstallMode (server handles it automatically). The SLX System Service should be started as a local account only. |
|
|
|
Re: SalesLogix System Logon SLXSERVICE
Posted: 22 Jul 09 1:42 PM
|
Hi thanks for the reply. I used to have the slxservice logon and then I had issues so I just used local system account and that worked fine for a while. Then that wouldn't work after some server maintenance so I am back to slxservice and it is working now. Crazy. Tech Support told me to use the slxservice but I found I had more success using local system.  |
|
|
|
Re: SalesLogix System Logon SLXSERVICE
Posted: 22 Jul 09 1:43 PM
|
| Yeah. Basically you are saying make sure slxservice has admin rights. I have done that. It is just tempermental for some reason. But slxservice is now working. Yeah! |
|
|
| |
|
Re: SalesLogix System Logon SLXSERVICE
Posted: 22 Jul 09 1:45 PM
|
| Right. I have slxservice as an admin. Now it seems to work after rebooting and everything. So we'll see what happens. Thanks so much. |
|
|
|
Re: SalesLogix System Logon SLXSERVICE
Posted: 22 Jul 09 2:28 PM
|
Hi Mike
About a year ago I built 5 new 2003 terminal servers with Citrix, and went through the same thing with the Saleslogix. It was frustrating not just for that but also because the servers all seemed to react differently even though they were the same(hardware and software).
Not sure if you have already, but make sure you test with multiple users connected before putting in production. That was another issue.
Jim |
|
|
|
Re: SalesLogix System Logon SLXSERVICE
Posted: 23 Jul 09 8:40 AM
|
| well - i went back to using logon as "local system account" and restarted last night and that works again. I believe I can trace this back to something getting out of sync with the SalesLogix server. During this mess that server was up and down and when it gets out of sync I think that is part of the problem. So... we'll see what happens. Thanks a lot |
|
|
|