Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NT server batch file

Status
Not open for further replies.
Mar 5, 2002
292
US
Hello all,

The batch file on our server ( NT 4.0 ) maps 7 drives, updates the time, and checks for anti-virus software. On a few machines, the batch file will fail and we get one of these two errors. This doesn't happen a lot, but does sometimes. It seems like it only happens to the GM too :O(

"...A required .DLL file V:VP_log32.exe was not found"
"...A required .DLL file V:Sleep.exe was not found"

It seems like the batch file will run, then hang like there is too much traffic or something.

At first I was thinking that the pc might be causing this because this persone has tons starting up on his notebook. His resources are 67% without anything starting.

Do you think it's the nic? This has happneded to me once though. I'm not sure what could cause this.

Thanks for any suggestions.
 
Is it just that V: drive that gets the error? If so, is he mapped properly for it? You can only map to the root in Win95/98/ME/NT

 
Rtaylor,

The V drive isn't even in the server batch file. Sometimes this happens, but irritates the user. The person usually has to reboot because the batch file will just hang. I believe after they get the message, the pc goes on into windows.

It seems like something is preventing the batch file from running. Is it network traffic or maybe the pc's network card. I'm not sure what's up. Thanks for helping.

[spin]
 
Can we see this batch file? a couple of things come to mind...the path v:sleep.exe is invalid. Also - why does is it calling a .dll file as sleep.EXE?

Anyway - you may want to add some time delay to this batch file if too much is starting all at once.

Lets see the batch file :)
Pbxman
Systems Administrator

Please let Tek-Tips members know their posts were helpful.
 
We had a similiar problem here, turns out the unit was trying to make the connection before the network drive was connected, changing the startup sequence of the software packages cured it. If not, Those two files aren't native to NT, are you sure the user didn't try to install a program they shouldn't have or a bad install that left these files there? I don't know how many laptops you have configured there but if I were you I'd configure one from scratch and then use Ghost to backup the image to a bootable cd so that in the future you can reconfigure units on the fly. By the way you can map TWO levels deep in NT, NOT just to the root.
 
MacMan,

Thanks for the reply. The user that was having the problems no longer works here. One good thing, he took his laptop with him. I think his laptop was causing the problem. We have no control over what some users install on their notebooks, you know, the big dogs way up in MGMT. They can do whatever they want, then it's my job to figure out why things don't work when I tell them all that junk is messing up their pc and causing the "standard" software we use not to work right, they get mad at me??
 
Yea, I know EXACTLY what you mean, I think the real reason they get mad is because not only did they not know what they were doing when they screwed it up, NOW somebody else knows how dumb they were too.

Good Luck
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top