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:

Error to manually add subscription to an article

When trying to add an article back to an existing publication thats active
in transactional replication I get the following error
Server: Msg 14100, Level 16, State 1, Procedure sp_addsubscription, Line 240
Specify all articles when subscribing to a publication using concurrent
snapshot processing.
Apparently concurrent snapshot is enabled and when I did issue the
sp_addsubscription and specified the @.article parameter with the table name
, it didnt like it and threw the above error..
It wanted 'all' .. and I was afraid it would do some reinitializing,etc..
Just curious to know why we need that 'all'.. Seems kinda buggy
Interesting. I remember seeing this on Vyas's blog:
http://vyaskn.tripod.com/sqlblog/. He didn't report a solution and I'll also
take a look.
Rgds,
Paul Ibison
|||I just substituted all and it worked. It did take care of just the
respective articles.. Thank God..
With that Im thinking, should we just use all even if we dont have
concurrent snapshot enabled . Will it just take care of just those articles
we want to add manually. I'll try it out and let u know
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23zcnRGXSFHA.1528@.TK2MSFTNGP09.phx.gbl...
> Interesting. I remember seeing this on Vyas's blog:
> http://vyaskn.tripod.com/sqlblog/. He didn't report a solution and I'll
also
> take a look.
> Rgds,
> Paul Ibison
>
>

error subscribing to publication

Hi All,
[CURRENT SET UP]
I have two SQL 2k Ent servers in two locations.
SVR1 has 2 publications (snapshot and merge) the SVR2 subscribes to.
SVR2 republishes these, so that a number of local MSDE clients can
subscribe to them.
SVR1 also has a number of local MSDE subscribers.
[PROBLEM]
Everything was working great, however this afternoon I tried to add a new
MSDE subscriber (through enterprise manager on my machine, as opposed to
SVR1) to SVR1 and got the following message ?
SQL Server Enterprise Manager could not retrieve information about the
publications from Publisher 'SVR1'.
Error 208: Invalid object name 'syspublications'.
Invalid object name 'sysextendedarticlesview'.
I really don't want to drop publications on this server, and so am trying
to find a way of solving this problem, rather than redeploying the
replication structure.
Any help in understanding or troubleshooting this would be greatly
recieved !
TIA.
Ranjeet.
oddly, if I script a subscription and run it, all is OK.
It appears enterprise manager in trying to enumerate the publications is
failing, and so preventing me from subscribing users through EM.
Does anyone know how the publications are enumerated - is there a view /
table / SP that exists for this ?
TIA
Ranjeet.

error setting up publication

Hello,
I am trying to setup merge publication and receive the following
error:
SQL Server Enterprise Manager could not configure 'DEV' as the
Distributor for 'DEV'.
Error 18483: Could not connect to server 'DEV' because
'distributor_admin' is not defined as a remote login at the server.
Im stumped on this one.
Todd
Are you using an IP address to set up replication across domains? If so then
you'll need to use an alias instead.
Does SELECT@.@.Servername return a different name to your server select
SERVERPROPERTY('ServerName').
If so then you need to run:
Use Master
go
Sp_DropServer 'Server1'
GO
Use Master
go
Sp_Addserver 'Server1', 'local'
GO
Stop and Start SQL Services
Regards,
Paul Ibison