Report data synchronization job reporting "The process could not be created for step 1 of job 0xD48B2D68116F2040892322888C53C829 (reason: A required privilege is not held by the client)."
Last Updated November 04, 2013
Confirm Windows user rights:
Windows user rights
Typically, the default installation of the operating system gives the Local Administrators Group all the user rights that SQL Server requires to function correctly. Therefore, local Windows NT accounts or domain accounts that have been added to the Local Administrators Group, with the intent of being the startup account for the SQL Server service, have all the user rights that they require. However, we do not recommend that you run SQL Server with these user rights.
For SQL Server 2005, if you do not want the SQL Server or the SQL Server Agent startup account to be a member of the Local Administrators Group, see the "Reviewing Windows NT Rights and Privileges Granted for SQL Server Service Accounts" section in the "Setting Up Windows Service Accounts" topic in SQL Server 2005 Books Online.
For SQL Server 2000, if you do not want the SQL Server or the SQL Server Agent startup account to be a member of the Local Administrators Group, then the startup account for the MSSQLServer service and the SQLServerAgent service (either a local Windows NT account, or a domain Windows NT account) must have these user rights:
Act as Part of the Operating System = SeTcbPrivilege
· Bypass Traverse Checking = SeChangeNotify
· Lock Pages In Memory = SeLockMemory
· Log on as a Batch Job = SeBatchLogonRight
· Log on as a Service = SeServiceLogonRight
· Replace a Process Level Token = SeAssignPrimaryTokenPrivilege