FIX: SQL Server Jobs That Are Owned by Non-sysadmin Users May Not Start

Article translations Article translations
Article ID: 825042 - View products that this article applies to.
BUG #: 469844 (SHILOH_BUGS)
BUG #: 469845 (SHILOH_BUGS)
Expand all | Collapse all

On This Page

SYMPTOMS

SQL Server jobs that are owned by non-sysadmin users may not start if all the following conditions are true. There are two cases where this problem may occur.

Case 1

The problem may occur in this case if all the following conditions are true:
  • SQL Server is installed on a Microsoft Windows 2000 or later Active Directory directory service domain. For example, the domain name is ADDom.
  • The owner of the job is a non-admin user in the domain. For example, the user is ADDom\User.
  • The owner of the job is a member of only the domain local groups in this domain. For example, the user is a member of ADDom\ADDomDLG.
  • The owner can access the computer that is running SQL Server by using a domain local group login. For example, the group login for the computer that is running SQL Server is ADDom\ADDomDLG.
  • The group login does not have sysadmin administrative credentials on the computer that is running SQL Server.
  • The group login has sufficient administrative credentials to create and execute a job. For example, the group login is part of all roles except the System Administrators role.
  • The user owns a job. For example, the name of this job is TestJob.
You may see the following message in the job history:
The owner (ADDOM\User) of job TestJob does not have server access

Case 2

The problem may occur in this case if all the following conditions are true:
  • SQL Server is installed on a Windows 2000 or later Active Directory domain. For example, the domain name is ADDom.
  • The owner of the job is from one domain and SQL Server is installed on another domain. For example, the other domain is NT4Dom, and the user is NT4Dom\User.
  • The owner of the job is a member of a domain local group in the Active Directory domain. For example, the name of the domain local group is ADDomDLG).
  • The owner can access the computer that is running SQL Server by using a domain local group login. For example, the group login for the computer that is running SQL Server is ADDom\ADDomDLG).
  • The group login does not have sysadmin administrative credentials on the computer that is running SQL Server.
  • The group login has sufficient administrative credentials to create and execute a job. For example, the group login is part of all roles except the System Administrators role.
  • The user owns a job. For example, the name of this job is TestJob.
You may see the following message in the job history:
The owner (NT4DOM\User) of job TestJob does not have server access

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack

Hotfix information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version            Size    File name
   -------------------------------------------------------------------
   31-May-2003  18:45  2000.80.818.0      78,400  Console.exe      
   25-Jun-2003  01:01  2000.80.818.0      33,340  Dbmslpcn.dll     
   25-Apr-2003  02:12                    786,432  Distmdl.ldf
   25-Apr-2003  02:12                  2,359,296  Distmdl.mdf
   30-Jan-2003  01:55                        180  Drop_repl_hotfix.sql
   23-Jun-2003  22:40  2000.80.837.0   1,557,052  Dtsui.dll        
   23-Jun-2003  22:40  2000.80.837.0     639,552  Dtswiz.dll       
   24-Apr-2003  02:51                    747,927  Instdist.sql
   03-May-2003  01:56                      1,581  Inst_repl_hotfix.sql
   08-Feb-2003  06:40  2000.80.765.0      90,692  Msgprox.dll      
   01-Apr-2003  02:07                      1,873  Odsole.sql
   05-Apr-2003  01:46  2000.80.800.0      62,024  Odsole70.dll     
   07-May-2003  20:41  2000.80.819.0      25,144  Opends60.dll     
   02-Apr-2003  21:48  2000.80.796.0      57,904  Osql.exe         
   02-Apr-2003  23:15  2000.80.797.0     279,104  Pfutil80.dll     
   22-May-2003  22:57                     19,195  Qfe469571.sql
   11-Jul-2003  17:04                  1,084,147  Replmerg.sql
   04-Apr-2003  21:53  2000.80.798.0     221,768  Replprov.dll     
   08-Feb-2003  06:40  2000.80.765.0     307,784  Replrec.dll      
   11-Jul-2003  16:56                  1,085,925  Replsys.sql
   01-Jun-2003  01:01  2000.80.818.0     492,096  Semobj.dll       
   31-May-2003  18:27  2000.80.818.0     172,032  Semobj.rll
   29-May-2003  00:29                    115,944  Sp3_serv_uni.sql
   01-Jun-2003  01:01  2000.80.818.0   4,215,360  Sqldmo.dll       
   07-Apr-2003  17:44                     25,172  Sqldumper.exe    
   19-Mar-2003  18:20  2000.80.789.0      28,672  Sqlevn70.rll
   02-Jul-2003  00:18  2000.80.834.0     180,736  Sqlmap70.dll     
   08-Feb-2003  06:40  2000.80.765.0      57,920  Sqlrepss.dll     
   10-Jul-2003  22:00  2000.80.840.0   7,553,105  Sqlservr.exe     
   08-Feb-2003  06:40  2000.80.765.0      45,644  Sqlvdi.dll       
   25-Jun-2003  01:01  2000.80.818.0      33,340  Ssmslpcn.dll     
   01-Jun-2003  01:01  2000.80.818.0      82,492  Ssnetlib.dll     
   01-Jun-2003  01:01  2000.80.818.0      25,148  Ssnmpn70.dll     
   01-Jun-2003  01:01  2000.80.818.0     158,240  Svrnetcn.dll     
   31-May-2003  18:59  2000.80.818.0      76,416  Svrnetcn.exe     
   30-Apr-2003  23:52  2000.80.816.0      45,132  Ums.dll          
   02-Jul-2003  00:19  2000.80.834.0      98,816  Xpweb70.dll 
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.

MORE INFORMATION

To apply this hotfix on a computer that is running Windows 2000 Server, the computer must be running Windows 2000 Service Pack 4 (SP4) or later because this SQL Server fix relies on a new AuthZ API that was introduced in Windows 2000 SP4 and later. This API is not available in Windows 2000 Server SP3 and earlier. For more information about this new API, see the Platform SDK (Security) or visit the following Microsoft Web site:
http://msdn.microsoft.com
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 825042 - Last Review: November 2, 2007 - Revision: 7.3
APPLIES TO
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000, Workgroup Edition
  • Microsoft SQL Server 2000 Desktop Engine (Windows)
  • Microsoft SQL Server 2000 Enterprise Edition 64-bit
Keywords: 
kbhotfixserver kbqfe kbqfe kbsqlserv2000presp4fix kbfix kbbug KB825042

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com