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 Breaks after applying SP4

Hi
I installed SP4 on our enterprise server this morning and now all
replication jobs fail with the message "No such interface supported"
Has anyone seen this before / know how to resolve this?
We run Enterprise Edition on Win2003
Many Thanks
D
nope. I suggest you re-register the replication dll's and exes. I think you
can find them in c:\program files\microsoft sql server\mssql\80\com
"DJ" <DJ@.discussions.microsoft.com> wrote in message
news:CA106D94-FD82-4099-A342-BF75A0910D5B@.microsoft.com...
> Hi
> I installed SP4 on our enterprise server this morning and now all
> replication jobs fail with the message "No such interface supported"
> Has anyone seen this before / know how to resolve this?
> We run Enterprise Edition on Win2003
> Many Thanks
> D
|||There was apparently an as yet not fully explained registry ACLing problem in
SP4 setup per the following thread (reported by Tomasz Skorupa originally):
http://groups.google.com/group/micro...85 a5a37097d4
With more than one person hitting the same problem, I would like to try
again and see if I can find out more about the cause of it. Was the user
running SP4 setup on the machine the same as the one running SQL Server Agent
service? If not, did the account running SP4 have privilege for enumerating
account information for the SQL Server Agent service account?
-Raymond Mak
"DJ" wrote:

> Hi
> I installed SP4 on our enterprise server this morning and now all
> replication jobs fail with the message "No such interface supported"
> Has anyone seen this before / know how to resolve this?
> We run Enterprise Edition on Win2003
> Many Thanks
> D
|||Thanks for the reply Raymond and apologies for not replying sooner but I have
been off work.
I tried re-registering the dll following the steps you mentioned in the
other thread but this did not work for me.
I re-registered them and stopped and started SQL Agent. Did I need to do
anything else?
The version of sqlrepss.dll on my instance is :2000.80.2039.0
I was not connected as the service account so I may not have had the
prvilages for enumeration the account informaion.
I can run the replication from the command line but I always get the error
when using Enterprise Manager.
Do you have any other suggestions to resolve this?
Many Thanks
Daryl
"Raymond Mak [MSFT]" wrote:
[vbcol=seagreen]
> There was apparently an as yet not fully explained registry ACLing problem in
> SP4 setup per the following thread (reported by Tomasz Skorupa originally):
> http://groups.google.com/group/micro...85 a5a37097d4
> With more than one person hitting the same problem, I would like to try
> again and see if I can find out more about the cause of it. Was the user
> running SP4 setup on the machine the same as the one running SQL Server Agent
> service? If not, did the account running SP4 have privilege for enumerating
> account information for the SQL Server Agent service account?
> -Raymond Mak
>
> "DJ" wrote:
sql

Replication Advice Needed

Environment:
SQL 2000 SP4 on Windows 2003
Replication Type = Transactional Replication
Servers involved = server 1, server 2
Activity = server 1 has lots of activity for inserts,updates but no deletes
for 7:30 AM - 6 PM NY TIME then it becomes stable and becomes active again
from 9 PM - 4 AM NY TIME for offshore processing.
Situation:
I need to set up an environment to support minimum latency as low as few
seconds or so. I need to make sure that two systems stay in sync with Data
and schema though there are very less chances of making schema changes. I
thought of considering replication but there are few concerns.
1. Data can be replicated very quickly but then schema changes are a big
concern as replication blocks most of the schema changes.
2. When a new table is added on server A, I want it to be added to a server
B as well which can not happen without adding this table to a new or existing
publication and run snapshot\distribution agent etc..
3. On existing stored procedure, if I replicate the schema and executions,
do the subsequent alter procedure commands also get replicated? OR if the
proc is altered on Server 1, I need to manually run ALTER Table on server 2.
Then I thought of using Log Shipping and ran into following concerns.
1. If I set up transaction log backup very frequently on server 1 say every
minute, performance becomes a nightmare which is not acceptable at all in
this situation.
One more question on replication:
If I take the publisher server backup and restore on subscriber, how would
it affect replication? Would the replication be still funtional after restore
is done on subscriber?
Please advice if replication is a right approach in this scenario and if I
do implement replication, what additional steps would I need to take should
new schema changes appear. If Replication is not a good approach and Log
Shipping is a performance bottleneck, what other directions can I look at,.
Thanks for reading my request and I appreciate your suggestions.
Thanks in advance.
Nitin
Nitin,
to clarify a bit, I'd like to know what the second server is to be used
for - is it a HA box, or is it to be used for reporting?
Also, how definite are you on the idea of a few seconds latency?
My first reflex is database mirroring, with database snapshots if you
require a reporting solution, but let's find out more first.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi Paul:
Thanks fror your response. Second server is used only in read only mode.
There wont be new transactions other than what are happening on Server 1.
Also, Database mirroring is not supported on SQL 2005 yet and is turned off.
I dont know if we can mirror DB in SQL 2000. Few seconds latecy is ok. I have
spoken to people and they have said latency shouldnt go in minutes, seconds
are OK as nothing can be instantaneous in real world.
What are your thoughts on it.
-Nitin
"Paul Ibison" wrote:

> Nitin,
> to clarify a bit, I'd like to know what the second server is to be used
> for - is it a HA box, or is it to be used for reporting?
> Also, how definite are you on the idea of a few seconds latency?
> My first reflex is database mirroring, with database snapshots if you
> require a reporting solution, but let's find out more first.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Nitin,
database mirroring is not yet supported, but it is available. Some companies
are using it but admittedly it is a little worrying in a production
environment if it is not yet supported. Anyway, log shipping would have too
long a latency and mirroring doesn't exist in SQL Server 2000 so
transactional replication would be the obvious choice. Whether you'll
achieve the latency you require is difficult to say - I guess you'll need to
do a POC.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi Paul:
Since this is production environment, I really cant use DB Mirroring since
it is not supported if somethig goes wrong tomorrow and I cant get a support
on it, I will be in trouble. What do you recommend for moving the schema
changes to server 2 when changes were made on server 1 without replication
being stopped. For example: a dba can create index on an article without
affecting replication but now two servers are out of sync with schema. Do you
think there is a way to script out the schema differences and some automated
job can run those schema changes on server 2.
Nitin
"Paul Ibison" wrote:

> Nitin,
> database mirroring is not yet supported, but it is available. Some companies
> are using it but admittedly it is a little worrying in a production
> environment if it is not yet supported. Anyway, log shipping would have too
> long a latency and mirroring doesn't exist in SQL Server 2000 so
> transactional replication would be the obvious choice. Whether you'll
> achieve the latency you require is difficult to say - I guess you'll need to
> do a POC.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Nitin,
as you're on SQL 2000, the process is more manual but you can use
sp_repladdcolumn and sp_repldropcolumn for most things (including many
schema changes http://www.replicationanswers.com/AddColumn.asp). As I say,
this is manual, and you'll need to ensure this is done on the publications.
Index changes aren't propagated in SQL 2005 either so I tend to do these
manually although if I had a lot of subscribers or disconnected pull
subscribers I'd use sp_addscriptexec. Keeping the databases in sync will
require a strict way of working, and sometimes you might have to
reinitialize a table (yes, it's possible in transactional replication using
SQL 2000).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)