Share via

Memory Errors in SSMS log

Veena Srinivas 251 Reputation points
2021-01-05T20:25:06.34+00:00

Hello ,

I have 1 database server which has 32 GB physical memory . 4 cpu.
Instance is running SQL Server 2014 version, and OS is Windows Server 2016.

Right now, 8 gb is allocated to SQL Server, and remaining is for OS.

Before I have adjusted to16 gb is given to SQL and remaining to OS.

We have an external application which connects to the DB, it will work fine for few days, and then the next time they try to login, it wont allow from application.

We see these errors in log file, and then I end up restarting SQL services. Then again it will be fine for few days, and then same issue will repeat. Please help!

There is insufficient system memory in resource pool 'internal' to run this query.

Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.

Failed to reserve pages: FAIL_PAGE_RESERVATION 128

SQL Server | Other
SQL Server | Other

Additional SQL Server features and topics not covered by specific categories

0 comments No comments

Answer accepted by question author

Shashank Singh 6,251 Reputation points
2021-01-06T08:00:53.83+00:00

Failed to reserve pages: FAIL_PAGE_RESERVATION 128

You are facing OOM issue and primarily it seems due to low memory set for SQL Server. As Amelia has suggested you should increase the max server memory. SQL Server is even not able to reserve memory, forget about allocating.

Right now, 8 gb is allocated to SQL Server, and remaining is for OS.

This does not seems correct and this could be the reason for OOM error. You have 32 GB and giving just 8 GB to SQL Server will starve it for memory and you may see such issues.

If nothing else is running on the system set max server memory to 26 or 27 GB.

Was this answer helpful?

0 comments No comments

1 additional answer

Sort by: Most helpful
  1. AmeliaGu-MSFT 14,016 Reputation points Microsoft External Staff
    2021-01-06T07:24:04.967+00:00

    Hi VeenaSrinivas-0229,
    This issue may be due to insufficient memory. You can try to increase SQL Server memory:

    EXEC sp_configure 'show advanced option', '1'
    GO
    RECONFIGURE WITH OVERRIDE
    GO
    EXEC sp_configure 'max server memory', '102400' --set the value based on your requirement
    GO
    RECONFIGURE WITH OVERRIDE
    GO
    

    Please refer to this article which might help.
    Best Regards,
    Amelia

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.