Just a thought, have you tried accessing the machines that your failing on using the event viewer whilst logged on as whatever userid the script runs on?
The reason I ask is I once saw a similar problem with a script accessing stuff on a remote server. The script ran fine under the development account, but when run as a scheduled task on the production machine it would get so far and then hang and have to be killed.
When we went to the actual server (stuck away under lock and key in a remote server room) and switched on the screen, having worked out which combination of switches connected the single screen and keyboard to the right one of 10 or 12 boxes in the room (closet), we discovered that there was a "Invalid logon, try again" dialog sitting on the screen.
The one server (of a couple of hundred) where it kept hanging had a non-standard set of domain permissions.
In reply to Re: more Win32::EventLog oddities
by BrowserUk
in thread more Win32::EventLog oddities
by Reverend Phil
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |