GPResult returns "Error: Not Found"

[philjones2000]

Annoyingly 1 or 2 machines in our ICT suites have started dropping their printers (which are applied with print management through the GPO).

 

So I check that they're in the right OU and they have good network connections and can ping everywhere etc. No probs.

 

Go to run gpresult to make sure the gp is being applied and it merely answers back:

 

Error: Not found

 

Like I say, this is only happening on one or two machines per room and seemingly at random. Identical machines (same hardware, same image) act like totally normal.

 

Is something corrupting somewhere? Although this is only a small problem at the moment, I'd like to stop it before it spreads...

 

Plus I'm just curious to know what's happening...

 

Thanks as always

 

Phil

[contink]

Well this is a guess but have you checked that the machines can see the printers still?

 

I'd check for network connection issues, ACL permissions issues for the printers, etc...

[Ric_]

I'd check DNS and try rejoining to the domain (assuming that the GPMC works OK with other machines).

[philjones2000]

You can install the printer fine manually. And every other flippin machine in the room works

 

Have quit and rejoined domain. Moved OU. Changed OU. Changed GPO. Tried new GPO. Tried talking to machine nicely. Tried beating it with a stick. Tried beating self with stick.

 

GPResult

Error: Not Found

 

Going to cry in server room now.

 

It's only the computer policy that appears not to apply. The users policy applies and generally people don't notice. Until they come to print....

[contink]

oooh... hold on a tick... is this one of those times when the GP has decided it isn't readable any more.

 

Really can't remember details but IIRC you can try opening the policy, editing something random, closing it, re-opening it, editing it back to the normal and try gpupdate.

 

Can't remember why it does it, or indeed if I'm remembering this right but I believe that might be part of the problem.

[NicholaisoN]

Hello, I'm also experiencing this same errror - does anyone know of a solution yet?

 

Nick

[atboukha]

This is the #1 google result for this error so I'm just quickly posting the solution here even if the thread is a year old, this is because of a defective WMI database on the PC, you will have to delete it so Windows can re-create it from scratch (the WMI database just contains cached data about hardware and software information on the PC).

 

You can use these instructions: hxxp://windowsxp.mvps.org/repairwmi.htm

[burgemaster]

do you have event 1090 in the event viewer logs?

 

If so:

net stop winmgmt

cd /d %windir%\system32

regsvr32 /n /I userenv.dll

cd wbem

mofcomp scersop.mof

 

**** opps didnt see the dates on these posts lol

[zippo]

Check you servers are replicating properly - if they are not - sort it out because that is probably the problem.

[mjgreen]

I am having this problem as well! Any ideas??

[mjgreen]

Oh and I have checked replication, they are replicating fine.

 

My only concern is that it may be to do with the time falling out of sync. We had this problem recently but we think that we have resolved it. Could it be linked!

[Michael]

oooh... hold on a tick... is this one of those times when the GP has decided it isn't readable any more.

 

Really can't remember details but IIRC you can try opening the policy, editing something random, closing it, re-opening it, editing it back to the normal and try gpupdate.

 

Can't remember why it does it, or indeed if I'm remembering this right but I believe that might be part of the problem.

 

It could be that it updates the timestamp on the policy as something has been changed. One theory anyway

 

Oh and I have checked replication, they are replicating fine.

 

My only concern is that it may be to do with the time falling out of sync. We had this problem recently but we think that we have resolved it. Could it be linked!

 

Replication could create problems like this, but the problem would be more widespread. If the server/workstation times are 5 mins out, you will also get problems too. Configuring your 2008 R2 DC as a time server, Windows 7 clients will automatically check in periodically with no GPOs or scripts required. It's a native feature.

Edited November 17, 2011 by Michael

[Michael]

This is how I setup a time server in 2008 R2 with 7 clients

[mjgreen]

This is how I setup a time server in 2008 R2 with 7 clients

 

Thanks guys but just to confirm, we do have our Primary Domain Controller setup as a time server and I do believe that it is working correctly so I am not sure that this is the answer. Is there anything else I can look at?

[ricki]

HI

 

I am guessing here wildly.

 

Did you start happening when the clocks moved. If so as people have said it could be time.

 

Or

 

We had this when a network card went strange in a printer I think and started broadcasting to the entire network and got switchs to fall over.

 

We also had it when a switch was overheating due to fans and had to have the fans replaced.

 

The other thoughts I have had. Are the machines with the problem ones with a 1gig network card. We have had it where the card was too fast for the network and we had to put a gpo in to wait for network and a registry key in to get the client to wait for network at boot so it picked up gpo settings.

 

I think it was

 

Windows Registry Editor Version 5.00

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]

 

"GpNetworkStartTimeoutPolicyValue"=dword:0000003c

 

Read up on this online before doing it but it did fix our problems

 

Put this into a name.reg file and then apply the registry setting.

 

Richard

[mjgreen]

HI

 

I am guessing here wildly.

 

Did you start happening when the clocks moved. If so as people have said it could be time.

 

Or

 

We had this when a network card went strange in a printer I think and started broadcasting to the entire network and got switchs to fall over.

 

We also had it when a switch was overheating due to fans and had to have the fans replaced.

 

The other thoughts I have had. Are the machines with the problem ones with a 1gig network card. We have had it where the card was too fast for the network and we had to put a gpo in to wait for network and a registry key in to get the client to wait for network at boot so it picked up gpo settings.

 

I think it was

 

Windows Registry Editor Version 5.00

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]

 

"GpNetworkStartTimeoutPolicyValue"=dword:0000003c

 

Read up on this online before doing it but it did fix our problems

 

Put this into a name.reg file and then apply the registry setting.

 

Richard

 

Thanks very much for your advice. More and more research seems to be suggesting the time problrem. Now that we fixed an issue with the time, I think we just need to wait and see if the problem occours again on any other PC's. I just had hoped that when we fixed the time, the PC that is currently having these problems would start working again. Perhaps not!

 

I will keep my eye out and if we get another one doing this, revive this thread.

 

Many thanks