Logon script suddenly throwing up error

[Andie]

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!!!

[ICTNUT]

Have a look at: Code 8007007B - A filename, directory name or volume label syntax is incorrect.

also: http://www.computerperformance.co.uk/Logon/code/

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 :-)

[timzim]

Would help to see the script since the error refers to a particular line.

[Geoff]

Can you post the script please?

[DrPerceptron]

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 :-)

If you scroll to the bottom on the bulk of non-cached pages, you can see the answers now...

You could register as an expert I think and you can just view the answers normally.

[Andie]

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...

[Andie]

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.

[mac_shinobi]

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

[Andie]

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

I think I'll give it a go tomorrow, thanks . Will let you know if it fixes it.

[Andie]

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.

[mac_shinobi]

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!

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)

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.

Because ................. that would be too easy