Can't re-submit a deleted conflicted row

Hello,
I have a merge replication which use identity range management (for some
tables).
I have a table that inserted a row on the publisher and tried to transfer it
to subscriber. The subscriber got an error when trying to insert it (by the
way, I use MSDE on subscriber and MSmerge_contents and MSmerge_tombstone are
huge and the DB limit of 2 GB arrive fast - it was nice that the system
tables are not included in the 2 GB limit... I decided to move that 2 tables
in another DB and it works nice). As I said, the subscriber gave an error
(different reasons) and the conflict resolver decided to delete the row from
publisher, because it can't insert in on subscriber !?! Anyway seems to be ok
because the row i have in conflict viewer, that seems that I can re-insert
it. But when I try to re-insert it, it gave me an error because the identity
ranges changed and the old value (of deleted row) is not proper for the new
constraints of identity... I supposed that SQL will deactivate the
constraint, as it does during replication...
Any ideea how to re-insert it? Or I have to "manually" (programatically)
de-activate it, insert it from conflict table and re-activate it?
Thanks for any suugestion.
Catalin
Hello Catalin,
I have something for you. I've tried reaching you through phone or email,
without success. Email me at chris lafrance at h_tm__l dot com.
Cheers
"Catalin NASTAC" wrote:

> Hello,
> I have a merge replication which use identity range management (for some
> tables).
> I have a table that inserted a row on the publisher and tried to transfer it
> to subscriber. The subscriber got an error when trying to insert it (by the
> way, I use MSDE on subscriber and MSmerge_contents and MSmerge_tombstone are
> huge and the DB limit of 2 GB arrive fast - it was nice that the system
> tables are not included in the 2 GB limit... I decided to move that 2 tables
> in another DB and it works nice). As I said, the subscriber gave an error
> (different reasons) and the conflict resolver decided to delete the row from
> publisher, because it can't insert in on subscriber !?! Anyway seems to be ok
> because the row i have in conflict viewer, that seems that I can re-insert
> it. But when I try to re-insert it, it gave me an error because the identity
> ranges changed and the old value (of deleted row) is not proper for the new
> constraints of identity... I supposed that SQL will deactivate the
> constraint, as it does during replication...
> Any ideea how to re-insert it? Or I have to "manually" (programatically)
> de-activate it, insert it from conflict table and re-activate it?
> Thanks for any suugestion.
> Catalin

Cant insert new record to database.

SOS
I am working with SQL 2000 located on a Networksolutions server and I have a Test record I inserted manually, but I am unable to insert a new record and get this error "can't insert new record to database".
No doubt this is a no brainer, but I can't solve it.
Many Thanks
Who ever you are.SOS
I am working with SQL 2000 located on a Networksolutions server and I have a Test record I inserted manually, but I am unable to insert a new record and get this error "can't insert new record to database".
No doubt this is a no brainer, but I can't solve it.
Many Thanks
Who ever you are.
Its too little info,plz provide more.This can occur due to lots of reason.|||The Table was manually created in Enterprise Manager.
This is the Script :
= = =
if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[tblProfile]') and OBJECTPROPERTY(id, N'IsUserTable') = 1)
drop table [dbo].[tblProfile]
GO

CREATE TABLE [dbo].[tblProfile] (
[ID] [int] IDENTITY (1, 1) NOT NULL ,
[Password] [varchar] (50) COLLATE Latin1_General_CI_AS NOT NULL ,
[FirstName] [varchar] (50) COLLATE Latin1_General_CI_AS NOT NULL ,
[LastName] [varchar] (50) COLLATE Latin1_General_CI_AS NOT NULL ,
[ZipCode] [varchar] (10) COLLATE Latin1_General_CI_AS NOT NULL ,
[Email] [varchar] (100) COLLATE Latin1_General_CI_AS NOT NULL ,
[Digit9] [varchar] (9) COLLATE Latin1_General_CI_AS NOT NULL ,
[Digit81] [varchar] (2) COLLATE Latin1_General_CI_AS NOT NULL ,
[Digit16] [varchar] (2) COLLATE Latin1_General_CI_AS NOT NULL ,
[StateAffiliation] [varchar] (9) COLLATE Latin1_General_CI_AS NOT NULL ,
[DateCreated] [datetime] NOT NULL ,
[DateUpdated] [datetime] NOT NULL
) ON [PRIMARY]
GO
The Connection String has been tested and is OK.
===
Thank you for your response|||Do you have insert statements for the record you inserted and the one you are attempting to insert?|||Hello and Thank you
I'm not sure what you mean by "insert statement"|||Let me make sure we are talking about the same thing. You have created the table that is scripted above. Now you are attempting to add data to this table by typing it into the table in enterprise manager. Is this correct?|||No.
The Table is for a Registration form.
Can't insert new record to database is the Error Message I get when I try to register a new user.
Sorry I was not clear.|||OK, as rudra said, could be lots of things. Here's my first suggestion, maybe the form is trying to put a value in the [ID] field.

Another thing, does the form retrieve data from the table before trying to write to it so you know it is not a security problem?

Is there any way you can display the output of the form before it sends it to the database. This sort of problem can be really hard to diagnose from a distance!!