| Event Id | 15008 |
| Source | MSSQLServer |
| Description | User '%s' does not exist in the current database. |
| Event Information | "According to Microsoft Cause: The user specified in your sp_revokedbaccess, sp_addrole, sp_dropuser, sp_changegroup, or sp_addalias command does not exist or does not have the expected properties in the current database. Often this is the result of rebuilding master or doing a restore or attach of a database from another instance of SQL Server. In those situations you may have orphaned users that must be resynchronized with the logins in the master database. For more information about matching database users to logins in the master database, see the various references in the Microsoft Knowledge Base article, 314546. Resolution: When specifying a Windows NT user or group, specify the name that the Windows NT user is known by in the database (added using sp_grantdbaccess). Specify a user that exists in the sysusers table for the current database. If the specified user does exist, compare the values in the sysusers table for that user to the properties checked by the specific stored procedure that reported the error. The validations performed by each procedure include: sp_revokedbaccess: name can be the name of a Microsoft SQL Server user, or Microsoft Windows NT user or group, and must exist in the current database. sp_addrole: owner must be a user or role in the current database. sp_addalias: alias_user must be a valid Windows NT or SQL Server user in the database in which the login is aliased.sp_addalias is provided for backward compatibility. Microsoft SQL Server 2000 provides roles and the ability to grant permissions to roles as an alternative to using aliases. sp_changegroup: The user must already exist in the current database. sp_changegroup is provided for backward compatibility. Microsoft SQL Server 2000 uses roles instead of groups. Use sp_addrolemember instead. sp_dropuser: The user must exist in the current database. When specifying a Windows NT user, specify the name that the Windows NT user is known by in the database (added using sp_grantdbaccess). sp_dropuser is provided for backward compatibility. Use sp_revokedbaccess to remove a user. If there are orphaned users in the database, see the Microsoft Knowledge Base article, 314546 for links to the various ways to resynchronize your users to your logins. " |
| Reference Links | Event Id:15008 of Source Id:MSSQLServer |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.