Our client has faced with a problem that memory allocation for SLXServer.exe is growing up (1,4 Gb and still growing). Can you give us any suggestion why it is growing and how to avoid that?

How many memory allocated SLXServer.exe at your customers?

Slx Version = SalesLogix 7.5 SP2 (without hot fixes)
OS = Windows server 2008
Database = Oracle 9.2.0.7.0
Users = 250

Please help.

SLX Server should not have a need for that much Memory (even for large deployments), you are indeed looking at a Memory Leak issue.

I would suggest that you restart the Service when you notice that the Memory allocation starts growing (I would observe where the Memory usage stands after a day's use and take that as a baseline). Have you noticed how much it grows each day?

How to avoid it? You may have to check with SAGE and see if this is a known issue, and if so what the solution is. Check all available hotfixes and see if any of them references this kind of problems.

There is typicaly no harm on Restarting this service at the end of the day when no users are on the system.

I would also look at the types of groups some of the users are running. For example I've seen users with large databases modify the "All Accounts" group to have a outer join to the history table so they can "scan history info quickly" this was close to a million records and impacted more than just the provider box. But the point is you might want to look at what caching is doing or holding.

I assume you have not "customized" the provider. This is a little know method of modifying the security at the provider level and requires a high level of understanding to get right. If you have, I'd start looking there.

Quote: Originally posted by Lane I would also look at the types of groups some of the users are running. For example I've seen users with large databases modify the "All Accounts" group to have a outer join to the history table so they can "scan history info quickly" this was close to a million records and impacted more than just the provider box. But the point is you might want to look at what caching is doing or holding. I assume you have not "customized" the provider. This is a little know method of modifying the security at the provider level and requires a high level of understanding to get right. If you have, I'd start looking there.

Yes, but...

The provider is Implemented at the Client level and would show High memory usage on the SLXSystem.ext.

The SLX Server revolves more around Licensing and User Validation which is why I mentioned that the memory footprint for it should always be low.

Thanks for reply!

1. After restart SLXServer.exe takes 5 Mb.

2. Per day of memory allocation (SLXServer.exe) grows to 20 MB. (~140 Mb - per week).

3. We don't "customized" the slx provider.

4. Sage say: "We haven’t had any reports of this type of problem on a 7.5 system."

I know that this isn't a solution, but a workaround:

Build a Script to Restart the Service.

Create a Scheduled Task to run the script every day (e.g. @ 3 AM).

Are you synchronizing to remote users?  If not, but the database is set up for it, then the service is processing a lot of queue files that it does not need to do.

We don't synchronizing to remote users. And database is not set up for it.

The problem is not solved.

Which 7.5.2 hot fixes have you installed? Which hot fixes have you researched?