Home Dashboard Directory Help

Bug in SQL Server Agent jobs by exxoid


 as Won't Fix Help for as Won't Fix

Sign in
to vote
Type: Bug
ID: 788410
Opened: 5/22/2013 10:34:29 AM
Access Restriction: Public
User(s) can reproduce this bug


We are running SQL 2012 (recently upgraded) and I ran into a bug transfering one of my SQL Agent Jobs.

To narrow down what was causing the issue, I manually started adding the failing job on SQL 2012, re-creating the Job steps from scratch.

It failed for a step of SQL Server Analysis Services Command type, which basically executes a Full Process of Cube.

The issue was, in this job step under advanced options, if we check "Include step output in history" and apply the settings SQL fails with an error message of..

Alter failed for JobStep 'Process cube'. (Microsoft.SqlServer.Smo)
The @flags parameter is not valid for a job step of type 'ANALYSISCOMMAND'. (Microsoft SQL Server, Error: 14545)

The script actions of this step is:

USE [msdb]
EXEC msdb.dbo.sp_update_jobstep @job_id=N'aa50a3f3-698d-4678-894f-e956d35542ca', @step_id=9 ,

Now once we remove the "Include step output in history", everything works OK.

I think the issue is with "@flags=4" which gets added by ticking the "Include step output in history" for SQL Server Analysis Services Command" job type.

This check works for other step types, such as SQL Server Integration Services Package or Transact-SQL script (T-SQL) steps.

This is a bug.
Sign in to post a comment.
Posted by Microsoft on 6/25/2013 at 12:22 PM
Hello exxoid. The error message you're encountering is stating that you should have the check box for Include Step Output in History unmarked for Analysis Service Command jobs, as it does not function for this type of command. The UI change necessary to keep this from happening is out of the scope for a PCU item, but we'll keep it in mind moving forward. Sorry this got resolved without your reply being posted. I was drafting your reply when you emailed me about it. Usually, customers don't get back to us within three minutes of resolution.

-Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)
Posted by exxoid on 6/25/2013 at 12:03 PM
Why was this set to "Won't Fix" without any comment as to why the bug was closed?
Posted by exxoid on 5/23/2013 at 7:00 AM
Thanks, I am interesting to see if this indeed is a confirmed bug.
Posted by Microsoft on 5/22/2013 at 4:42 PM
Hello exxoid. Thank you for bringing this to our attention. We really do appreciate the feedback. We’ll investigate and get back to you. -Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)
Sign in to post a workaround.