Subscribe to Windows IT Pro
April 22, 2002 12:00 AM

Troubleshooting the AT Command

Windows IT Pro
InstantDoc ID #24569
Rating: (0)

I have a strange problem with the Windows NT AT command. The command worked until I loaded Microsoft SQL Server 7.0 on my NT server. Now the command won't run at all. What happened?

I don't know of any incompatibilities between SQL Server and the AT scheduling service, but my guess is that SQL Server installed a task scheduler that replaced the default NT Schedule service. Open the Control Panel Services applet. If you can't find the Schedule service and instead see the SQL Server scheduling service, this switch is the culprit.

The easiest and safest solution is to use the Control Panel Add/Remove Programs applet to remove the new scheduler. Sometimes, though, this action won't restore the NT Schedule service. In that case, you need to follow a more volatile solution: Edit the registry.

First, cross your fingers and be sure to update your Emergency Repair Disk (ERD) before you start tweaking. Then, go to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Schedule subkey and change the ErrorControl, ImagePath, ObjectName, and Start values as Table 1, page 96, specifies. (Leave any other existing values alone.)

Related Content:

ARTICLE TOOLS

Comments
  • John Eccles
    10 years ago
    Apr 29, 2002

    This isn't so much a problem with SQL7 as it is with IE5 which is required to install SQL 7. It replaces the Schedule service with "Task Scheduler". One is ATSvc.exe and the other is MSTask.exe. MSTask cannot be run under a user account and must be set as LocalSystem. It also is incompatible with NT4's Schedule service (can't run jobs on a TS-enabled machine to a Schedule running machine).
    Task Scheduler is not a removable option of IE5's installation. It is _always_ installed when IE5 is installed.

    You can revert to the ATSvc.exe version and get rid of your problems by running:
    rundll32 advpack.dll,LaunchINFSection %SystemRoot%\\INF\\mstask.inf,Uninstall.NT

    This might work in Win2K, but you need to copy atsvc.exe from an NT4SP6 machine.

    I've also seen problems where a RunAs registry setting has messed up the Task Scheduler so it can't create jobs.
    Check HKEY_CLASSES_ROOT\\CLSID\\{D6277990-4C6A-11CF-8D87-00AA0060F5BF} and delete any value named RunAs.

You must log on before posting a comment.

Are you a new visitor? Register Here

advertisement

advertisement

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.