Replication error 28037

I am using merge replication between SQL Server 2000 sp3a running on windows
2000 server sp4 and sql server ce 2.0 over gprs.
First time when I synchronize is working fine, but when I add or modify data
in sql server ce database and try to replicate over gprs I get error 28037
(A request to send data to the computer running IIS has failed), during this
time my pocket pc is connected with the server (it respond to ping from the
computer running sql server, and pocket ie shows SQL Server CE Server
Agent ).
I tried to test replication on another database on only one table, it works
ok first time but when I modify many records on pocket pc database (100) and
replication fails with error 28037. If I modify the same amount of records
on server replication is working.
When I get this error I can not longer replicate over gprs but with cradle
it works. After I replicate on cradle and there is not data modified if I
replicate over gprs it works.
I believed that the amount of data uploaded from pocket pc to sql server is
to much so I created a new default merge agent profile with
downloadgenerationsperbatch set to 10 and uploadgenerationsperbatch set to 1
and recreated the publication, but nothing changed.
Any suggestion is welcome
thanks
Marius
Marius,
I am having exactly the same problem...did you manage to find out any solution?
Are we the only two people in the worldusing merge replication over GPRS? I hope not!
Cheers,
Nick
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
|||Hi Nick,
Till now I did not found any solution, we contacted microsoft support but
the problem still persist although I tried a hot fix and defined custom
merge agents. When we lead to a conclusion I'll let you know.
The strange thing is that the problem appears over GPRS with RDA also if
application try to pull a table that contains more then 20 changes (updates,
inserts, deletes), this number may vary but in small bounds.

> Marius,
> I am having exactly the same problem...did you manage to find out any
solution?
> Are we the only two people in the worldusing merge replication over GPRS?
I hope not!
> Cheers,
> Nick
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.

Replication Error - SharePoint 2007 DB

I have several SharePoint 2007 SQL 2005 databases that are replicating fine.

However, I have the WSS_Content _db that errors every time as shown below.

This only happens on the table shown, not on any of the other tables.

I am looking for confimation that this is a glitch withing SQL 2005 and there is nothing I can do about it pending a service release.

Anyone else run into this?

---

Error messages:

Source: Microsoft.SqlServer.Smo
Target Site: System.Collections.Specialized.StringCollection ScriptWithList(Microsoft.SqlServer.Management.Smo.DependencyCollection, Microsoft.SqlServer.Management.Smo.SqlSmoObject[])
Message: Script failed for Table 'dbo.NameValuePair_Hindi_CI_AS'.
Stack: at Microsoft.SqlServer.Management.Smo.Scripter.ScriptWithList(DependencyCollection depList, SqlSmoObject[] objects)
at Microsoft.SqlServer.Management.Smo.Scripter.ScriptWithList(SqlSmoObject[] objects)
at Microsoft.SqlServer.Replication.Snapshot.TransSmoScriptingManager.GenerateLogBasedArticleSchScript(Scripter scripter, BaseArticleWrapper articleWrapper, Table smoTable)
at Microsoft.SqlServer.Replication.Snapshot.TransSmoScriptingManager.GenerateLogBasedArticleScripts(ArticleScriptingBundle articleScriptingBundle)
at Microsoft.SqlServer.Replication.Snapshot.TransSmoScriptingManager.GenerateArticleScripts(ArticleScriptingBundle articleScriptingBundle)
at Microsoft.SqlServer.Replication.Snapshot.SmoScriptingManager.GenerateObjectScripts(ArticleScriptingBundle articleScriptingBundle)
at Microsoft.SqlServer.Replication.Snapshot.SmoScriptingManager.DoScripting()
at Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.DoScripting()
at Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.GenerateSnapshot()
at Microsoft.SqlServer.Replication.SnapshotGenerationAgent.InternalRun()
at Microsoft.SqlServer.Replication.AgentCore.Run() (Source: Microsoft.SqlServer.Smo, Error number: 0)

Can you exlain your scenario in more detail? Are you using transactional replication? Also, are you using Hindi as table name? What collation are you using?

Gary

|||

The 'Hindi' table is part of the database that was automatically installed by SharePoint, along with numerous others.

Wish I could include a photo.

Some of the other tables are Greek, Hebrew, Hindi, Hungarian, Japanese....etc

They start with Albanian and end with Vietnamese.

The backup works great until it hits the 'Hindi' table and then crashes.

If this wasn't a production environment I would delete the table and see what happened.

Thanks.

Replication Error

I have a database thats got sql as the engine and access 2000 for the client side.Now my problem is every time I edit a record this "Write Conflict" comes up. I did some investigating and I found out its due to a REPLICATIONCONFLICT ERROR.
Can anyone help me plsIs your Access FE running against a database that participates in merge replication? You need to have a serious talk with your DBA about whether you should be developing any app using a db that is already part of another app.|||the only application involved is access 2000, and the network techs are the dba|||what do you mean pls explain FE??sql

replication distribution server agents keep time out

Hi,
We have a distribution server that have all of our
transactional replications on it. All the distribution
agents and log reader agents keep time out and we have to
keep restart the agents.
What's the roob cause of this? Too many replications on
one distribution box? Or too many agents running at the
same time schedule?
Many thanks.
JJDon't the distribution agents keep trying for a certain number of times
before they error out? While they keep trying, you don't need to manually
restart them.
Distribution agents often times out in our environment. Causes I have found
are:
1. Blocking on the subscriber;
2. No more space on the subscriber database;
3. Server connection problem;
Richard
"JJ Wang" <jwang@.leapwireless.com> wrote in message
news:01a501c39284$479d5ee0$a401280a@.phx.gbl...
> Hi,
> We have a distribution server that have all of our
> transactional replications on it. All the distribution
> agents and log reader agents keep time out and we have to
> keep restart the agents.
> What's the roob cause of this? Too many replications on
> one distribution box? Or too many agents running at the
> same time schedule?
> Many thanks.
> JJ

Replication between 4 servers

Hello,
Currently I have successfully replicated data between 2
servers. The replication is for the most part stable but
does have its "issues" from time to time.I am still in the
process of understanding all situations that could cause
replication to error out.
Anyhow.. Whewww.. I am now in the position that I need to
replicate this data to 2 other servers.
My question is:
If replication occurs between SERVERA, SERVERB SERVERC
SERVERD.Lets say SERVERA replicates to SERVER B and
SERVERC but the replication fails between SERVERA and
SERVERC. Does the replication subscription I set up
between SERVERA and SERVERB also error out?
Sorry this is long winded.
Thanks,
niv
niv,
Not unless the cause of the replication failure between SERVER A and SERVER
C was caused by a network/hardware failure and the subscription on SERVER B
also relies on these resources. As long as the Log Reader and Distribution
agent is running as well as SERVER C and network connectivity is present it
should be fine.
This really is a broad question. I understand that you would like to cover
all possible scenarios and to ask you to be more specific would not be
relevant.
Charles Deaton
"niv" <niv@.hotmail.com> wrote in message
news:1b3c701c44fb3$e2c83b50$a401280a@.phx.gbl...
> Hello,
> Currently I have successfully replicated data between 2
> servers. The replication is for the most part stable but
> does have its "issues" from time to time.I am still in the
> process of understanding all situations that could cause
> replication to error out.
> Anyhow.. Whewww.. I am now in the position that I need to
> replicate this data to 2 other servers.
> My question is:
> If replication occurs between SERVERA, SERVERB SERVERC
> SERVERD.Lets say SERVERA replicates to SERVER B and
> SERVERC but the replication fails between SERVERA and
> SERVERC. Does the replication subscription I set up
> between SERVERA and SERVERB also error out?
> Sorry this is long winded.
> Thanks,
> niv
|||For transactional, there will either be one Distribution Agent per
subscription (an independent agent) or one Distribution Agent per
publication database and subscription database pair (a shared agent). For
merge, each merge subscription has its own Merge Agent that connects to and
updates both the Publisher and the Subscriber. So, as the agents in your
case are independant, a failure in one will not affect the other in a sense
of the replication process. However, as Charles points out, if the error is
a general one to your network then both agents will fail.
HTH,
Paul Ibison

Replication and Rebuild index

Hi:
If replication and rebuild index happen at the same time, which one
will fail ?
Please advice
JCVoon
This really depends on a few factors. Firstly, how do you rebuild your
indexes? DBCC DBREINDEX and DBCC INDEXDEFRAG are considered offline and
online operations respectively, due to the different locking behaviour. In
SQL Server 2005 this corresponds to ALTER INDEX ALL on tablename REBUILD
WITH (ONLINE = ON) and ALTER INDEX ALL on tablename REBUILD WITH (ONLINE =
OFF), or the old DBCC syntax can be used as well. The online options should
be compatible with the distribution or merge agent running while the offline
is less likely. It really all depends on the QUERYTIMEOUT parameter's value
and how this realtes to the time taken to rebuild the table indexes.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||It depends on which one starts first. index rebuild requires an exclusive
lock on the table. If the rebuild starts first, replication will not be able
to update it until the rebuild finishes. If the replication is updating the
table when the index rebuild attempts to run, it will fail because it can not
get an exclusive lock.
Regards
John
"jcvoon" wrote:

> Hi:
> If replication and rebuild index happen at the same time, which one
> will fail ?
> Please advice
> JCVoon
>

Replication and Rebuild index

Hi:
If replication and rebuild index happen at the same time, which one
will fail ?
Please advice
JCVoonThis really depends on a few factors. Firstly, how do you rebuild your
indexes? DBCC DBREINDEX and DBCC INDEXDEFRAG are considered offline and
online operations respectively, due to the different locking behaviour. In
SQL Server 2005 this corresponds to ALTER INDEX ALL on tablename REBUILD
WITH (ONLINE = ON) and ALTER INDEX ALL on tablename REBUILD WITH (ONLINE =
OFF), or the old DBCC syntax can be used as well. The online options should
be compatible with the distribution or merge agent running while the offline
is less likely. It really all depends on the QUERYTIMEOUT parameter's value
and how this realtes to the time taken to rebuild the table indexes.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)|||It depends on which one starts first. index rebuild requires an exclusive
lock on the table. If the rebuild starts first, replication will not be able
to update it until the rebuild finishes. If the replication is updating the
table when the index rebuild attempts to run, it will fail because it can no
t
get an exclusive lock.
Regards
John
"jcvoon" wrote:

> Hi:
> If replication and rebuild index happen at the same time, which one
> will fail ?
> Please advice
> JCVoon
>

Replication and Rebuild index

Hi:
If replication and rebuild index happen at the same time, which one
will fail ?
Please advice
JCVoonThis really depends on a few factors. Firstly, how do you rebuild your
indexes? DBCC DBREINDEX and DBCC INDEXDEFRAG are considered offline and
online operations respectively, due to the different locking behaviour. In
SQL Server 2005 this corresponds to ALTER INDEX ALL on tablename REBUILD
WITH (ONLINE = ON) and ALTER INDEX ALL on tablename REBUILD WITH (ONLINE =OFF), or the old DBCC syntax can be used as well. The online options should
be compatible with the distribution or merge agent running while the offline
is less likely. It really all depends on the QUERYTIMEOUT parameter's value
and how this realtes to the time taken to rebuild the table indexes.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)|||It depends on which one starts first. index rebuild requires an exclusive
lock on the table. If the rebuild starts first, replication will not be able
to update it until the rebuild finishes. If the replication is updating the
table when the index rebuild attempts to run, it will fail because it can not
get an exclusive lock.
Regards
John
"jcvoon" wrote:
> Hi:
> If replication and rebuild index happen at the same time, which one
> will fail ?
> Please advice
> JCVoon
>

replication and identity problem

Every time I start replication i get following error:
Cannot insert explicit value for identity column in table 'xxxx' when
IDENTITY_INSERT is seto to OFF
the publisher side:
xxxx table has identity set on one column
the subscriber side
xxxx table has identity set on one column.
How can I change or how can I set IDENTITY_INSERT to ON during replication
process?
regards,
DaliborNot sure if this is the right way but this is what I did:
Go to the insert stored proc for replication on the
Subscriber DB.(sp_msins_TableName)
Comment out thie insert line for that column.
>--Original Message--
>Every time I start replication i get following error:
>Cannot insert explicit value for identity column in
table 'xxxx' when
>IDENTITY_INSERT is seto to OFF
>the publisher side:
>xxxx table has identity set on one column
>the subscriber side
>xxxx table has identity set on one column.
>How can I change or how can I set IDENTITY_INSERT to ON
during replication
>process?
>regards,
>Dalibor
>
>.
>|||Use NOT FOR REPLICAITON on the identity.
e.g.
CREATE TABLE dbo.test (
id int IDENTITY (1, 1) NOT FOR REPLICATION NOT NULL ,
office_location varchar (10) NOT NULL ,
...
)
Linchi
>--Original Message--
>Every time I start replication i get following error:
>Cannot insert explicit value for identity column in
table 'xxxx' when
>IDENTITY_INSERT is seto to OFF
>the publisher side:
>xxxx table has identity set on one column
>the subscriber side
>xxxx table has identity set on one column.
>How can I change or how can I set IDENTITY_INSERT to ON
during replication
>process?
>regards,
>Dalibor
>
>.
>

Replication

Hi everybody.
I am working on merge replication first time and I ran a
synchronizing processing and get error message:
Cannot insert the value NULL into column 'objid',
table 'ReplicationDB_1.dbo.sysmergeschemaarticles';
column does not allow nulls. INSERT fails.
My snapshots has created successfully.
Any suggestions or advices?
Thank you Mike.
I believe this is a bug. Contact PSS for a hot fix.
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:8bbf01c432aa$26749460$a001280a@.phx.gbl...
> Hi everybody.
> I am working on merge replication first time and I ran a
> synchronizing processing and get error message:
> Cannot insert the value NULL into column 'objid',
> table 'ReplicationDB_1.dbo.sysmergeschemaarticles';
> column does not allow nulls. INSERT fails.
> My snapshots has created successfully.
> Any suggestions or advices?
> Thank you Mike.
>
>

Replication

I have replication configured in an sql 2005 environment. I have
executed the wizard twice but each time the following maintenance jobs
are missing
Reinitialize subscriptions having data validation failures
Agent history clean up: distribution
Replication monitoring refresher for distribution.
Replication agents checkup
Distribution clean up: distribution
Expired subscription clean up
If someone can tell me what most be done to have these jobs created
or why the wizard failed to create them it would be a big help.What do you set up exactly? Distributor, Publisher and Subscriber? Also what
Replication method do you setup? Merge, Transactional, Snapshot?
--
Ekrem Önsoy
"NC3" <ncoleman3@.yahoo.com> wrote in message
news:1191870323.081389.186990@.r29g2000hsg.googlegroups.com...
>I have replication configured in an sql 2005 environment. I have
> executed the wizard twice but each time the following maintenance jobs
> are missing
>
> Reinitialize subscriptions having data validation failures
> Agent history clean up: distribution
> Replication monitoring refresher for distribution.
> Replication agents checkup
> Distribution clean up: distribution
> Expired subscription clean up
> If someone can tell me what most be done to have these jobs created
> or why the wizard failed to create them it would be a big help.
>|||On Oct 8, 4:22 pm, Ekrem =D6nsoy <ek...@.btegitim.com> wrote:
> What do you set up exactly? Distributor, Publisher and Subscriber? Also w=hat
> Replication method do you setup? Merge, Transactional, Snapshot?
> --
> Ekrem =D6nsoy
> "NC3" <ncolem...@.yahoo.com> wrote in message
> news:1191870323.081389.186990@.r29g2000hsg.googlegroups.com...
>
> >I have replication configured in an sql 2005 environment. I have
> > executed the wizard twice but each time the following maintenance jobs
> > are missing
> > Reinitialize subscriptions having data validation failures
> > Agent history clean up: distribution
> > Replication monitoring refresher for distribution.
> > Replication agents checkup
> > Distribution clean up: distribution
> > Expired subscription clean up
> > If someone can tell me what most be done to have these jobs created
> > or why the wizard failed to create them it would be a big help.- Hide q=uoted text -
> - Show quoted text -
I have transactional replication configured using a remote distributor
to 'push' articles to a subscriber with ALL jobs configured to run at
the distributor.|||Hello,
What version of SQL 2005 you are using. As there was bug prior SP1. try
increasing the size of your model db try configuring again.
Thanks
Ajay Rengunthwar
MCDBA,MCTS
"NC3" <ncoleman3@.yahoo.com> wrote in message
news:1191876823.867493.221310@.50g2000hsm.googlegroups.com...
On Oct 8, 4:22 pm, Ekrem Önsoy <ek...@.btegitim.com> wrote:
> What do you set up exactly? Distributor, Publisher and Subscriber? Also
> what
> Replication method do you setup? Merge, Transactional, Snapshot?
> --
> Ekrem Önsoy
> "NC3" <ncolem...@.yahoo.com> wrote in message
> news:1191870323.081389.186990@.r29g2000hsg.googlegroups.com...
>
> >I have replication configured in an sql 2005 environment. I have
> > executed the wizard twice but each time the following maintenance jobs
> > are missing
> > Reinitialize subscriptions having data validation failures
> > Agent history clean up: distribution
> > Replication monitoring refresher for distribution.
> > Replication agents checkup
> > Distribution clean up: distribution
> > Expired subscription clean up
> > If someone can tell me what most be done to have these jobs created
> > or why the wizard failed to create them it would be a big help.- Hide
> > quoted text -
> - Show quoted text -
I have transactional replication configured using a remote distributor
to 'push' articles to a subscriber with ALL jobs configured to run at
the distributor.

replicating to denormalized db

SQL2K sp3
Howdy all ...its been some time since Ive been around these parts.
I may need to start replicating to a denormalized DB. I tested this a while
back and it was grueling. After spinning my wheels for a couple of weeks my
then emplyer decided he wanted to keep the db as is so I just did normal
replication. Now if memory servers correctly, the only method I found for
successful replication to a denormalized db was to create Clustered Indexed
Views on the Publisher, and then replicate those, not the tables. I recall
trying another method (dont remember what it was), that was totally
unsuccessful. I need to do 1 way, continuous, Transactional replication. So
my questions are:
1; Are there other methods?
2; If so, what are they?
3; Are they in Hillary's book?
4; I may have the luxury of making the Subscriber SQL2K5, will that help
accomplish my goials.
TIA, ChrisR
Chris,
as an alternative to indexed views, you could use transformable
subscriptions, which is a mix of replication and DTS. This applies to SQL
Server 2000 rather than 2005 AFAIR.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)