Also, if the E: drive is on an external array or is clustered with another
server, it may not have been available through the boot process yet when
the scheduler service was started. If so, the scheduler wouldn't recognize
the drive until the scheduler was stopped and restarted.

At 03:58 PM 10/11/99 -0500, you wrote:
>        I was looking at the out put of a q event * * and noticed an NT
>client as
>listed as "missed".  I contacted the NT administrator responsible fo rhte
>machine and he said the scheduler was running.  The dsmsched.err file yields
>the following errors:
>
>
>09/23/1999 17:03:18 ANS1134E Drive E: is an invalid drive specification
>09/23/1999 17:03:18 ANS1512E Scheduled event 'NTSERVER30' failed.  Return
>code = 4.
>10/11/1999 13:43:13 ntConsoleEventHandler(): Caught Logoff console event .
>10/11/1999 13:43:13 ntConsoleEventHandler(): Process Detached.
>
>     The NT admin says the machine was not rebooted and has been running
>continously through out the time period.  Has anyone run into this before?
>
>Regards,
>[------------------------------------]
>  Jason E. Thomas
>  syne7 AT yahoo DOT com / ronin91 AT home DOT com
>  Systems Engineer
>  Dickens Services Group [DSG]
>[------------------------------------]
>
>
>__________________________________________________
>Do You Yahoo!?
>Bid and sell for free at http://auctions.yahoo.com