Error when running Snapshot Agent

David,
can you have a look at the list of processes and see if
the snapshot.exe is listed, then kill it if it is.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
No - definitely no snapshot.exe.
"Paul Ibison" wrote:

> David,
> can you have a look at the list of processes and see if
> the snapshot.exe is listed, then kill it if it is.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||David,
have a look at sp_removedbreplication, which should
remove any lingering system table traces. Have a look for
any orphaned jobs which are running the snapshot agent.
Also, consider restarting the sql server service.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||An update on this issue:
I disabled replication and distribution on the publisher and distributor
(respectivley) started again.
I was able to start the snapshot agent.
I then received a different error from the snapshot agent:
Invalid object name: syspublications.
Still stuck on this error though.
"Paul Ibison" wrote:

> David,
> have a look at sp_removedbreplication, which should
> remove any lingering system table traces. Have a look for
> any orphaned jobs which are running the snapshot agent.
> Also, consider restarting the sql server service.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
>

Error when running Agent in Merge Replication!

Hi All:
I am trying to setup a Merge Replication over Internet. Snapshot runs
successfully, but when it tries to run sycronize the data for ther first
time, it gives the following error in the end:
The Subscription to Publication 'xxxx' is invalid
'xxxx' is the Database Name
The connectivity to the remote DB is working.
One of the reasons for this swich I found was the the remote server's name
was changed after SQL server was installed. Therefore the old name was
dropeed b y using these:
sp_dropserver <server name>
go
sp_addserver <new server name> , LOCAL
go
After doing this, we still get the same message "The Subscription to
Publication 'xxxx' is invalid"
Please suggest the remedy for this.
Thanks,
Anukul
anukul,
Just for grins, check that the publisher is aware of the new server name. If not you can either drop the subscription in both places and re-create or alter the subscription in both places to utilize the new machine name.
Give it a shot. Worst case it doesn't work...|||If you changed the server name after configuring the Subscriber, the
Publisher doesn't know about the new server name. You need to drop and
recreate the subscription at the Subscriber and re-register the Subscriber
with the Publisher, using the following stored procedures:
? sp_dropmergepullsubscription at the Subscriber (only if the Merge Agent
runs at the Subscriber, a pull subscription).
? sp_dropmergesubscription at the Publisher.
? sp_dropsubscriber at the Publisher.
You should also be able to do this from Enterprise Manager.
Then you must re-register the Subscriber using sp_addsubscriber or (from
Enterprise Manager) and recreate the subscription using either Enterprise
Manager or executing sp_addmergesubscription at the Publisher and
sp_addmergepullsubscription (only if the Merge Agent runs at the Subscriber,
a pull subscription).
Best wishes,
Glenn Gailey
SQL Server User Education
This posting is provided "AS IS" with no warranties, and confers no rights.
"Anukul" wrote:

> Hi All:
> I am trying to setup a Merge Replication over Internet. Snapshot runs
> successfully, but when it tries to run sycronize the data for ther first
> time, it gives the following error in the end:
> The Subscription to Publication 'xxxx' is invalid
> 'xxxx' is the Database Name
> The connectivity to the remote DB is working.
> One of the reasons for this swich I found was the the remote server's name
> was changed after SQL server was installed. Therefore the old name was
> dropeed b y using these:
> sp_dropserver <server name>
> go
> sp_addserver <new server name> , LOCAL
> go
> After doing this, we still get the same message "The Subscription to
> Publication 'xxxx' is invalid"
> Please suggest the remedy for this.
> Thanks,
> Anukul
>
>

Error when applying snapshot

Hello, I have setup web sync from wm 5.0 and it seems to crash when applying the snapshot. Looking at the column definitions it seems fine. Am I missing something? Thanks in advance.

John

The identity column must be either an integer or big integer data type and cannot be NULL.
HRESULT 0x80004005 (25551)

The SQL statement failed to execute. [ SQL statement = CREATE TABLE "macros" ( "peopleid" numeric ( 18 , 0 ) NOT NULL , "macroid" numeric ( 18 , 0 ) IDENTITY ( 1 , 1 ) NOT NULL , "description" nvarchar ( 255 ) NULL , "rowguid" uniqueidentifier ROWGUIDCOL NOT NULL CONSTRAINT "MSmerge_df_rowguid_8E4B26C6706844BC984B039BA07845B5" DEFAULT ( NEWID ( ) ) ) ]
HRESULT 0x80004005 (28560)

The operation could not be completed.

The error message has everything! Please read it again. It says that your identity column (macroid) is not of type bigint or int. SQL Server Mobile/Everywhere support IDENTITY only on int and bigint.

Thanks,

Laxmi Narsimha Rao ORUGANTI, SQL Server Everywhere, Microsoft Corporation

|||

I'm getting the same error when trying to set up a subscription to merge replication with wm 5.0. Here is the error:

The identity column must be either an integer or big integer data type and cannot be NULL.
HRESULT 0x80004005 (25551)

The SQL statement failed to execute. If this occurred while using merge replication, this is an internal error. If this occurred while using RDA, then the SQL statement is invalid either on the PULL statement or on the SubmitSQL statement. [ SQL statement = CREATE TABLE "INV_MfrProduct" ( "MfrProductId" numeric ( 18 , 0 ) IDENTITY ( 1 , 1 ) NOT NULL , "MfrProductDesc" nvarchar ( 100 ) NOT NULL , "isActive" bit NOT NULL , "ClassId" numeric ( 18 , 0 ) NULL , "rowguid" uniqueidentifier ROWGUIDCOL NOT NULL CONSTRAINT "MSmerge_df_rowguid_CA8620C3C47D4A388517DDA409E1C2AB" DEFAULT ( NEWID ( ) ) ) ]
HRESULT

The table in question though is only one (last one) out of several that have identity as numeric field. The identity range is safely within the limits of bigint though. So, what would be the solution to this? Not use merge replication?

Please, advise.

Error when applying snapshot

Hello, I have setup web sync from wm 5.0 and it seems to crash when applying the snapshot. Looking at the column definitions it seems fine. Am I missing something? Thanks in advance.

John

The identity column must be either an integer or big integer data type and cannot be NULL.
HRESULT 0x80004005 (25551)

The SQL statement failed to execute. [ SQL statement = CREATE TABLE "macros" ( "peopleid" numeric ( 18 , 0 ) NOT NULL , "macroid" numeric ( 18 , 0 ) IDENTITY ( 1 , 1 ) NOT NULL , "description" nvarchar ( 255 ) NULL , "rowguid" uniqueidentifier ROWGUIDCOL NOT NULL CONSTRAINT "MSmerge_df_rowguid_8E4B26C6706844BC984B039BA07845B5" DEFAULT ( NEWID ( ) ) ) ]
HRESULT 0x80004005 (28560)

The operation could not be completed.

The error message has everything! Please read it again. It says that your identity column (macroid) is not of type bigint or int. SQL Server Mobile/Everywhere support IDENTITY only on int and bigint.

Thanks,

Laxmi Narsimha Rao ORUGANTI, SQL Server Everywhere, Microsoft Corporation

|||

I'm getting the same error when trying to set up a subscription to merge replication with wm 5.0. Here is the error:

The identity column must be either an integer or big integer data type and cannot be NULL.
HRESULT 0x80004005 (25551)

The SQL statement failed to execute. If this occurred while using merge replication, this is an internal error. If this occurred while using RDA, then the SQL statement is invalid either on the PULL statement or on the SubmitSQL statement. [ SQL statement = CREATE TABLE "INV_MfrProduct" ( "MfrProductId" numeric ( 18 , 0 ) IDENTITY ( 1 , 1 ) NOT NULL , "MfrProductDesc" nvarchar ( 100 ) NOT NULL , "isActive" bit NOT NULL , "ClassId" numeric ( 18 , 0 ) NULL , "rowguid" uniqueidentifier ROWGUIDCOL NOT NULL CONSTRAINT "MSmerge_df_rowguid_CA8620C3C47D4A388517DDA409E1C2AB" DEFAULT ( NEWID ( ) ) ) ]
HRESULT

The table in question though is only one (last one) out of several that have identity as numeric field. The identity range is safely within the limits of bigint though. So, what would be the solution to this? Not use merge replication?

Please, advise.

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 trying to websync

Hello,

We dropped an article and then made a change to a column. We then added the article back in. Generated a snapshot and reinitialized all subscriptions without uploading data changes. After we did this we still continue to get this error. Any ideas? Thanks.

John

The Merge Agent failed after detecting that retention-based metadata cleanup has deleted metadata at the Publisher for changes not yet sent to the Subscriber. You must reinitialize the subscription (without upload).

John,

After you drop the article and before you add the article in, did you run the marge agent? Also, what version of SQL Server are you using?

|||

Yi,

No we didn't run merge agent manually. Were we supposed to? It's SQL 2k5

John

|||

The error message is telling that some metadata that is needed to enumerate what rows need to sent to the subscriber has been cleaned up. Hence you will need to reinitialize the subscription.

And you need not run the merge agent in between dropping and adding the article.

You might have encoutnered this scenario because the merge agent may not have synchronized with the publisher for a long time (time longer than the retention period)

Please reinitialize without upload, run the merge agent and report back if you still see failures.

Error trying to websync

Hello,

We dropped an article and then made a change to a column. We then added the article back in. Generated a snapshot and reinitialized all subscriptions without uploading data changes. After we did this we still continue to get this error. Any ideas? Thanks.

John

The Merge Agent failed after detecting that retention-based metadata cleanup has deleted metadata at the Publisher for changes not yet sent to the Subscriber. You must reinitialize the subscription (without upload).

John,

After you drop the article and before you add the article in, did you run the marge agent? Also, what version of SQL Server are you using?

|||

Yi,

No we didn't run merge agent manually. Were we supposed to? It's SQL 2k5

John

|||

The error message is telling that some metadata that is needed to enumerate what rows need to sent to the subscriber has been cleaned up. Hence you will need to reinitialize the subscription.

And you need not run the merge agent in between dropping and adding the article.

You might have encoutnered this scenario because the merge agent may not have synchronized with the publisher for a long time (time longer than the retention period)

Please reinitialize without upload, run the merge agent and report back if you still see failures.

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.