AT Command Fails to Run Some Applications

Last reviewed: May 14, 1997
Article ID: Q113073
The information in this article applies to:
  • Microsoft Windows NT operating system version 3.1
  • Microsoft Windows NT Advanced Server version 3.1

SYMPTOMS

If you have either a batch file or a command file that contains OS/2 commands and uses the Schedule service to run, OS/2 commands in the file are not executed.

This applies to both the AT.EXE scheduler that comes with Windows NT and the WINAT.EXE scheduler that comes with the Windows NT Resource Kit.

CAUSE

By default, the schedule service runs under the System account. If you change the schedule service to use a different logon account, OS/2 commands become operational, but Win32 commands do not function properly. Note that this behavior only applies to batch or command files being scheduled, and does not apply to interactive usage.

RESOLUTION

You can change the account that the schedule service uses by doing the following:

  1. From the Control Panel window, choose the Services icon.

  2. Select the Schedule service.

  3. Choose the Startup button.

  4. Change the Log On As account from System to the account of your choice.

  5. Choose OK to keep your selection.

At this time, there is no workaround to run both types of commands in a single, scheduled batch file or command file.

STATUS

Microsoft has confirmed this to be a problem in Windows NT and Windows NT Advanced Server version 3.1. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words: prodnt
Keywords : kbbug3.10 kbtool ntutil
Version : 3.1
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 14, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.