RAISERROR(‘A problem was encountered granting access to MSDB database for login ”%s”. PRINT ‘Granting login access”’ ”’ to msdb database…’ IF NOT EXISTS(SELECT * FROM sys.database_principals WHERE (sid = OR (LOWER(name collate SQL_Latin1_General_CP1_CS_AS) = collate SQL_Latin1_General_CP1_CS_AS))) –add job_owner to the SQLAgentUserRole msdb role in order to permit the job owner to handle his jobs SELECT = ISNULL(IS_SRVROLEMEMBER(‘sysadmin’),0) - check role membership SELECT DISTINCT j.owner_sid FROM sysjobs jįETCH NEXT FROM job_nonsysadmin_owners_cursor INTO = 0) Inside this file, I searched for POST_SQLAGENT100.SQL section (above you can see that there is a message saying that “Execution of POST_SQLAGENT100.SQL was completed”) and then found that SQL was trying to execute this code:ĭECLARE job_nonsysadmin_owners_cursor CURSOR LOCAL FOR Instance default installation path\Install\msdb110_upgrade.sql Below those scary messages, I found another interesting thing:įirst: “Granting login access User name to MSDB database” and then “A problem was encountered granting access to MSDB database for login (null)”… That means that something was going on with that particular account.įirst, I started debugging the file that sql server was trying to execute: “Config Statement cannot be used inside a user transaction” or Cannot recover the master database… Interesting…. SP 1 was applied on the passive node then the failover was executed and it failed. Today, I want to talk about one situation that happened last week… I received an email saying that there were some issues within a failover cluster patching implementation.įailover clustered instance in SQL Server 2016 RTM with 2 nodes: We are not able to use our passive node now and we are still running on RTM, please help us! Hi Gonzalo, We applied SP1 on the passive node and the failover didn’t work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |