Windows Thread, Logon script suddenly throwing up error in Technical; In your code you have repeated chunks of code regarding your DIMS ie Dim x As Integer or Dim strText ...
9th May 2011, 05:31 PM #16
In your code you have repeated chunks of code regarding your DIMS ie Dim x As Integer or Dim strText and the same for the creation of objects
You only need one and whenever you need to use it again you just change the coding below to refer to one so you could delete the 2nd and 3rd one and only use the first one or however you wanted to do it as you dont need to create the same object with different variable names
-> Set objNetwork = CreateObject("WScript.Network")
Set WSHShell = CreateObject("WScript.Shell")
-> Set WshNetwork = WScript.CreateObject("WScript.Network")
-> Set oNetwork = CreateObject("WScript.Network")
Set clPrinters = WshNetwork.EnumPrinterConnections
Are you able to post the few lines of code where you think its erroring out on ?
Set WshNetwork = WScript.CreateObject("WScript.Network")
Also you have a disconnect sub - which you shouldn't need as when you are mapping the printers there is a for loop that removes all printers before it re adds them.
Last edited by mac_shinobi; 9th May 2011 at 05:34 PM.
IDG Tech News
9th May 2011, 05:34 PM #17
at the end of day its for testing...
not world order..
9th May 2011, 06:02 PM #18
what's that comment all about ?
Originally Posted by Cools
Just trying to tidy the code up so it makes more sense and not repeatdly re create the same objects with different variable names and the same for declaring of variables, its just not needed.
Also could create a sub to take the server name and share name as the rest of the code regarding adding of a printer is the same
10th May 2011, 05:20 PM #19
- Rep Power
You could try updating/reinstallling WSH on the affected machines, i've had a few times where it can become messed up. There should be a download on the MS site ... Type Windows Script Host in the search
12th May 2011, 10:01 PM #20
Progress of sorts
OK, some progress. I spent about an hour looking at this with my secondary school technical support person. Turns out that the colour printer was a bit of a red herring - the current error points to line 138 or 148 depending on which of the scripts runs (logon or stafflogon). This line refers to the Y5Laser. The colour printer is being blocked because in one script it comes after the Y5Laser - in the other script it comes before.
Yes, thanks for the test script. The colour printer mapped and pings fine. The Y5Laser pings, but doesn't map, even as domain admin. We've checked the share name is correct and checked permissions, and checked the IP address of the port.
Originally Posted by Cools
I went and tested a random sample of other laptops that connect to Y5Laser. All are showing the same issue (although no one had logged it). We REMd out the Y5Laser lines in the script, and the scripting error went away. So there appears to be an issue with this particular printer and the curriculum laptops. Staff laptops, which aren't on the domain, print to it fine. Can do a test print direct from the server too. Ran out of time, but next test will be to run a test from a networked desktop in the IT Suite. I'm also going to double check the Y4Laser, as it is same make and model as Y5Laser. Both are HP 2200dn with JetDirect cards.
Last edited by Andie; 12th May 2011 at 10:04 PM.
16th May 2011, 11:04 AM #21
Working on a YR4 laptop and it is fine, with no scripting error and the Y4Laser set as default. BUT just been to deal with a problem in year 3 on a laptop, and when they logged in they were getting a scripting error. This laptop had just been brought to me because it had failed to log on to the network, and had come up with a local profile (no scripting error then). When logged on next time, it had picked up the network, but had a scripting error.
16th May 2011, 03:45 PM #22
Latest Error Message
Can anyone shed any light on this issue?
The laptop I am using shows a printer connection to a printer called Y4Laser, with the printer set to Ready. I am logged in as domain admin. If I double click the printer, I get the attached on screen.
I can't map to this printer from this laptop.
The laptops behind me, using the same wireless connection to the network, can map to the printer with no error messages. All of the laptops in this room with me are in the same AD group and they were all imaged from the same build. The laptops behind me are a random sample from year 4. None have the scripting error. So far, this year group seems to be the only one unaffected by the issues with these laser printers, unless I have been incredibly lucky with my random sample.
I can't work out what the link is.
16th May 2011, 04:50 PM #23
Bad haiku? Poor quality pharmaceuticals?? Solar flare???
Originally Posted by Cools
19th May 2011, 10:28 PM #24
After some more tests, have started a new thread:
Weird: printer mapping issue
Last edited by Andie; 19th May 2011 at 10:33 PM.
By karldenton in forum Windows
Last Post: 25th March 2009, 01:05 PM
By indie in forum Windows
Last Post: 14th September 2007, 12:34 PM
By Galway in forum Windows
Last Post: 29th August 2007, 12:00 PM
By ajbritton in forum Windows
Last Post: 19th June 2006, 10:47 AM
By tarquel in forum Windows
Last Post: 14th June 2006, 10:07 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)