Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 Failed Virtual Allocate Bytes: FAIL_VIRTUAL_RESERV

Author  Topic 

imarchenko@hotmail.com
Starting Member

6 Posts

Posted - 2009-02-02 : 16:42:04
Hello!

Our server, SQL Server 2005 Standard 32-bit on Windows Server 2003 R2 with 4GB, is experiencing problems. At some random point, CPU goes above 90% and server becomes unusable. I come across following errors in the log right before CPU comes to a stall:

...
2008-12-21 21:20:20.36 spid262 Failed Virtual Allocate Bytes: FAIL_VIRTUAL_RESERVE 589824
2008-12-21 21:20:20.42 spid262
Memory Manager
VM Reserved = 1779104 KB
VM Committed = 1681860 KB
AWE Allocated = 0 KB
Reserved Memory = 1024 KB
Reserved Memory In Use = 0 KB

2008-12-21 21:20:20.42 spid262
...
2008-12-21 21:20:20.59 spid262 Error: 701, Severity: 17, State: 123.
2008-12-21 21:20:20.59 spid262 There is insufficient system memory to run this query.
...

Currently, we do not have /3GB switch enable. It looks to me that CPU issues are result of aforementioned errors.
I did disable CLR integration and disable a couple of maintenance jobs (index and database integrity checks) as some people mentioned this could be a culprit, but problem still there.
I am going to add /3GB switch to make SQL Server use more memory.

Any advice on this matter is greatly appreciated.

Igor

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2009-02-02 : 16:58:22
Check Standard reports for CPU consumption?
Go to Top of Page

saurabhsrivastava
Posting Yak Master

216 Posts

Posted - 2009-02-03 : 22:01:23
adding /3GB should help but this is a workaround you may see Memory issues in future with growing workload. You current VM consumption is VM Reserved = 1779104 KB VM Committed = 1681860 KB When you run into this problem check what queries are running on the system and thier impact. You may find some poor performing queries. If you have default trace enabled check it to find mmory errors and what triggers it.
Go to Top of Page

saurabhsrivastava
Posting Yak Master

216 Posts

Posted - 2009-02-03 : 22:07:23
Forgot to ask what is spid262, this may be triggering memory issue.
Let us know details about this spid to discuss further to come to a conslusion.
Also check this KB article - http://support.microsoft.com/kb/316749
Go to Top of Page
   

- Advertisement -