General discussion

Locked

Windows cannot query for the list of Group Policy objects

By mciolino ·
I started with this showing up on my sql server

The description for Event ID ( 1000 ) in Source ( Userenv ) could not be found. It contains the following insertion string(s): The Group Policy client-side extension Security was passed flags (17) and returned a failure status code of (

Then it changed to this
The description for Event ID ( 1000 ) in Source ( Userenv ) could not be found. It contains the following insertion string(s): The Group Policy client-side extension Security was passed flags (17) and returned a failure status code of (2)..

My network is as follow
1 DC windows 2000
and 3 members severs
1 Sql 2000
1 Exchange 2000
1 a nt 4.0

I started get these evt shown above on my sql meber server when a person or app for to log on the server.

This conversation is currently closed to new comments.

3 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by Joseph Moore In reply to Windows cannot query for ...

Ok, let's see where we get with this one.
First off, read this Technet article:
http://support.microsoft.com/?kbid=312164

It talks about decoding the error numbers somewhat. Basically, with "passed flags (17)", that gives you this:
"If you convert the decimal representation of the flags value that is specified in the event message (17) to hexadecimal, you get 0x00000011. This tells you that both the GPO_INFO_FLAG_MACHINE and GPO_INFO_FLAG_BACKGROUND flags are set."

So, now we know it is Group Policy stuff, part that runs in the background. Ok.

Now, the two "failure status codes" give us these messages:
The system cannot find the file specified.
and
Not enough storage is available to process this command.

Good. The Technet article tells you how to find these error messages. So, Group Policy can't find some file, and there is not enough drive space for Group Policy to finish what it is doing.
Here is my though on this. I believe that a lot of times, this "Not enough storage" message refers to the amount of drive space the Registry is allocated. When it gets too low, then I think you start getting this error.
So maybe what is happening is Group Policy wants to push stuff into the REgistry on your SQL Server box, but it doesn't have enough allocated memory for the REgistry on it do to this, so you get errors.
So, try increasing the amount of drive space for the Registry on the SQL Server box.
Open Control Panel -> System -> Advanced Tab ->Performance Options button -> Virtual Memory Change button.
Then in the Registry Size section, change the max size to something larger then what it is. And note what the current size is. Are they close? Set it like 30 megs higher then the currrent Max setting.
I think you need to reboot before doing this.

Collapse -

by Joseph Moore In reply to

Also, TEST THIS first, to make sure you don't fry your SQL Server. Take a backup of the SQL Server before doing this. I have never actually changed this Registry size setting, and I think it is safe to do, but I have never actually done it!
So be careful!
hope this helps

Collapse -

by Joseph Moore In reply to

PS: I hate when that <BR> sneaks in there during a post!

Back to Windows Forum
3 total posts (Page 1 of 1)  

Related Discussions

Related Forums