Could not find the index entry for RID

Hi all, got this error and well want some advice really. Cheers
The process could not enumerate changes at the 'Subscriber'.
(Source: Merge Replication Provider (Agent); Error number: -2147200999)
------
Could not find the index entry for RID
'16f8db910fd437730d2cca409ba472f23ca363ef200' in index page (1:353425),
index ID 0, database 'VMR'.
(Source: BBSERVER-SAT1 (Data source); Error number: 644)
------
The merge process encountered an unexpected network error. The connection to
Subscriber 'BBSERVER-SAT1' is no longer available.
(Source: Merge Process (Agent); Error number: -2147199469)
------
Put the database in single user mode and run a dbcc dbreindex, this normally
solves this problem.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"andrew bourne" <andrewbourne@.vardells.com> wrote in message
news:OoLVGQN9FHA.4076@.tk2msftngp13.phx.gbl...
> Hi all, got this error and well want some advice really. Cheers
> The process could not enumerate changes at the 'Subscriber'.
> (Source: Merge Replication Provider (Agent); Error number: -2147200999)
> ------
> Could not find the index entry for RID
> '16f8db910fd437730d2cca409ba472f23ca363ef200' in index page (1:353425),
> index ID 0, database 'VMR'.
> (Source: BBSERVER-SAT1 (Data source); Error number: 644)
> ------
> The merge process encountered an unexpected network error. The connection
> to Subscriber 'BBSERVER-SAT1' is no longer available.
> (Source: Merge Process (Agent); Error number: -2147199469)
> ------
>

Could not find stored procedure ''?

Hi
I recently recovered my SQL2000 Sp3 Merge Replication structure from a
failure after adding a few new articles to my publication. Everything was
going fine (getting everyone up again), until I noticed 5 out of the 100
sites with the following problem:
The merge process could not retrieve column information for table
'dbo.C_ClaimStatus'.
(Source: Merge Replication Provider (Agent); Error number: -2147201016)
Could not find stored procedure ''.
(Source: DAYMED\CC (Data source); Error number: 2812)
I tried re-initialising these subcriptions again, but the problem stayed.
What bugs me is that all my sites were restarted in exactly the same way
(re-initialise site with a pre and post snapshot script to run) and these
are the only 5 sites with this problem.
(All sites are running MSDE sp3 or SQL2000 sp3 and are pull subscriptions)
Has anybody had this before, and if so, how do I fix this?
Regards
Paul Kleynhans
Paul,
This may be due to a failed sp installation. Reapplying sp3a may fix it and
to get a bit more info, have a look at sqlsp.log file from the c:\windows
directory - this might shed some light on any failed actions during the sp
installation.
Regards,
Paul Ibison

Could not find stored procedure

I have this error (Merge Replication):

The row was inserted at 'DISTRIBUTION.db_main' but could not
be inserted at 'subscriber.db_test'. Could not find stored
procedure 'bp_ins_8284C429C5514F08046769C0F2D24607'.

How can I solve this problem?

Thanks.

the proc name doesn't look right, it should be 'sp_ins...', not 'bp_ins...'. Regardless, did you or someone else drop the proc along the way by accident? You may want to try reinitializing the subscription.

|||The first time you generate the publication the stored procedure name will begin with sp_ins; with subsequent reinitializations it will increment the letter, the next one will be ap_ins, then bp_ins.|||BTW-I opened a support incident on this problem in 2002, IIRC - the support engineer was Rand Boyd. Hope this helps you to track it.|||

How can i track it?

|||

I can't recall the srx number, nor the date I opened it. The work around was to deploy all the subscribers. That involved dropping all existing subscribers and resyncing.

I am not sure if the MS guy was able to repro the problem or solve the bug. You would have to call Microsoft and mention my name and have them search on it. Perhpas one of the MS guys who hang out here could seach the RAID database for it.

|||Do you know who is that writes in sysmergearticles?
|||I am not sure what you mean by this. Sysmergearticles is created when you do a sp_replicationdboption 'database','merge publish','true'

The merge agent will fill in this table with the values.|||Why does Merge agent create a new stored? In which situation?
|||Yes, the first time the merge agent runs to apply the snapshot it should fill in these values. It should not modify them at any other point in time.|||Should it modify them only if there is a reinizialization?

I think that it is so but...

For solve this problem I reinitialize from publisher four subscriber then I lunch themerge agent and I have this error: Line 1: Incorrect syntax near ','. 170

and

The process could not deliver the snapshot to the Subscriber. -2147201001.

|||I drop all subscriptions of this publication. I drop my publication that give me error.

I do a new publication. I do my subscriptions with no initializate schema and data.

Now all go well.

Could not find stored procedure

I have this error (Merge Replication):

The row was inserted at 'DISTRIBUTION.db_main' but could not
be inserted at 'subscriber.db_test'. Could not find stored
procedure 'bp_ins_8284C429C5514F08046769C0F2D24607'.

How can I solve this problem?

Thanks.

the proc name doesn't look right, it should be 'sp_ins...', not 'bp_ins...'. Regardless, did you or someone else drop the proc along the way by accident? You may want to try reinitializing the subscription.

|||The first time you generate the publication the stored procedure name will begin with sp_ins; with subsequent reinitializations it will increment the letter, the next one will be ap_ins, then bp_ins.|||BTW-I opened a support incident on this problem in 2002, IIRC - the support engineer was Rand Boyd. Hope this helps you to track it.|||

How can i track it?

|||

I can't recall the srx number, nor the date I opened it. The work around was to deploy all the subscribers. That involved dropping all existing subscribers and resyncing.

I am not sure if the MS guy was able to repro the problem or solve the bug. You would have to call Microsoft and mention my name and have them search on it. Perhpas one of the MS guys who hang out here could seach the RAID database for it.

|||Do you know who is that writes in sysmergearticles?
|||I am not sure what you mean by this. Sysmergearticles is created when you do a sp_replicationdboption 'database','merge publish','true'

The merge agent will fill in this table with the values.|||Why does Merge agent create a new stored? In which situation?
|||Yes, the first time the merge agent runs to apply the snapshot it should fill in these values. It should not modify them at any other point in time.|||Should it modify them only if there is a reinizialization?

I think that it is so but...

For solve this problem I reinitialize from publisher four subscriber then I lunch themerge agent and I have this error: Line 1: Incorrect syntax near ','. 170

and

The process could not deliver the snapshot to the Subscriber. -2147201001.

|||I drop all subscriptions of this publication. I drop my publication that give me error.

I do a new publication. I do my subscriptions with no initializate schema and data.

Now all go well.

Could not find stored procedure

I have this error (Merge Replication):

The row was inserted at 'DISTRIBUTION.db_main' but could not
be inserted at 'subscriber.db_test'. Could not find stored
procedure 'bp_ins_8284C429C5514F08046769C0F2D24607'.

How can I solve this problem?

Thanks.

the proc name doesn't look right, it should be 'sp_ins...', not 'bp_ins...'. Regardless, did you or someone else drop the proc along the way by accident? You may want to try reinitializing the subscription.

|||The first time you generate the publication the stored procedure name will begin with sp_ins; with subsequent reinitializations it will increment the letter, the next one will be ap_ins, then bp_ins.|||BTW-I opened a support incident on this problem in 2002, IIRC - the support engineer was Rand Boyd. Hope this helps you to track it.|||

How can i track it?

|||

I can't recall the srx number, nor the date I opened it. The work around was to deploy all the subscribers. That involved dropping all existing subscribers and resyncing.

I am not sure if the MS guy was able to repro the problem or solve the bug. You would have to call Microsoft and mention my name and have them search on it. Perhpas one of the MS guys who hang out here could seach the RAID database for it.

|||Do you know who is that writes in sysmergearticles?
|||I am not sure what you mean by this. Sysmergearticles is created when you do a sp_replicationdboption 'database','merge publish','true'

The merge agent will fill in this table with the values.|||Why does Merge agent create a new stored? In which situation?
|||Yes, the first time the merge agent runs to apply the snapshot it should fill in these values. It should not modify them at any other point in time.|||Should it modify them only if there is a reinizialization?

I think that it is so but...

For solve this problem I reinitialize from publisher four subscriber then I lunch themerge agent and I have this error: Line 1: Incorrect syntax near ','. 170

and

The process could not deliver the snapshot to the Subscriber. -2147201001.

|||I drop all subscriptions of this publication. I drop my publication that give me error.

I do a new publication. I do my subscriptions with no initializate schema and data.

Now all go well.

Could not find stored procedure

I have this error (Merge Replication):

The row was inserted at 'DISTRIBUTION.db_main' but could not
be inserted at 'subscriber.db_test'. Could not find stored
procedure 'bp_ins_8284C429C5514F08046769C0F2D24607'.

How can I solve this problem?

Thanks.

the proc name doesn't look right, it should be 'sp_ins...', not 'bp_ins...'. Regardless, did you or someone else drop the proc along the way by accident? You may want to try reinitializing the subscription.

|||The first time you generate the publication the stored procedure name will begin with sp_ins; with subsequent reinitializations it will increment the letter, the next one will be ap_ins, then bp_ins.|||BTW-I opened a support incident on this problem in 2002, IIRC - the support engineer was Rand Boyd. Hope this helps you to track it.|||

How can i track it?

|||

I can't recall the srx number, nor the date I opened it. The work around was to deploy all the subscribers. That involved dropping all existing subscribers and resyncing.

I am not sure if the MS guy was able to repro the problem or solve the bug. You would have to call Microsoft and mention my name and have them search on it. Perhpas one of the MS guys who hang out here could seach the RAID database for it.

|||Do you know who is that writes in sysmergearticles?
|||I am not sure what you mean by this. Sysmergearticles is created when you do a sp_replicationdboption 'database','merge publish','true'

The merge agent will fill in this table with the values.|||Why does Merge agent create a new stored? In which situation?
|||Yes, the first time the merge agent runs to apply the snapshot it should fill in these values. It should not modify them at any other point in time.|||Should it modify them only if there is a reinizialization?

I think that it is so but...

For solve this problem I reinitialize from publisher four subscriber then I lunch themerge agent and I have this error: Line 1: Incorrect syntax near ','. 170

and

The process could not deliver the snapshot to the Subscriber. -2147201001.

|||I drop all subscriptions of this publication. I drop my publication that give me error.

I do a new publication. I do my subscriptions with no initializate schema and data.

Now all go well.

Could not find stored procedure

I have this error (Merge Replication):

The row was inserted at 'DISTRIBUTION.db_main' but could not
be inserted at 'subscriber.db_test'. Could not find stored
procedure 'bp_ins_8284C429C5514F08046769C0F2D24607'.

How can I solve this problem?

Thanks.

the proc name doesn't look right, it should be 'sp_ins...', not 'bp_ins...'. Regardless, did you or someone else drop the proc along the way by accident? You may want to try reinitializing the subscription.

|||The first time you generate the publication the stored procedure name will begin with sp_ins; with subsequent reinitializations it will increment the letter, the next one will be ap_ins, then bp_ins.|||BTW-I opened a support incident on this problem in 2002, IIRC - the support engineer was Rand Boyd. Hope this helps you to track it.|||

How can i track it?

|||

I can't recall the srx number, nor the date I opened it. The work around was to deploy all the subscribers. That involved dropping all existing subscribers and resyncing.

I am not sure if the MS guy was able to repro the problem or solve the bug. You would have to call Microsoft and mention my name and have them search on it. Perhpas one of the MS guys who hang out here could seach the RAID database for it.

|||Do you know who is that writes in sysmergearticles?
|||I am not sure what you mean by this. Sysmergearticles is created when you do a sp_replicationdboption 'database','merge publish','true'

The merge agent will fill in this table with the values.|||Why does Merge agent create a new stored? In which situation?
|||Yes, the first time the merge agent runs to apply the snapshot it should fill in these values. It should not modify them at any other point in time.|||Should it modify them only if there is a reinizialization?

I think that it is so but...

For solve this problem I reinitialize from publisher four subscriber then I lunch themerge agent and I have this error: Line 1: Incorrect syntax near ','. 170

and

The process could not deliver the snapshot to the Subscriber. -2147201001.

|||I drop all subscriptions of this publication. I drop my publication that give me error.

I do a new publication. I do my subscriptions with no initializate schema and data.

Now all go well.

Could not deliver update

I have started merge replication. It was working. Now I get messege that 'The
process could not deliver update(s) at the Subscriber'.
If I start it manually, I see message come it has down loaded some records.
100 update, 1 insert etc. I can see my CPU usage is 100%. Then after few min
later it gives that message.
Do not see anythng in the conflict viewer.
Please help
can you enable logging so we can see the exact failure message? Please refer
to this link for more info.
http://support.microsoft.com/default...b;en-us;312292
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Aziz" <Aziz @.discussions.microsoft.com> wrote in message
news:59C17F3D-2C9D-4285-A476-E83BAC9E1025@.microsoft.com...
> I have started merge replication. It was working. Now I get messege that
'The
> process could not deliver update(s) at the Subscriber'.
> If I start it manually, I see message come it has down loaded some
records.
> 100 update, 1 insert etc. I can see my CPU usage is 100%. Then after few
min
> later it gives that message.
> Do not see anythng in the conflict viewer.
> Please help

could not deliver the snapshot to the subscriber

We have a customer w/ merge replication setup and has been functioning.
Their server's were hacked. We have spent 3 days on the phone w/ MS and
everything is working except for 1 client. When it is trying to deliver
the snapshot it is getting an error:
The process could not bulk copy into table {table name}
Violation of PRIMARY KEY constraint. Cannot insert duplicate key.
I understand what that means, so on that table (it is not a necessary
table, just a log), I deleted all records from that table and the
delivery got past that table to the next table in the list and displayed
the same message.
What can I do on the client to get this to work? I can't delete the info
in the second table because it is much more required and I don't want to
have it delete the same data on the main server. I know it is trying to
insert a new record that has the same primary key, but is it trying to
do that because the server record has one guid and the client has a
different guid (I don't really know how the guid's work in replication -
if the record has the same guid on all servers).
Darin
*** Sent via Developersdex http://www.codecomments.com ***
I would use a tool like RedGate's datacompare to reconcile the data to the
Publisher. You'll need to modify the scripts somewhat if you have PK issues
and then I'd reinitialize.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||I know they are duplicate keys. The client has a record w/ the key as 2
(identity column), so does the distributor. The snapshot is trying to
send that record down - why, and how can I make so the snapshot doesn't
try to send it down?
Darin
*** Sent via Developersdex http://www.codecomments.com ***
|||Hi.
In the publisher, mark that identity column which is acting as primary key
to NOT FOR REPLICATION in the design mode of that table.
in this case, the identity will be inserted independently at the subscriber
avoiding primary key errors.
"Darin" wrote:

> I know they are duplicate keys. The client has a record w/ the key as 2
> (identity column), so does the distributor. The snapshot is trying to
> send that record down - why, and how can I make so the snapshot doesn't
> try to send it down?
> Darin
> *** Sent via Developersdex http://www.codecomments.com ***
>
|||The table on both the subscriber and the distrubtor are setup that way.
Darin
*** Sent via Developersdex http://www.codecomments.com ***
|||Can you outline your situation a little more. Usually a snapshot of the
publisher's data is sent from the publisher to the subscriber. Initially
there is a drop table executed on the subscriber. There are variations - one
of which is a nosync initialization, where all the required info already
exists on the subscriber and the publisher just sends the metadata and
system stored procedures/triggers required to run replication. There are
other possibilities where the table and its data remain and the new data is
appended. Of these, which is your requirement, or is your requirement
something quite different?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

could not bulk copy out of table 'contE6E5BDF7F1C24EC588142A934ACF00D1'

Hi all,
Sorry to post this one again but I have added some more info....
I have a sql2000 SP3 merge replication set up using dynamic filters
to 29 sites/publications so each site only see's it's own data.
I have been adding new tables to the schema using sp_mergearticle
(but that is another story !!). I have been running the
sp_mergearticle , running the snapshot, merging, new tables published
...etc OK. I did this 10 times and then hit the error The process
could not bulk copy out of table
'contE6E5BDF7F1C24EC588142A934ACF00D1'. when running the snapshot
agent for one of the publications.
I added the -output (Outputverboselevel 2) and got the follow info at
the end (it failes when it starts to bulk copy)
Bulk copying snapshot data for system table 'MSmerge_contents'
select * from cont21D0C82D8E3E47B8A3C3BC024732C0AC where 1 = 2
[9/16/2004 2:56:22 PM]GODZILLA.MearsData: select * from
cont21D0C82D8E3E47B8A3C3BC024732C0AC where 1 = 2
SourceTypeId = 5
SourceName = GODZILLA
ErrorCode = 8624
ErrorText = Internal SQL Server error.
The process could not bulk copy out of table
'cont21D0C82D8E3E47B8A3C3BC024732C0AC'.
Disconnecting from Publisher 'GODZILLA'
I ran the profiler whilst the snapshot was generated, I could see the
view contE6E5BDF7F1C24EC588142A934ACF00D1 being queried, then when it
errored it sent a drop command on contE6E5BDF7F1C24EC588142A934ACF00D1
(any anything else it had temp created) Is there any way I can capture
the view before it is dropped or stop the drop from occuring. I am sure
if I can get hold of this view then I will be able to find the fault.
I am confused as to why this has been fine on 10 of the publications
then suddenly decided to error.
The file versions I have are:
SQLSRV32.DLL = 2000.81.9042.0
SQLSRV32.RLL = 2000.81.9001.0
odbcbcp.dll = 2000.81.9042.0
Thanks
Ian
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
I've had my share of problems with dynamic filters, but not the one you are
encountering. Can you drop this subscription and filter and then try to
recreate it using another folder?
If you want to catch this transitory view you are best to query it in the
publication database.
IE repeatedly run
sp_helptext contE6E5BDF7F1C24EC588142A934ACF00D1
Or run profiler to try to capture its creation
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"ian bentley" <ian@.ianpb.fsnet.co.uk> wrote in message
news:eesd36JnEHA.556@.tk2msftngp13.phx.gbl...
> Hi all,
> Sorry to post this one again but I have added some more info....
>
> I have a sql2000 SP3 merge replication set up using dynamic filters
> to 29 sites/publications so each site only see's it's own data.
> I have been adding new tables to the schema using sp_mergearticle
> (but that is another story !!). I have been running the
> sp_mergearticle , running the snapshot, merging, new tables published
> ...etc OK. I did this 10 times and then hit the error The process
> could not bulk copy out of table
> 'contE6E5BDF7F1C24EC588142A934ACF00D1'. when running the snapshot
> agent for one of the publications.
> I added the -output (Outputverboselevel 2) and got the follow info at
> the end (it failes when it starts to bulk copy)
> Bulk copying snapshot data for system table 'MSmerge_contents'
> select * from cont21D0C82D8E3E47B8A3C3BC024732C0AC where 1 = 2
> [9/16/2004 2:56:22 PM]GODZILLA.MearsData: select * from
> cont21D0C82D8E3E47B8A3C3BC024732C0AC where 1 = 2
> SourceTypeId = 5
> SourceName = GODZILLA
> ErrorCode = 8624
> ErrorText = Internal SQL Server error.
> The process could not bulk copy out of table
> 'cont21D0C82D8E3E47B8A3C3BC024732C0AC'.
> Disconnecting from Publisher 'GODZILLA'
>
> I ran the profiler whilst the snapshot was generated, I could see the
> view contE6E5BDF7F1C24EC588142A934ACF00D1 being queried, then when it
> errored it sent a drop command on contE6E5BDF7F1C24EC588142A934ACF00D1
> (any anything else it had temp created) Is there any way I can capture
> the view before it is dropped or stop the drop from occuring. I am sure
> if I can get hold of this view then I will be able to find the fault.
>
> I am confused as to why this has been fine on 10 of the publications
> then suddenly decided to error.
> The file versions I have are:
> SQLSRV32.DLL = 2000.81.9042.0
> SQLSRV32.RLL = 2000.81.9001.0
> odbcbcp.dll = 2000.81.9042.0
>
> Thanks
> Ian
>
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||Hilary,
Thanks for your responses.
The trouble is the temp view gets a new name each time I run the
snapshot so I do not know what to look for with sp_helptext.
I could drop the publication/subscription but it has over 100 tables
with un-merged data so I will have to manually put the data in(unless
there is an easier way that I do not know about ?)
Regards,
Ian
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||The way I view it you have about 4 options
1) call PSS
2) figure out the proc which is used to generate this view and modify it to
write a perm view.
3) create a new publication which has this problem filter in and deploy it
to the subscriber
4) backup the publication database and restore it on the subscriber.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"ian bentley" <ian@.ianpb.fsnet.co.uk> wrote in message
news:eq1LVMMnEHA.608@.TK2MSFTNGP09.phx.gbl...
> Hilary,
> Thanks for your responses.
> The trouble is the temp view gets a new name each time I run the
> snapshot so I do not know what to look for with sp_helptext.
> I could drop the publication/subscription but it has over 100 tables
> with un-merged data so I will have to manually put the data in(unless
> there is an easier way that I do not know about ?)
> Regards,
> Ian
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||I've decided to raise a call at Microsoft. If I still cannot resolve
then I will just re-create the publication etc so I will loose nothing
by doing so (except a few ).
I will let you know the outcome.Thanks again for your responses.
Regards,
Ian
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Could not able to enable auto identity range, please help.

Hi there,
I am trying to publish database and replicate using merge replication.
Lot of my table have identity column which are pk as well. I crated
publication and it not giving me option to enable auto identity range
by sql server 2000 itself. could you please let me know what i need to
do so that server give me option to enable auto identity range
management option during initial pulication creation.
Please help me .
Thanks.
Indra.
Have you already created your Publication?
If so you can't do this by altering the publication/articles properties via
the EM.
open up Query Analyzer and do this
declare @.keyword varchar(250)
declare @.keyword2 varchar(250)
declare @.str nvarchar(2500)
set @.keyword='ringer'
set @.keyword2='green'
set @.str='select * from authors as a join containstable(authors,
*,''isabout('+char(34)+@.keyword +char(34)+' weight(.8),'
+char(34)+@.keyword2+char(34)+' weight(.7))'') as t on a.au_id=t.[key]'
exec (@.str)
in front of isabout there are two single quotes, same as by weight(.7))
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Indra" <itimilsina@.savannaenergy.com> wrote in message
news:e667cf1e.0407220804.11855f4b@.posting.google.c om...
> Hi there,
> I am trying to publish database and replicate using merge replication.
> Lot of my table have identity column which are pk as well. I crated
> publication and it not giving me option to enable auto identity range
> by sql server 2000 itself. could you please let me know what i need to
> do so that server give me option to enable auto identity range
> management option during initial pulication creation.
> Please help me .
> Thanks.
> Indra.
|||oops, scratch that - wrong newsgroup
I think you have to drop your publication and recreate it. When you get to
the specify articles dialog, click the browse button and go to the identity
range tab and make the changes there.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:%23HuVUpBcEHA.2388@.TK2MSFTNGP11.phx.gbl...
> Have you already created your Publication?
> If so you can't do this by altering the publication/articles properties
via
> the EM.
> open up Query Analyzer and do this
> declare @.keyword varchar(250)
> declare @.keyword2 varchar(250)
> declare @.str nvarchar(2500)
> set @.keyword='ringer'
> set @.keyword2='green'
> set @.str='select * from authors as a join containstable(authors,
> *,''isabout('+char(34)+@.keyword +char(34)+' weight(.8),'
> +char(34)+@.keyword2+char(34)+' weight(.7))'') as t on a.au_id=t.[key]'
> exec (@.str)
> in front of isabout there are two single quotes, same as by weight(.7))
>
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Indra" <itimilsina@.savannaenergy.com> wrote in message
> news:e667cf1e.0407220804.11855f4b@.posting.google.c om...
>

Corrupted table causes problems

Hi there;
I have a very strange problem. We are running merge replication for a while
and it just stopped working overnight. I am no longer able to create a
snapshot.It stops with the message: An exception occured in the Snapshot
subsystem.
I browsed the newsgroup and someone suggested to run the snapshot from the
commandline. I did that and it run halfway through und terminated with the
message: Column S1Taxvadue4 not found. Which is correct there is no such
column in the database, it is called S1Taxvalue4!
Further investigation revealed that one columns in on of the conflict_...
has a wrong name. Don't ask me why? Well I tried open the table in design
mode to change the name. I am getting the message:
Table 'conflict_...' could not be loaded.
ODBC Error: Cannot insert the value NULL into column'', table '', column
does not allow nulls. Insert fails
Further investigation of the entries in sysobject revealed that this
particular column has NULL in the column usertype. All other columns of this
table have the value 24 in there.
Any ideas on this?
Thomas BornWe are running SQL Server 2000 with SP3 installed on a Windows 2000 Server
machine.
"Thomas Born" <thomas.born@.setac.net.au> wrote in message
news:%23%23gPUB3rDHA.2432@.TK2MSFTNGP10.phx.gbl...
> Hi there;
> I have a very strange problem. We are running merge replication for a
while
> and it just stopped working overnight. I am no longer able to create a
> snapshot.It stops with the message: An exception occured in the Snapshot
> subsystem.
> I browsed the newsgroup and someone suggested to run the snapshot from the
> commandline. I did that and it run halfway through und terminated with the
> message: Column S1Taxvadue4 not found. Which is correct there is no such
> column in the database, it is called S1Taxvalue4!
>
> Further investigation revealed that one columns in on of the conflict_...
> has a wrong name. Don't ask me why? Well I tried open the table in design
> mode to change the name. I am getting the message:
> Table 'conflict_...' could not be loaded.
> ODBC Error: Cannot insert the value NULL into column'', table '', column
> does not allow nulls. Insert fails
> Further investigation of the entries in sysobject revealed that this
> particular column has NULL in the column usertype. All other columns of
this
> table have the value 24 in there.
> Any ideas on this?
> Thomas Born
>