Skip to main content
Announcements
See what Drew Clarke has to say about the Qlik Talend Cloud launch! READ THE BLOG
cancel
Showing results for 
Search instead for 
Did you mean: 
DuongNguyen
Contributor III
Contributor III

Failure upon initial CAPTURE fitness checking

I got this error when running replicate from SQL Server Source to ODBC (IBM DB2 for iSeries) Target

DuongNguyen_0-1697012246158.png

the account I have set db_owner permissions!

DuongNguyen_0-1697012734197.png

how to fix it?

2 Solutions

Accepted Solutions
SushilKumar
Support
Support

Hello Team,

Request you to follow the instruction mentioned in the help Document when you are using SQL Server as a Source endpoint.

https://help.qlik.com/en-US/replicate/May2022/Content/Replicate/Main/SQL%20Server/SQLServer_DB_sourc...

As its have Some pre-requisite in term of

Prerequisites
Required permissions
Setting up Microsoft SQL Server for replication

Regards,

Sushil Kumar

 

 

 

View solution in original post

Heinvandenheuvel
Specialist III
Specialist III

The error message is incorrect it should read: 

  • A member of both the db_owner database role and the sysAdmin fixed server role.

AND, not OR

Hein.

View solution in original post

3 Replies
SushilKumar
Support
Support

Hello Team,

Request you to follow the instruction mentioned in the help Document when you are using SQL Server as a Source endpoint.

https://help.qlik.com/en-US/replicate/May2022/Content/Replicate/Main/SQL%20Server/SQLServer_DB_sourc...

As its have Some pre-requisite in term of

Prerequisites
Required permissions
Setting up Microsoft SQL Server for replication

Regards,

Sushil Kumar

 

 

 

Heinvandenheuvel
Specialist III
Specialist III

The error message is incorrect it should read: 

  • A member of both the db_owner database role and the sysAdmin fixed server role.

AND, not OR

Hein.

DuongNguyen
Contributor III
Contributor III
Author

DuongNguyen_0-1697103372318.png

DuongNguyen_1-1697103383505.png

@Heinvandenheuvel @SushilKumar I set user has permission sysadmin and db_owner but it still has the same problem as above