title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | ms.custom | helpviewer_keywords | monikerRange | ||
---|---|---|---|---|---|---|---|---|---|---|---|---|
MSSQL_ENG021797 |
MSSQL_ENG021797 |
MashaMSFT |
mathoma |
09/25/2024 |
sql |
replication |
reference |
|
|
=azuresqldb-mi-current||>=sql-server-2016 |
[!INCLUDE SQL Server SQL MI]
Attribute | Value |
---|---|
Product Name | SQL Server |
Event ID | 21797 |
Event Source | MSSQLSERVER |
Component | [!INCLUDEssDEnoversion] |
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'. |
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 [!INCLUDEssNoVersion]. The security model changed in [!INCLUDEssVersion2005], and these scripts must be updated.
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 [!INCLUDEmsCoName] 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 [!INCLUDEssNoVersion] 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.
Ensure you specify a valid Windows account for the @job_login
parameter of each procedure. If you have replication scripts from previous versions of [!INCLUDEssNoVersion], update these scripts to include the stored procedures and parameters required by [!INCLUDEssVersion2005]. For more information, see Upgrade Replication Scripts (Replication Transact-SQL Programming).