MSSQL_ENG021797
Message Details
Product Name |
SQL Server |
Product Version |
9.0 |
Product Build Number |
9.00.1399.60 |
Event ID |
21797 |
Event Source |
MSSQLSERVER |
Component |
SQL Server Database Engine |
Symbolic Name |
|
Message Text |
'%s' must be a valid Windows Login in the form: 'MACHINE\Login' or 'DOMAIN\Login'. Please see the documentation for '%s'. |
Explanation
This error is raised by the following replication stored procedures if the value specified for the @job_login parameter is null or not valid. This error can occur if a member of the db_owner fixed database role runs scripts from previous versions of SQL Server. The security model has changed in SQL Server 2005, and these scripts must be updated.
- sp_addlogreader_agent (Transact-SQL)
- sp_addqreader_agent (Transact-SQL)
- sp_addpublication_snapshot (Transact-SQL)
- sp_addpushsubscription_agent (Transact-SQL)
- sp_addpullsubscription_agent (Transact-SQL)
- sp_addmergepushsubscription_agent (Transact-SQL)
- sp_addmergepullsubscription_agent (Transact-SQL)
These stored procedures can be executed by a member of the sysadmin fixed server role on the appropriate server or a member of the db_owner fixed database role in the appropriate database. The stored procedures each create an agent job and allow you to specify the Microsoft Windows account under which the agent runs. For users in the sysadmin role, agent jobs are created implicitly even if a Windows account is not specified (if an account is specified, it must be valid); agents run under the context of the SQL Server Agent service account at the appropriate server. Although the account is not required, it is a security best practice to specify a separate account for the agents. For more information, see Replication Agent Security Model.
User Action
Ensure you specify a valid Windows account for the @job_login parameter of each procedure. If you have replication scripts from previous versions of SQL Server, update these scripts to include the stored procedures and parameters required by SQL Server 2005. For more information, see How to: Upgrade Replication Scripts (Replication Transact-SQL Programming).
See Also
Concepts
Cause and Resolution of Replication Errors