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 sp_add_jobstep.

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:

Was @subsystem ='ACTIVESCRIPTING' in fact secretly removed in an undocumented way, or did we miss an installable component that enables it?

  • 2
    Added a comment on Microsoft's sp_add_jobstep page noting the discontinuing of ACTIVESCRIPTING as of SQL 2016. Apr 11 '17 at 15:07

Discontinued Database Engine Functionality in SQL Server 2016 indicates

ActiveX subsytem is discontinued. Use command line or PowerShell scripts instead.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.