Scheduler Doesn't Update its Environment Variable

 Last reviewed: June 12, 1995
Article ID: Q131229
The information in this article applies to:
  • Microsoft Windows NT operating system version 3.1
  • Microsoft Windows NT Advanced Server version 3.1
  • Microsoft Windows NT Workstation versions 3.5 and 3.51
  • Microsoft Windows NT Server versions 3.5 and 3.51

SYMPTOMS

When you change an environment variable in the Control Panel System dialog box, the Scheduler service (AT command) doesn't recognize the change.

CAUSE

Program Manager and Control Panel System get the environment variables from the registry. The scheduler service inherits the environment from the service controller, which obtains the environment only once, at boot.

WORKAROUND

To work around this problem, shutdown and restart Windows NT.

STATUS

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

KBCategory: kbtool kbenv kbbug3.10 kbbug3.50 kbbug3.51
KBSubcategory: ntutil
Additional reference words: 3.10 3.50 3.51 prodnt

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: June 12, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.