Search

msdb..sp_update_job does not work with Windows (Active Directory) groups as the @owner_login_name by DIMiller

Active

1
0
Sign in
to vote
Type: Bug
ID: 776349
Opened: 1/11/2013 10:03:57 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
I need to be able to change the owner of a particular job to an Active Directory Security Group. It appears the accepted method for doing this is to use the msdb stored procedure sp_update_job. When using a Windows Login as the @owner_login_name parameter, sp_update_job works as expected. However, if you attempt to use an Active Directory Security group (for which a login has been created), you get the following error message:

Msg 14234, Level 16, State 1, Procedure sp_verify_job, Line 197
The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]).
Details (expand)

Product Language

English

Version

SQL Server 2008 R2 SP1

Category

SQL Engine

Operating System

Windows Server 2008 R2 Enterprise

Operating System Language

US English

Steps to Reproduce

- create a SQL Server Login corresponding to an Active Directory security group
- create a SQL Server job with any owner corresponding to a SQL Server Login
- attempt to execute the T-SQL below:

CREATE LOGIN [Domain\Domain Group] FROM WINDOWS;
<create Any_Job>
USE [msdb]
GO
EXEC msdb.dbo.sp_update_job @job_name=N'Any_Job',
        @owner_login_name=N'Domain\Domain Group'

Actual Results

Msg 14234, Level 16, State 1, Procedure sp_verify_job, Line 197
The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]).

Expected Results

Command(s) completed successfully.

Platform

X64

Virtualization

Other (e.g. VM Ware, specify in Description)
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 1/15/2013 at 10:25 AM
Hi,

Thank you for reporting this issue. We will take a look on it and let you know what is the outcome.
Again, thank you very much for finding time to report this issue.

Evgeny Krivosheev,
SQL Server Program Manager
Sign in to post a workaround.