Skip to main content
Announcements
Qlik Introduces a New Era of Visualization! READ ALL ABOUT IT
cancel
Showing results for 
Search instead for 
Did you mean: 
Naga_vivek
Contributor III
Contributor III

Qlik Replicate: [SQL Server]Invalid parameter passed to OpenRowset(DBLog, ...). (PcbMsg: 105)'

Hi Team,

we recently encountered an error in the Qlik replicate task 

Encountered an unexpeceted error.
SqlStat: 42000 NativeError:9005 [Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid parameter passed to OpenRowset(DBLog, ...). (PcbMsg: 105)"

  • we are using  Microsoft SQL server as source
  • windows OS with November 2022 Replicate version.

Could you let me know the places where it will affect the Task and the causes for that error.

Please kindly assist to resolve the issue.

 

 

Labels (2)
1 Solution

Accepted Solutions
john_wang
Support
Support

Hello @ANANDKUMAR ,

Maybe yes maybe No, anyway set SOURCE_CAPTURE to Verbose and check the task log file to understand further of the reason.

Hello @Naga_vivek ,

Not very sure how the TLOG rollover policy or if the backup was done by non-default format . Would you please set SOURCE_CAPTURE to Verbose , recreate the issue then check the task log file. Or upload the Diagnostics Packages to support case, The Support Team will help you on the issue.

thanks,

John.

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!

View solution in original post

6 Replies
john_wang
Support
Support

Hello @Naga_vivek ,

Welcome to Qlik Community forum and thanks for reaching out here!

A few of reasons may lead this same error, for example:

1. Backup transaction log is inaccessible, Suspect TLOG was truncated when Replicate task was stopped, resume the task got this error. Reload the task may solve the issue

     Similar article: Invalid parameter passed to OpenRowset

2. The backup was generated by the third-party backup tools/apps rather than SQL Server native format. In this scenario the backup TLOG should be converted to MS SQL Server native format prior to Replicate access them.

Hope this helps.

Regards,

John.

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
ANANDKUMAR
Contributor
Contributor

Thanks John for the answer.

Quick question - This error cause any data loss in the target ?

Naga_vivek
Contributor III
Contributor III
Author

Hi @john_wang ,

 

Thank you for the answer.

We tried reloading the target but still we are facing the same issue  after the reload. 

Could you suggest me any Solution how we can resolve the issue

and could you let me know how we  can verify if there is any loss in TLOG.

If It is lost then there might be a chance of data loss right?

 

Regards 

N Vivek

john_wang
Support
Support

Hello @ANANDKUMAR ,

Maybe yes maybe No, anyway set SOURCE_CAPTURE to Verbose and check the task log file to understand further of the reason.

Hello @Naga_vivek ,

Not very sure how the TLOG rollover policy or if the backup was done by non-default format . Would you please set SOURCE_CAPTURE to Verbose , recreate the issue then check the task log file. Or upload the Diagnostics Packages to support case, The Support Team will help you on the issue.

thanks,

John.

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
suvbin
Creator III
Creator III

i also faced the same issue. What does this error means ?

john_wang
Support
Support

Hello @suvbin ,

Not very sure what's the Replicate version you are running now, however "SQL Server Native Client 11.0" is not officially supported in the last 2 major versions. I'd like to suggest you upgrade to supported Replicate versions if possible.

Regarding the error, you may set SOURCE_CAPTURE to Verbose, recreate the error, then you may find out the SQL Statement from the task log file how Qlik Replicate to capture changes from TLOG. you may manually run the same SQL in SSMS to fully understand the reason.

Hope this helps.

John.

 

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!