Scripts failed due to the error listed below, file not found

[synodontis]

I have several computers that have an issue processing a startup GPO script. The gpo works on most machines, but some for some reason have stopped processing any script related policies. The client portion of group policy scripting seems broken. The issue was more widespread at one point and I opened a call with PSS that led us to the %windir%\system32\grouppolicy\gpt.ini file which had extra values, possibly related to a previous existence of the Novell client. I cleaned up that file via logon script but still, some of the machines haven't woke back up. I have tried sfc /scannow, I have tried re-registering the gptext.dll, I am almost at wits end.

Has anyone had any experience with this type issue?

I am working with an AD 2003 environment, the operating systems of the clients are xp sp1 and sp2. It's a very vanilla policy, but as I said, the issue isn't the policy, it's the processing on the client that is broken. RSOP will list current date and times for all except scripting and scripting has an old date/time and nothing since then. gpupdate /force does not kick it.

[JerryC]

Try re-creating the GPO from scratch and then see if those devices "wake up"...

If that fails, activate verbose UserEnv logging and look at the results to see if there are any explicitly noted errors when the scripting client extension runs. The log is located at C:\Windows\Debug\Usermode\UserEnv.Log

[code:1]Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Wind ows NT\CurrentVersion\Winlogon]
"UserenvDebugLevel"=dword:0003000 2[/code]
Set it back to a default value of 1 when completed...

[synodontis]

Thanks for the response Jerry...

I have even gone so far as to create several startup scripts and they are all the same... The machine has rights to get to sysvol and the policy directory. I cannot see anything obviously wrong via userenv logging...

But you look in rsop and see this

Component Status
Component Name Status Last Process Time
Group Policy Infrastructure Success 8/10/2006 6:42:33 AM
EFS recovery Success (no data) 8/7/2006 9:01:03 PM
Registry Success 8/7/2006 9:00:46 PM
Scripts Failed 7/10/2006 8:01:00 AM
Scripts failed due to the error listed below.

The system cannot find the file specified.

Additional information may have been logged. Review the Policy Events tab in the console or the application event log for events between 7/10/2006 8:01:00 AM and 7/10/2006 8:01:00 AM.

[JerryC]

As noted in the systems response, what's in your Application Event log at that time?