
Support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Cannot execute as the database principal because the principal "dbo" does not exist
Last Update:
Mar 1, 2022 6:17:39 AM
Updated By:
Created date:
Feb 24, 2022 7:43:20 AM
A Qlik Replicate task is running without issue.
However, on the SQL source end, the Log Reader agent is failing to start which appears to be causing the LDF files to grow large and the Log Reader agent is failing to start as well.
Environment:
Qlik Replicate
SQL 2014
Resolution
When checking on the Log Reader Agent, it fails on error: refused because the job is already running from a request by Start Sequence
- We try to manually remove the Log Reader Agent, and then remove the AR_PUBLICATION_000x that Qlik Replicate creates and start over.
- On Start over, the Publication can not be removed.
- We have to use the two commands below:
- use master; sp_removedbreplication 'mydatabasenamehere'
- EXEC sp_replicationdboption @dbname = 'mydatabasenamehere', @optname = 'publish', @value = 'true'
- Then we let the Qlik Replicate task run so that it could create the Publication and the Log Reader Agent.
- Checking on the Log Reader Agent job now we have a new error:
Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impersonated, or you do not have permission. - We check the database that is used for Qlik Replicate, and the database does not have an owner.
So we assign an owner to the database:use [YourDatabaseName] EXEC sp_changedbowner 'sa'
- Now the Log Reader Agent job run without issue.
Cause
The database used for Replication does not have an Owner. Make sure that the database has an owner assigned to it.
1,126 Views