check epo and database communication
If you monitor the memory usage on the machine, is it genuinely running out of memory? If so, which process is using it all?
you're right. It really was that simple.
About 10 GB of memory was used by SQL Server. But it had AWE enabled and therefore memory consumption was not displayed correctly in Task Manager.
I still don't understand why it runs out of memory although there is enough swap space.
However I'm happy that it is working now :-)
No problem - glad it was that easy
I am not seeing what you actually did to correct the issue. I am seeing the exact same errors in server.log and it started after upgrading to 4.6 sql server is taking all available mem 8gb.
I've limited the memory available to SQL server. You can use SQL Server Management Studio to do that.
Right click on the server in object explorer and select "server properties".
I've set the maximum server memory to 2/3 of the total physical memory.
Here is a screenshot of that configuration window:
With 12 GB physical memory I have:
- Use AWE: Disabled
- Minimum server memory: 0 MB
- Maximum server memory: 8192 MB
Unfortunately I the same Problem and can´t get it resolved. Could you please help me?
My configuration right now is the following:
Windows Server 2003
SQL Server Standard 2005
RAM: 4096 MB
/3GB Option in Boot.ini enabled
Virtual Memory: 10 GB
Min Memory: 0
Max Memory: 3072
You could try to further reduce the max memory.
In my case the physical memory usage had to be below 95% or ePO failed to respond to agents. On server 2008 the memory usage is shown in the task manager (physical memory xx %). I can't find the percentage value on a 2003, so you have to try different settings.
If you have a lot of other services running on this server, even 3072 could be too high.
Please also note that you have to restart SQL server service after you modify the max memory setting.