December 4, 2014 at 8:39 am
I just started at a new job and they have DQS set up on our BI server. Some genius decided to delete [##MS_dqs_service_login##] login, the user dqs_service still exists in the DQS_Main db. The error log is full of errors similar to this one...
The activated proc '[internal_core].[ParallelExecutionActivator]' running on queue 'DQS_MAIN.dbo.ParallelExecutionRequestQueue' output the following: 'Cannot execute as the database principal because the principal "dqs_service" does not exist, this type of principal cannot be impersonated, or you do not have permission.'
I have tried the standard exec sp_change_users_login 'Auto_Fix' with no success. At this point I don't think anyone is utilizing DQS, but at some point I am going to have to fix this. Any thoughts, ideas would be greatly appreciated.
December 8, 2014 at 1:02 am
Try running it from DQS_MAIN
ie:
use [DQS_MAIN]
go
sp_change_users_login 'Report'
-- use UserSID from above in quer
-- Login: ##MS_dqs_service_login##
CREATE LOGIN [##MS_dqs_service_login##] WITH PASSWORD = 0x0200B94B995770F2746EB332B9A77A2728AAD0FD46D2E516015D1981C00524CAAE31CF1B8ABCD16982C3D6E566C8E1F0A5E6A1684F998C5D105ABF2D760C36CB6012EDAAEA17 HASHED
,SID = 0x5FA4E84B4F1C934096F249E32224F94A /*REPLACE THIS SID */
, DEFAULT_DATABASE = [master], CHECK_POLICY = ON, CHECK_EXPIRATION = OFF; ALTER LOGIN [##MS_dqs_service_login##] DISABLE
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply