Migrating our database from SQL Server 2012 to 2016, we can't recreate an SQL Agent job that involves an ActiveX Scripting step written in VBScript.
The error message suggests that
'ACTIVESCRIPTING' is not an allowed value for the
@subsystem parameter of
I know ActiveX Scripting is marked as "will be removed in a future version of SQL Server". However I cannot see anything about it actually being removed in this version of SQL Server.
SQL Server documentation seems to suggest it is still available in SQL Server 2016:
- Create an ActiveX Script Job Step (SQL Server 2016)
- Documentation on
sp_add_jobstep, updated in March 2017, still lists
@subsystem ='ACTIVESCRIPTING'as available.
@subsystem ='ACTIVESCRIPTING' in fact secretly removed in an undocumented way, or did we miss an installable component that enables it?