Replication Timeout Issue

Greetings!

I am running into this error when running Replication:

The response message was received from 'https://replia.websitename.net/replia/replisapi.dll' and is being processed.

(f) The process could not connect to Distributor 'OURDATABASE-DB'.

(f) The process could not connect to Distributor 'OURDATABASE-DB'.

(f) Unable to complete login process due to delay in opening server connection

*******************************************************

01/11/2007 18:26:09 - Error during FINAL DB Replication. The process could not connect to Distributor 'OURDATABASE-DB'.

I am running Replication on a Windows XP Pro laptop, with 1 GB of RAM, 1.83 GHz CPU. Any ideas, suggestions and/or help would be appreciated!

Thanks!

Cristian E.

Please provide more information. What version of SQL server are you using? Are you using standard edition, enterprise, or express? Transactional or merge replication?

Gary

|||

Hello,

1. Is the Laptop computer your Subscriber or Publisher/Distributor?

2. If you do not do web sync, can you run sync through merge agent (replmerg.exe) from Console window command line using fully connected mode?

This posting is provided AS IS with no warranties, and confers no rights.

|||

I am using SQL Server 2005 Express version, Merge replication. I changed the History Verbose Level to a 2 and I got a different error:

(f) The response message was received from 'https://replia.websitename.net/replia/replisapi.dll' and is being processed.
(f) The process could not connect to Distributor 'ABCD-DB'.
(f) The process could not connect to Distributor 'ABCD-DB'.
(f) Named Pipes Provider: Could not open a connection to SQL Server [2].
(f) An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
(f) Login timeout expired
(f) The merge process failed to execute a query because the query timed out. If this failure continues, increase the query timeout for the process. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write.
*******************************************************
01/13/2007 09:31:39 - Error during FINAL DB Replication. The process could not connect to Distributor 'ABCD-DB'.

*******************************************************

I have already increased the timeout to 15-20 mins. Any other suggestions?

Thanks!

Cristian E.

|||

I am using SQL Server 2005 Express version, Merge replication. I changed the History Verbose Level to a 2 and I got a different error:

(f) The response message was received from 'https://replia.websitename.net/replia/replisapi.dll' and is being processed.
(f) The process could not connect to Distributor 'ABCD-DB'.
(f) The process could not connect to Distributor 'ABCD-DB'.
(f) Named Pipes Provider: Could not open a connection to SQL Server [2].
(f) An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
(f) Login timeout expired
(f) The merge process failed to execute a query because the query timed out. If this failure continues, increase the query timeout for the process. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write.
*******************************************************
01/13/2007 09:31:39 - Error during FINAL DB Replication. The process could not connect to Distributor 'ABCD-DB'.

*******************************************************

I have already increased the timeout to 15-20 mins.

The Laptop computer is the Publisher and it is running web synchronization (web services).

|||

Has it ever worked before?

Can you try this on your machine?

osql -S"ABCD-DB" -U"login"

See if you get the same error message for "Named Pipes Provider: Could not open a connection to SQL Server [2]. "

If you get the same message, then the problem is as simple as enable the protocols in your sql server setting.

I also noticed that the name "ABCD-DB" sounds more like a database name than a server name...

Regards,
Gary

sql

Replication question

Dear Friends,
i'm facing a strange thing with merge replication , the
merge agent is running and working successfully
displaying the message 'no data needed to be merged'
although alot of modificatins is been made to the
subscriber. and i stoped the agent and run it again , same
message.
any idea might cause this problem
Thanks
Scroll to the right. There are numbers out there for the volume of
inserts/updates/deletes being moved. What you are seeing is completely
normal since you are seeing the final state after it has run and already
moved data.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com

Replication problem(integrity violation) - Cannot Sync up emulator -HELP!

Can somebody help please - i keep getting this erro when trying to sycn
up my emulator to my Merged Replication DB. When i look into he error
message via the VS debugger i can see this text in the SqlException
error:
"The row update or insert cannot be reapplied due to an integrity
violation. [,,,,,]"
Anybody know what this problem could be? I have recently dropped an
recreated a lot of my tables and changed some data types but did not
think it would effect me this badly.
I have also disabled and re-enabled my merge replication db many times.
I am sure all my connection settings are correct and the problem
appears to be deeper than that.
Recently i have changed the constraint on all of my tables to "Not to
enforce relationships on insert / update". It seems like this is what
the emulator is trying to do though'
Suggestions GREATLY appreciated!!!!
Thanks,
SteveHi
Is this any help?
http://support.microsoft.com/default.aspx?scid=kb;en-us;889521
You may want to try logging the updates:
http://support.microsoft.com/default.aspx?scid=kb;en-us;312292
John
"steroche" wrote:
> Can somebody help please - i keep getting this erro when trying to sycn
> up my emulator to my Merged Replication DB. When i look into he error
> message via the VS debugger i can see this text in the SqlException
> error:
> "The row update or insert cannot be reapplied due to an integrity
> violation. [,,,,,]"
>
> Anybody know what this problem could be? I have recently dropped an
> recreated a lot of my tables and changed some data types but did not
> think it would effect me this badly.
>
> I have also disabled and re-enabled my merge replication db many times.
> I am sure all my connection settings are correct and the problem
> appears to be deeper than that.
>
> Recently i have changed the constraint on all of my tables to "Not to
> enforce relationships on insert / update". It seems like this is what
> the emulator is trying to do though'
>
> Suggestions GREATLY appreciated!!!!
> Thanks,
> Steve
>|||Im afraid not. I have tried everything at this stage and its driving me
crazy!!!!!
I have re-published my database about 10times i'd say and i always get
an error.
Generally I get one of 2 errors. If i have already created the database
the errors are:
Message "Row data cannot be set. [,,,,,]"
NativeError 28572
and
Message "Invalid row handle"
NativeError 0
However if i dont have it created previous to running it and it creates
it itself I get the error:
message "Run"
NativeError 28557
Message "The row update or insert cannot be reapplied due to an
integrity violation. [,,,,,]
NativeError 28549
What the hell is going on' I have checked all the tables to make sure
that the checkbox "Enforce Relationship for replication" IS checked so
the NOT FOR REPLICATION bug doesn't apply here.
I have checked over all my datatypes and relationships and the data
that they contain to ensure that there can be no FK conflicts.
I know the table is being created as i can see it on the CE Query
analyser but it contains no tables so this probably gives rise to the
second error but why is it not creating the db properly in the first
place'
I heard that compacting the db might help - how do i do that'|||Hi
Unfortunately I am not an expert on replication!
Hilary Cotter who has replied in microsoft.public.sqlserver.replication
knows alot more about replication than I.
John
"steroche" wrote:
> Im afraid not. I have tried everything at this stage and its driving me
> crazy!!!!!
> I have re-published my database about 10times i'd say and i always get
> an error.
> Generally I get one of 2 errors. If i have already created the database
> the errors are:
> Message "Row data cannot be set. [,,,,,]"
> NativeError 28572
> and
> Message "Invalid row handle"
> NativeError 0
> However if i dont have it created previous to running it and it creates
> it itself I get the error:
> message "Run"
> NativeError 28557
> Message "The row update or insert cannot be reapplied due to an
> integrity violation. [,,,,,]
> NativeError 28549
> What the hell is going on' I have checked all the tables to make sure
> that the checkbox "Enforce Relationship for replication" IS checked so
> the NOT FOR REPLICATION bug doesn't apply here.
> I have checked over all my datatypes and relationships and the data
> that they contain to ensure that there can be no FK conflicts.
> I know the table is being created as i can see it on the CE Query
> analyser but it contains no tables so this probably gives rise to the
> second error but why is it not creating the db properly in the first
> place'
> I heard that compacting the db might help - how do i do that'
>|||Check that your subset filters and merge filters in the publication are
correctly constructed.
You are potentially sending down some data on a foreign key that is getting
filtered out.
Rob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:F13AC93E-5354-4A2F-A066-2B3D22AA6D8F@.microsoft.com...
> Hi
> Unfortunately I am not an expert on replication!
> Hilary Cotter who has replied in microsoft.public.sqlserver.replication
> knows alot more about replication than I.
> John
> "steroche" wrote:
>> Im afraid not. I have tried everything at this stage and its driving me
>> crazy!!!!!
>> I have re-published my database about 10times i'd say and i always get
>> an error.
>> Generally I get one of 2 errors. If i have already created the database
>> the errors are:
>> Message "Row data cannot be set. [,,,,,]"
>> NativeError 28572
>> and
>> Message "Invalid row handle"
>> NativeError 0
>> However if i dont have it created previous to running it and it creates
>> it itself I get the error:
>> message "Run"
>> NativeError 28557
>> Message "The row update or insert cannot be reapplied due to an
>> integrity violation. [,,,,,]
>> NativeError 28549
>> What the hell is going on' I have checked all the tables to make sure
>> that the checkbox "Enforce Relationship for replication" IS checked so
>> the NOT FOR REPLICATION bug doesn't apply here.
>> I have checked over all my datatypes and relationships and the data
>> that they contain to ensure that there can be no FK conflicts.
>> I know the table is being created as i can see it on the CE Query
>> analyser but it contains no tables so this probably gives rise to the
>> second error but why is it not creating the db properly in the first
>> place'
>> I heard that compacting the db might help - how do i do that'
>>

Replication problem "can not insert null into colum step_name in sysjobs".

When trying to create a new publication using the wizzard i get the error message

"cannot insert null into colum step_name in sysjobs".

Replication was working fine on the server before. It stopped working when i installed SP3, i removed the old replication and tried setting it up again but get the error above when creating the publication.

Any ideas would be extremely useful. I have been unable to find any details of this on the web.

Many Thanks
Ash.Are you sure the clean up was successful? What I mean is there maybe some replication setups still reside in the system tables. I would check sysjobs first to see if there are unrecognized jobs in it and go from there.|||Originally posted by joejcheng
Are you sure the clean up was successful? What I mean is there maybe some replication setups still reside in the system tables. I would check sysjobs first to see if there are unrecognized jobs in it and go from there.

Thanks for the reply joejcheng.

I've tried quite a few different things. Like you the first thing I thought was to look in sysjobs and sysjobsteps, however there isn't anything in there that looks untoward.

Like you I'm inclined to think its something that hasn't been completely removed. I'd do a reinstall but its a production server so this isn't an option.

Replication porblem

Hi everybody,

i got this error message while i'm trying to execute my replication job.

"error 4813"

Expected the text length in data stream for bulk copy of
text, ntext, or image data."

Does anybody have an idea about it?
thanks

Let me know if the workarounds in the below link do not work for you.

http://www.starquest.com/Supportdocs/techSQDR/SQV00DR0013_BCPError.html

|||It seems to work! Thanks
I wonder if there is a Microsoft's KB article about it, 'cause i didn't find any!!

Replication on Named Instance SS2K

Is it possible to create a Pull Subscription on a named instance in SQL Server 2000 Developer Edition? When I try, I get an error message 14234 saying that it can't find the value '@.server'. Its hint is to look for the server in sp_helpserver. When I go to QA and connect to that named instance and run sp_helpserver, I see it there.

Sincerely,

can you post the complete error message with all the details. can you also tell us what version of sql server you're connecting to (select @.@.version in query analyzer), as well as what version of sql server you have on the machine that has Enterprise Manager?

Replication Message

Does anyone know what causes this message?
The row was inserted at 'CVTDEESQL005.ZenithSQL_L_060104' but could not be
inserted at 'ICK24BQZ0J.Zenith'. Procedure or function sp_MSsetrowmetadata
has too many arguments specified.
Our conflict log seems to be full of them
Does this apply?
http://support.microsoft.com/kb/319258/en-us
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
"Spike" <Spike@.discussions.microsoft.com> wrote in message
news:582616D9-62FB-4E73-A83F-01B3C835BBB6@.microsoft.com...
> Does anyone know what causes this message?
> The row was inserted at 'CVTDEESQL005.ZenithSQL_L_060104' but could not be
> inserted at 'ICK24BQZ0J.Zenith'. Procedure or function sp_MSsetrowmetadata
> has too many arguments specified.
> Our conflict log seems to be full of them
>
|||Hi Hilary, I don't think so as we do have service pack 3 applied. However,
it seems to be tied up with a new subscription database that we issued to the
users.
My main concern is to not lose any of changes that have been stored as
conflicts.
kind regards
Spike
"Hilary Cotter" wrote:

> Does this apply?
> http://support.microsoft.com/kb/319258/en-us
> --
> 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
>
> "Spike" <Spike@.discussions.microsoft.com> wrote in message
> news:582616D9-62FB-4E73-A83F-01B3C835BBB6@.microsoft.com...
>
>
|||Spike,
Check your merge agents in the replication monitor, you may see errors
related to space in the database primary tables. We started coming up with
this error over a year ago and after fighting with MS for a long time they
came back that is was a bug in the merger replication. If you view the
replication conflicts for your published database you will probably find a
lot of them. You should be able to resolve them by either keeping the winning
change or resolving, which ever columb has data in it (the other side should
read somthing about the data was changed at both locations, the update
won/lost.. (sorry can't remember the exact verbage). This should add any lost
data back to your database.
I am not sure what SP (if any) that microsoft added this fix to, they sent
us 2 patches to resolve the issue.
Check your database sizes and make sure they are not approaching the limits.
You may need to allocate more space for the primary tables.
Hope this helps you out.
Gary
"Spike" wrote:
[vbcol=seagreen]
> Hi Hilary, I don't think so as we do have service pack 3 applied. However,
> it seems to be tied up with a new subscription database that we issued to the
> users.
> My main concern is to not lose any of changes that have been stored as
> conflicts.
> kind regards
> Spike
> "Hilary Cotter" wrote: