Re: Group Policy Script error

From: Roger Abell (mvpNOSpam_at_asu.edu)
Date: 01/29/05


Date: Fri, 28 Jan 2005 23:29:22 -0700

Well, you are right that it is a file not found issue while
doing a backgroup application of computer policy
http://support.microsoft.com/default.aspx?scid=kb;en-us;312164
but you are only guessing as to what file.
You may need to collect extended logging to know more
http://support.microsoft.com/kb/245422
(remember to shut it back down)

-- 
Roger Abell
Microsoft MVP (Windows  Security)
MCSE (W2k3,W2k,Nt4)  MCDBA
"DavieC" <DavieC@discussions.microsoft.com> wrote in message
news:8A6CC462-CEDF-4BBB-B011-DDDE4808B369@microsoft.com...
> Source: Userenv
> Category: None
> Event ID: 1000
> Type: Error
>
> I had a look on eventid.net and spotted a Flags(17) returned code (3),
> security.  This pointed me on to an article XP help found regarding
> re-registering DLLs.  I re-registered the DLLs but it didn't fix it.
>
> I've found some more information though, it seems to be related to the
> Machine Configuration of my GPO's, as running secedit /refreshpolicy
> machine_policy generates the error but user_policy doesn't.  I'm thinking
it
> must therefore be a Startup script issue.  On eventid.net there was a note
> about running "net helpmsg 2" which returns: The system cannot find the
file
> specified
>
> I believe it may be the default domain policy which has somehow retained a
> link to a deleted startup script; the problem is when I check the scripts
on
> the domain policy nothing is listed.
>
>
>
>
> "Mark" wrote:
>
> > What are the Event IDs?  You could try searching at www.eventid.net and
see
> > if there is any information there.
> >
> > Mark
> > "DavieC" <DavieC@discussions.microsoft.com> wrote in message
> > news:033B227F-0FDD-44D8-9037-CBC1535BBB62@microsoft.com...
> > > Hi,
> > >
> > > I receive the following error from my DC every 5 minutes, and from my
> > > member
> > > servers every 2 hours:
> > >
> > > The Group Policy client-side extension Scripts was passed flags (17)
and
> > > returned a failure status code of (2).
> > >
> > > For more information, see Help and Support Center at
> > > http://go.microsoft.com/fwlink/events.asp.
> > >
> > > Clicking on the link tells me there's no information available.  The
only
> > > change I've recently made is to install the update:
> > >
> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;842933
> > >
> > > so my 2K AD supports XP policies (which it now does correctly).  I'm
> > > guessing it's related to a Script somehow, does any one have any
> > > experience
> > > of this or be able to point me in the right direction?
> > >
> > > Thanks in advance
> >
> >
> >


Relevant Pages

  • Re: Modem on notebooks with Windows 2000 Prof
    ... I can imagine a startup script based solution, ... > Hi Roger. ... > If you can't think of a technical solution then I believe there is not ... >>> I don't know of a way to do such with Group Policy. ...
    (microsoft.public.win2000.security)
  • Re: EventID 1054 from Userenv for startup script
    ... startup script policy. ... I see a problem with the order in which the policies are applied. ... Those two contain the requirement to "Wait for network before logging ... Often, the startup script won't run, but if I run it manually, than ...
    (microsoft.public.windows.group_policy)
  • Re: PushPrinterConnection
    ... rsop.msc confirms that the GPO is a startup script with the correct GPO name ... If the policy is linked correctly and rsop.msc shows on a "problematic" machine that everything is okay, I'd check the eventlog and probably the userenv.log file to see what they come up with. ... I keep recommending leaving that alone and deploying the printers with good-old scripts that "map" the printers. ...
    (microsoft.public.windows.group_policy)
  • Re: Mapping network devices
    ... > instalation via software policy. ... Computers" permission to read/write in a shared folder and this allows my ... StartUp script to write to a log file in the shared folder. ...
    (microsoft.public.windows.server.scripting)
  • Re: Borland weblog policy posted
    ... Rather than leaving everyone guessing, I decided to post our blog ... Also the policy is a very well thought out one imo ...
    (borland.public.delphi.non-technical)