Windows 2003 Server Event 244

After I restarted my Windows 2003 R2 Standard DC SP2

Added /3gb /pae options to my boot.ini

This message appeared

Type :            Warning
Date :            4/8/2010
Time :            5:39:17 PM
Event :            244
Source :            Win32k
Category :      None
User :            N/A
Computer :      TGCS001
Failed to create a desktop due to desktop heap exhaustion.

any ideas


Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Do you really need the /3GB switch on a DC?  Also, you may have a driver that won't function while in /3GB mode.
InserachofAuthor Commented:
Yes I run sql 2005 on that server and we have issues with memory from sql


All server functions are working just trying to find out what this message means
Here, read this article when you have a moment.  It'll be better than me trying to explain it.

I've heard that there are alot of people with issues when using the /3GB switch on Windows 2003 R2 Standard DC SP2
Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

InserachofAuthor Commented:
ok thanks for the info but that does not explain this error

I would like an explaination of this error

“Failed to create a desktop due to desktop heap exhaustion.” is logged when the heap itself cannot be created. If a desktop heap cannot be created, then the entire desktop creation attempt fails. Usually a failure to create a new desktop heap means that session view space is exhausted for the session. You may be able to resolve this issue by increasing the size of session view space (using the SessionViewSize registry value) or by decreasing the third shared section value (assuming session view space is primarily used by non-interactive desktop heaps), to allow for more heaps to be created. Before making any changes, I suggest you use dheapmon to view desktop heap usage on your system shortly after you see the error. It helps to understand the usage of desktop heap before making changes. FYI, the desktop heap failure errors are only logged once per session to avoid a flood of events in the event log. So you may actually have more than one failure per session, but only one is logged. Desktop heap logging can be enabled or disabled with the DesktopHeapLogging registry value (see MS KB 810807).

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
InserachofAuthor Commented:
the next time i restart the server i will check it out and then i will post info
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.