Does anyone know where to find explanations for the errors
contained in the userenv.log? I have a few PCs that are
not applying Group Policy, and their userenv.log files are
full of messages like this :

USERENV(b8.a0) 10:15:34:656 MyGetUserName: GetUserNameEx
failed with 1355.

and

USERENV(65c.654) 12:17:39:671 RegisterGPNotification:
CreateEvent failed with 5

plus lots more.

TechNet is your best friend!
There is also a GPO troubleshooting guide, which might help. Just search on
Microsoft's site for it.

--
Derek Melber
BrainCore.Net
(E-Mail Removed)
"The Head Mushroom" <(E-Mail Removed)> wrote in message
news:deb101c40af2$def94ce0$(E-Mail Removed)...
> Does anyone know where to find explanations for the errors
> contained in the userenv.log? I have a few PCs that are
> not applying Group Policy, and their userenv.log files are
> full of messages like this :
>
> USERENV(b8.a0) 10:15:34:656 MyGetUserName: GetUserNameEx
> failed with 1355.
>
> and
>
> USERENV(65c.654) 12:17:39:671 RegisterGPNotification:
> CreateEvent failed with 5
>
> plus lots more.

net helpmsg doesn't work on error numbers like b8.a0, and
I've got the troubleshooting Group Policy document in
front of me (I have been using this document for months!),
but it doesn't seem to throw much light on things.

Hmmmmmmmmmmm



>-----Original Message-----
>Does anyone know where to find explanations for the
errors
>contained in the userenv.log? I have a few PCs that are
>not applying Group Policy, and their userenv.log files
are
>full of messages like this :
>
>USERENV(b8.a0) 10:15:34:656 MyGetUserName: GetUserNameEx
>failed with 1355.
>
>and
>
>USERENV(65c.654) 12:17:39:671 RegisterGPNotification:
>CreateEvent failed with 5
>
>plus lots more.
>.
>

Thanks......much obliged for your help.

Gerry




>-----Original Message-----
>you can type net helpmsg # and it will give you the
description of the error.
>
>1355 = The specified domain either does not exist or
could not be contacted.
>
>5 = Access denied.
>
>Start with making sure that DNS is setup properly. The
easiest setup is point the DC to itself and the client to
the DC for DNS. Reboot the DC to ensure all the records
get registered. Run ipconfig /flushdns on the client
machine.
>
>1355 is usually because of a DNS problem.
>.
>