SQL Server 2017维护计划向导调度器失效，点击更改计划报错

Hey there, let's work through this annoying error you're hitting when trying to adjust the maintenance plan schedule in SSMS 17.6 on Windows Server 2016. This is a common bug with a few straightforward fixes—let's dive in:

• Run SSMS as Administrator
  Right-click the SSMS shortcut and select Run as administrator. A lot of the time, insufficient permissions prevent the schedule component from initializing properly. Also, make sure your SQL login has the sysadmin server role—maintenance plans require elevated privileges to interact with scheduling tools.

• Repair or Update SSMS

  1. Open Control Panel → Programs and Features, find Microsoft SQL Server Management Studio 17.6.
  2. Right-click it, select Change, then choose the Repair option. This will reinstall any corrupted SqlMgmt or UI-related components.
  3. If repair doesn't work, upgrade to the latest 17.x SSMS version (17.9.1 is the final release in this branch). Uninstall 17.6 first, then install the newer version—Microsoft patched many UI bugs in later updates.

• Verify SQL Server Agent is Running
  Maintenance plans rely on SQL Server Agent to execute scheduled tasks. Here's how to check:

  1. Press Win+R, type services.msc, and hit Enter.
  2. Locate the SQL Server Agent service. Ensure it's in the Running state.
  3. If it's stopped, right-click and select Start, then set its startup type to Automatic to avoid this issue after server restarts.

• Workaround: Manually Create a Backup Job
  If the wizard keeps failing, skip it and build a backup job directly via SQL Server Agent:

  1. In SSMS, expand SQL Server Agent → Jobs, right-click and select New Job.
  2. On the General tab, name your job (e.g., "Daily Full Database Backup").
  3. Go to the Steps tab, click New. Set Step type to Transact-SQL (T-SQL), select your target database, and paste a backup query like:

     BACKUP DATABASE [YourDatabaseName] TO DISK = N'C:\Backup\YourDatabaseName_Full_$(ESCAPE_SQUOTE(SYSDATETIME))_backup.bak' 
     WITH INIT, COMPRESSION;
     

  4. Switch to the Schedules tab, click New, and configure your desired backup frequency/time.
  5. Save the job, then right-click it and select Start Job at Step... to test it works.

• Check System Dependencies
  Ensure your Windows Server 2016 has the required components:

  • Install the latest .NET Framework 4.6.2 or later (SQL Server 2017 depends on this).
  • Repair or install the Visual C++ 2015-2019 Redistributable (x64) package—SSMS uses these runtime libraries, and missing/corrupted files can cause initialization errors.

内容的提问来源于stack exchange，提问作者Chikli