Link to home
Start Free TrialLog in
Avatar of infranetsupport
infranetsupport

asked on

startup batch files causing errors

I am getting this error message in my Event log.

Event Type: Error
Event Source: UserInit
Event Category: None
Event ID: 1000
Date:  6/17/2008
Time:  8:22:29 AM
User:  N/A
Computer: ACTDC1
Description:
Could not execute the following script \\actserver\NETLOGON\EmrImages.bat. No network provider accepted the given network path.
.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

What is calling these batch files to run? I dont have these batch files anymore and something is still trying to find them.  Where could i find the script that is calling them? I looked in my GPOs and I couldnt find any, nor were they in my \sysvol folder.
ASKER CERTIFIED SOLUTION
Avatar of lnkevin
lnkevin
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of infranetsupport
infranetsupport

ASKER

i checked there and the logon scripts that are there are not the same ones as the one being called.
I did check those bat files and theres no mention of the emrimages.bat file.
Does it happen in one or multiple account?

I suggest you to delete the current Login policy and recreate it in your GPO. For some reason, the current rule get corrupted.

K
Its happening for every user. and only a few users actually have a login policy and its for a printer.
no ideas anyone? i saw an EE questions exactly like the one i had posted but the fix was a link to a technet article that didnt work anymore.
Did you check File and Printer share option in the NIC properties to make sure it is checked?

K
it doesnt have anything to do with that option.  And It is checeked
something is calling scripts to run and showing errors on my EV and i just need to find out what it is.
Because you change your DC, the old login script still have some where in you policy. If you recreate the rule in GPO for login script it will fix your issue.

K