Windows Thread, Logon script suddenly throwing up error in Technical; I've been using a couple of logon scripts for ages without problem. Now one client is throwing up a Windows ...
1st June 2009, 12:22 PM #1
Logon script suddenly throwing up error
I've been using a couple of logon scripts for ages without problem. Now one client is throwing up a Windows Script Host error code 8007007B, for all users including admin. The script connects shares and printers to the clients, and I haven't changed anything in the scripts recently. Moreover, the script works fine on other machines in the Suite. Only one printer is affected, and is not connected as a result. The only fairly recent change is that the clients have been updated to SP3 (XP Prof) and the server updated to SP2, but other updated clients are unaffected. I did google the error code, but the only mentions of similar problems were in experts exchange, which I need to pay for to access the actual solution! Server is Windows 2003. I've attached a screenshot of the error message, but it's lying!!!
1st June 2009, 12:40 PM #2
Have a look at: Code 8007007B - A filename, directory name or volume label syntax is incorrect.
As far as experts exchange is concerned when you google it make sure you open the cached version and scroll to the bottom the solution is visible to all :-)
Last edited by ICTNUT; 1st June 2009 at 12:43 PM.
1st June 2009, 12:40 PM #3
Would help to see the script since the error refers to a particular line.
1st June 2009, 12:56 PM #4
Can you post the script please?
1st June 2009, 01:38 PM #5
If you scroll to the bottom on the bulk of non-cached pages, you can see the answers now...
Originally Posted by ICTNUT
You could register as an expert I think and you can just view the answers normally.
1st June 2009, 03:14 PM #6
Thanks for the help with getting at the solution on experts exchange (useful tip!). The suggestion that looked likeliest suggests possible connection issues, and adds to the printer script by getting the connection to try 10 times witha 2 second pause. However, my problem is only on the one machine and is not intermittent. And the printer seems to connect despite the error when logged on as administrator...
2nd June 2009, 08:09 AM #7
OK, here are the scripts. I didn't think I needed to post these as they have been working fine for months, and they still are working fine on the rest of the (identical) clients in the IT Suite. Both of these scripts are throwing up the same error message on just this one machine (so far anyway!). These are not new scripts, and the offending line (in the IT Printing section, and ending in ColLaser) is repeated elsewhere for other machines in other locations and doesn't throw any errors either. Also I have now noticed that although the error comes up when logged in as domain admin, the printer is still available - not so for other users. The only recent change to the machines is an update to XP SP3.
2nd June 2009, 08:40 AM #8
maybe on this one machine un install and re install SP3 ?
That or re image it and then put SP3 on the machine - seeing as its only one machine and not all of them
Thanks to mac_shinobi from:
2nd June 2009, 10:18 PM #9
I think I'll give it a go tomorrow, thanks . Will let you know if it fixes it.
Originally Posted by mac_shinobi
3rd June 2009, 11:14 AM #10
I uninstalled SP3 and just did a bit of testing, logging in as admin and other users - no scripting error now and printer available. Then I reinstalled SP3. Again, logged in as admin and other users - no scripting error and printer now available. This will be one of those little IT mysteries as to why the first install caused this problem, but it's fixed so I'm happy. Thanks!
P.S. Uh, oh. Just found another client with same problem!! Why don't users report these things???!!! Now I'm going to have to check them all.
Last edited by Andie; 3rd June 2009 at 11:23 AM.
Reason: Postscript added.
3rd June 2009, 12:42 PM #11
Good to hear it and not sure why its done that - maybe did not copy a few of the files over correctly or they may of gotten corrupted some how (shrugs)
Originally Posted by Andie
Because ................. that would be too easy
Originally Posted by Andie
9th May 2011, 11:26 AM #12
Doing it again!
Sorry for resurrecting my old post, but this has reared it's ugly head again in a different situation.
We have a set of laptops in each class now, new laptops but running XP Professional SP3. The SP3 is part of the original Windows install on these, and not an update. Been fine for a good few months.
A teacher has given me three laptops which are now unable to print to the colour laser printer (HP Colour LaserJet 2605dn). Same printer as the original posting. Booted the laptops and they are all showing the scripting error. If I log in as a pupil, the colour laser printer is not found in the printers list. If I log in as domain admin, I still get the scripting error but the printer is shown and I can print a test page fine.
The script is the same as attached higher up. It is just used to allocate the correct set of printers to the workstation at login. We have 31 desktops and 98 laptops, and, as far as I know, only these three have this issue - so the script can't be the problem.
Server is Windows Server 2003.
Other printers are fine.
I can't uninstall SP3 update, as it isn't an update. I would have to reimage the laptops. If this problem occurs on other machines, this could become a real headache.
9th May 2011, 01:49 PM #13
can you manually map that printer by hand?
can you ping it.. from the pc you have the problem mapping from
have you tried a basic script to test
Dim netPrinter, UNCpath
UNCpath = "\\ms-lnm-server\ColLaser"
Set netPrinter = CreateObject("WScript.Network")
WScript.Echo "Your printer is mapped from : " & UNCpath
' End of example VBScript
or change script to use con2prt.exe
9th May 2011, 03:25 PM #14
The printer is there when logged in as administrator and I can print to it, even though I get the script error. The script has been running fine for all users for months and still runs fine for all the other identical laptops. It is just these three that, all of a sudden, are throwing up script errors and preventing ordinary users from connecting to the printer. I can run the test script, but I don't understand what this helps with. Sorry if I am being thick.
Originally Posted by Cools
9th May 2011, 03:37 PM #15
its just to check the connection to the printer..
as student.. some thing has changed even if you dont know what it is..
login in as admin is pointless as it's like having a master key to the school..
the script is to just test the connection as a student on a student GPO.. its saying it cant find it... i could say theres a dns error but not knowing what its set up like..
just try it for entertainment.. i have the same argument with virgin when things dont work.. and they say "Well everyone eles is ok in the street" it does not help.
By karldenton in forum Windows
Last Post: 25th March 2009, 12:05 PM
By indie in forum Windows
Last Post: 14th September 2007, 11:34 AM
By Galway in forum Windows
Last Post: 29th August 2007, 11:00 AM
By ajbritton in forum Windows
Last Post: 19th June 2006, 09:47 AM
By tarquel in forum Windows
Last Post: 14th June 2006, 09:07 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)