Error using 'Do not lock tables during snapshot generation' optio

I setup a transactional recplication and selected the 'Do not lock tables
during snapshot generation' option so to allow the publication DB to be
available while snapshot is being generated. Snapshot completed OK but the
distributor returned error:
Operand type clash: uniqueidentifier is incompatible with int
(Source: SQLSERVER1\SERVER1 (Data source); Error number: 206)
However, If I unselect the 'Do not lock tables during snapshot generation',
the distributor replicated the DB without error. However, I will lock up all
tables in the Publisher while snapshot is being generated.
Thanks for your help in advance.
Do you have any computed columns in the table that is causing you problem?
If so, does the primary key contain any computed columns?
-Raymond
"Fas" <Fas@.discussions.microsoft.com> wrote in message
news:F0B380C9-53B7-44BD-A810-864B9A685E63@.microsoft.com...
>I setup a transactional recplication and selected the 'Do not lock tables
> during snapshot generation' option so to allow the publication DB to be
> available while snapshot is being generated. Snapshot completed OK but
> the
> distributor returned error:
> Operand type clash: uniqueidentifier is incompatible with int
> (Source: SQLSERVER1\SERVER1 (Data source); Error number: 206)
> However, If I unselect the 'Do not lock tables during snapshot
> generation',
> the distributor replicated the DB without error. However, I will lock up
> all
> tables in the Publisher while snapshot is being generated.
> Thanks for your help in advance.
>
>
|||Thanks for your quick response. We do not use compute columns. Looks like
load loading process mismatch the uniqueidentifier field with an int field.
Because if I do not use the 'Do not lock tables during snapshot generation'
option. the loading process completed fine. The GUID (msrepl_tran_version)
file was added to the replication articles when the articles were created and
they are all at the last column.
"Fas" wrote:

> I setup a transactional recplication and selected the 'Do not lock tables
> during snapshot generation' option so to allow the publication DB to be
> available while snapshot is being generated. Snapshot completed OK but the
> distributor returned error:
> Operand type clash: uniqueidentifier is incompatible with int
> (Source: SQLSERVER1\SERVER1 (Data source); Error number: 206)
> However, If I unselect the 'Do not lock tables during snapshot generation',
> the distributor replicated the DB without error. However, I will lock up all
> tables in the Publisher while snapshot is being generated.
> Thanks for your help in advance.
>
>
|||This sounds kind of strange or I am simply confused as enabling the "Do not
lock tables..." option doesn't change the schema that replication expects at
the subscriber. It would be great if you can post the detail error text that
you were getting (sans sensitive information) if you have determined that
this is not a simple schema mismatch issue.
-Raymond
"Fas" <Fas@.discussions.microsoft.com> wrote in message
news:318470F3-DFE0-4B18-BD9C-17107A3AB3A3@.microsoft.com...[vbcol=seagreen]
> Thanks for your quick response. We do not use compute columns. Looks
> like
> load loading process mismatch the uniqueidentifier field with an int
> field.
> Because if I do not use the 'Do not lock tables during snapshot
> generation'
> option. the loading process completed fine. The GUID
> (msrepl_tran_version)
> file was added to the replication articles when the articles were created
> and
> they are all at the last column.
>
> "Fas" wrote: