GoldenWonder Posted November 18, 2008 Posted November 18, 2008 (edited) On our network we run several VBS scripts on machine startup.These clear old files, install Quicktime etc and have been working on over 500 PCs for several years. Occasionally, one PC will start to generate an error for each one of these vbs scripts: Event Type: Error Event Source: UserInit Event Category: None Event ID: 1000 Date: 06/11/2008 Time: 14:11:11 User: N/A Computer: pc_name Description: Could not execute the following script delprofile.vbs. . I have tried everything to resolve this, and in the last 2 years have only found one resolution - reinstall windows! These scripts work fine when run directly on the failing PC, and work everywhere else! The scripts don't generate any errors, and even if I reduce the scripts down to just one it still generates the error. No matter whether I run 1 or all 3 I get the corresponding number of errors. The only thing I can see that is common is that they are all VBS scripts - other parts of the startup batch file are running (registry hacks etc) We do have Software Restriction Policies applied to users (never Machines) and I'm wondering if this is corrupting somehow for vbs scripts- other scripts (.bat etc) are still running OK. I'm at a loss now, any suggestions gratefully received? Edited November 18, 2008 by GoldenWonder
mjs_mjs Posted September 10, 2009 Posted September 10, 2009 if i remember correctly there is a program that runs the VBS script. i think its windows scripting host on the clients. i dunno if it's possible to uninstall it then reinstall it? it's a shot in the dark.
srochford Posted September 10, 2009 Posted September 10, 2009 Are you saying that if you type "delprofile.vbs" on a "faulty" machine that the script runs? If you type "cscript delprofile.vbs" does it run? What about "wscript delprofile.vbs" As Matt says, it's Windows scripting host which runs a .vbs file and there are two versions (I think of them as the console version and the Windows version) - I'm wondering if one is Ok but the other is faulty. You could try following this MS KB article - When I run a script in Windows Script, I receive an error message: "Library not registered" to see if that helps. If typing "delprofile.vbs" doesn't work but "cscript delprofile.vbs" does work then you could always change the batch file on the server so that it calls your script like that - it's actually not a bad idea anyway because you avoid problems where some machine might be using wscript as default and others using cscript
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now