Replication error with sqlserver mobile:A request to send data to the computer running IIS is fa

I have smilar kind of an issue with replication. I had sucessfully done replication with Sqlce2.0 on sql server 2000. In development machine I had VS 2003, sqlce development tools.

Now I use the same code done in VS 2003 into VS2005, it sucessfully converted the code.

In server machine (win 2003) I installed sql server 2000, sql server 2000 service pack 4, SP4 merge replication components, sql server 2005 mobile server tools and .Net framework 2.0. Created pubication sucessfuly. In this machine I configured IIS as per the web synchronization wizard. Gave anyonymous permissions. Virual direcory is created sucessfully. I tested the server agent in IE http://myservername/aliasname/sqlcesa30.dll.

SQL Server Mobile Server Agent 3.0 is shown

My application opened successfuly in windows mobile 5.0 Pocket PC emulator. When try to sync its dislays error "A request to send data to the computer running IIS is failed, see Hrresult"

No firewall in both development and server machines.

The same code works if its sqlce20 perfectly with vs2003 code. Not in this

Can anyone tell me whats wrong in this?

Regards

Arif

I have moved this to the SQL Mobile forum for someone in the SQL Mobile team to look at.

Thanks

Amit

|||

Hello All,

It worked for me. I read some of the messages in this forum and found that I need to connect the Windows Mobile PPC emulator using activesync. I did it and now its working fine.

I was now able to do sync with both PPC2003 on Sql server 2000 and sqlce20 (VS2003 environment)

AND also

Windows mobile 5 on Sql Server 2000, SQL Server SP4, SP4 replication components, Sql server mobile (VS2005) succesfuly

Thanks for the questions and responses in this forum

Arif

www.anteriorsoft.com

|||

Thanks a lot for your compliments!

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

Replication design

Hi,
I have the following scenario, and need to configure
replication for this. Pls advice.
We have 3 SQL server databases, at 3 locations on SQL
server 2000 servers. They are connected over WAN by 2
MBPS link (triangle). I have to configure replication on
this. Database has around 200 tables, and size of
database would be around 200-500 MB each. Changes would
be minor on daily basis.
I have these servers at following locations.
Loc1 (HeadOffice)
Loc2 (branch office)
Loc3 (branch office)
Data has to replicate from Loc2 and Loc3 to Loc1 at short
intervals during the day.
Somewhere in midnight (off peak hours), data has to
replicate from Loc1 to Loc2 and Loc3 (for changes made at
Loc1 to be reflected in Loc2 and Loc3).
These database are modified only during the day, and
number of users at each location will not exceed 30.
I have following queries
- Can I configure Transactional replication for Loc2 ->
Loc1 and Loc3 -> Loc1 to replicate at short intervals.
And additionally Snapshot to happen at midnight from
Loc1 -> Loc2 and Loc3.
Or do I require Merge replication for this scenario. (or
any other solution you think would suit this requirement)
Pls suggest.
Thanx,
Shrikant,
the easiest scenario would be mege replication. Snapshot will copy over the
whole tables and unless the tables are small or all rows are always updated,
this is not recommended, and you'd have to set up replication each time
after the snapshot - possible but not so nice. Also, if the data is
partitioned then great, but if not then merge will take care of that with
the conflict resolvers. The only thing is that you won't be able to easily
prevent the download of data from Loc1 until the evening, as these changes
will propagate during the frequent synchronizations. If this is not at all
desirable, than you might have to consider a more radical solution - you
could have Loc1 as the publisher but use unidirectional merge with the
subscribers and reinitialize each evening.
HTH,
Paul Ibison
|||Hi Paul,
Thanx for your reply.
But would not be using the bi-directional transactional
replication solve this ?
Loc1 acts as Publisher with Loc2 and Loc3 as subscribers.
And then Loc2 and Loc3 as Publishers, and Loc1 as
Subscriber ?
regds,
Shrikant

>--Original Message--
>Shrikant,
>the easiest scenario would be mege replication. Snapshot
will copy over the
>whole tables and unless the tables are small or all rows
are always updated,
>this is not recommended, and you'd have to set up
replication each time
>after the snapshot - possible but not so nice. Also, if
the data is
>partitioned then great, but if not then merge will take
care of that with
>the conflict resolvers. The only thing is that you won't
be able to easily
>prevent the download of data from Loc1 until the
evening, as these changes
>will propagate during the frequent synchronizations. If
this is not at all
>desirable, than you might have to consider a more
radical solution - you
>could have Loc1 as the publisher but use unidirectional
merge with the
>subscribers and reinitialize each evening.
>HTH,
>Paul Ibison
>
>.
>
|||Shrikant,
this would be an option. If you expect conflicts then it can become terribly complicated, and the initial setup is not straightforward, but you're right - it is in some ways a simpler solution. To You might want to have a look at the most recent issue of
SQL Server magazine if you're thinking of going down this route - there is a nice article on setting it up.
Regards,
Paul Ibison

Replication Between Different Versions of SQL Server

Hello,

We are trying to set up replication between different versions of SQL
Server (7 & 2000).

This is how the 2 servers are now setup:
DB1 - External web-server w/SQL Server 7
DB2 - Internal server w/SQL Server 2000

REPLICATION SETUP
This is how we need the replication to be set up. They are all
Transactional Replications.

DISTRIBUTION:
This is set up on DB2, which is running on 2000

WITH PUBLISHERS ON DB1, AND PULL SUBSCRIPTIONS ON DB2:
dbo.Employment_App & dbo.Employ_Jobs (together in one replication)
dbo.Feedback
NOTE: This set of replications work some of the time, but make DB1 &
DB2 very slow when running. A lot of times, the jobs say "Retrying
Job", but they usually will eventually work.

WITH PUBLISHERS AND PUSH SUBSCRIPTIONS ON DB2:
dbo.Jobs
dbo.Releases
dbo.Search
NOTE: This set of replications used to work when DB1 & DB2 both ran on
SQL Server 7 with 2000 Enterprise Manager's. But since we moved the
data to an internal server (DB2) that runs on 2000, it doesn't work at
all.

We've researched the problem, and found an article by MS called
"Replication Between Different Versions of SQL Server" at
http://msdn.microsoft.com/library/d...plimpl_4joy.asp
that states that this setup should be possible (on Combination 3 for
Transactional Replications).

But it's not working at all. Are there some steps that we need to
check to have replication setup between 2 servers running on different
versions of SQL Server (7 & 2000)? Any & all help & advice is
appreciated. Thanks.

KWilliamsJust to follow up on this - I'd be very interested to know if anyone has
successfully got a replication to work with 6.5 as the publisher /
distribution and MSDE (7 or 2000) as the subscriber?

Thanks

Chris Gadsby

"KWilliams" <webmaster@.douglas-county.com> wrote in message
news:e9cb71d3.0311050735.38e1b491@.posting.google.c om...
> Hello,
> We are trying to set up replication between different versions of SQL
> Server (7 & 2000).
> This is how the 2 servers are now setup:
> DB1 - External web-server w/SQL Server 7
> DB2 - Internal server w/SQL Server 2000
> REPLICATION SETUP
> This is how we need the replication to be set up. They are all
> Transactional Replications.
> DISTRIBUTION:
> This is set up on DB2, which is running on 2000
> WITH PUBLISHERS ON DB1, AND PULL SUBSCRIPTIONS ON DB2:
> dbo.Employment_App & dbo.Employ_Jobs (together in one replication)
> dbo.Feedback
> NOTE: This set of replications work some of the time, but make DB1 &
> DB2 very slow when running. A lot of times, the jobs say "Retrying
> Job", but they usually will eventually work.
> WITH PUBLISHERS AND PUSH SUBSCRIPTIONS ON DB2:
> dbo.Jobs
> dbo.Releases
> dbo.Search
> NOTE: This set of replications used to work when DB1 & DB2 both ran on
> SQL Server 7 with 2000 Enterprise Manager's. But since we moved the
> data to an internal server (DB2) that runs on 2000, it doesn't work at
> all.
> We've researched the problem, and found an article by MS called
> "Replication Between Different Versions of SQL Server" at
http://msdn.microsoft.com/library/d...plimpl_4joy.asp
> that states that this setup should be possible (on Combination 3 for
> Transactional Replications).
> But it's not working at all. Are there some steps that we need to
> check to have replication setup between 2 servers running on different
> versions of SQL Server (7 & 2000)? Any & all help & advice is
> appreciated. Thanks.
> KWilliams

Replication - SQLServer Agent uses System Account

When I attempt to set up replication on my local box, I receive the error -'SQLServer Agent uses the Systems Account, which causes replication betweem servers to fail'.
Why does this happen? And can I overcome this?
Thanks :)
BiancaStart SQLServerAgent service using a domain account. This account must have the appropriate rights on teh Publisher, Distributor and Subscriber computers (depending on the replication type)

Originally posted by Bianca_J
When I attempt to set up replication on my local box, I receive the error -'SQLServer Agent uses the Systems Account, which causes replication betweem servers to fail'.

Why does this happen? And can I overcome this?

Thanks :)

Bianca|||Thank you for your post :)

What is a Domain Account?

Is this set up in Windows 2000? And if I set up a Domain Account in my local Windows 2000 box - how do I have right over a remore server?

Thanks

Bianca

Replication - Changes to Server databases impact to local database

We have a SQLSERVER database that is replicated to many users.
We are currently in an expansion phase where we need to make changes
to the server database. Each time we rollout a new release, we are
deleting the local replicating database and recreating.

Is there any way to automatically transfer the changes from the server
to existing local database without deleting?dipillama@.nswccd.navy.mil (Michael diPilla) wrote in message news:<4e67e68b.0308181234.4c8e5e98@.posting.google.com>...
> We have a SQLSERVER database that is replicated to many users.
> We are currently in an expansion phase where we need to make changes
> to the server database. Each time we rollout a new release, we are
> deleting the local replicating database and recreating.
> Is there any way to automatically transfer the changes from the server
> to existing local database without deleting?

It's not clear what you mean by 'changes' - changes to table
structures can be replicated if you make them through the publication
properties dialogue.

I'd suggest you post this in microsoft.public.sqlserver.replication,
as you'll probably get a better answer there.

Simon

Replication

What is replication in sqlserver and where it is used,and how can i
configure/use it.
And what is publication and subscription.
dijas
This is not really possible to answer in a simple posting. Have a thorough
look in BOL where these terms are defined. Have a look at Hilary's book (see
url below). If you are interested, have a look at the Microsoft 3-day
course. There are several people on the newsgroup who will be able to help
with any specific questions you have.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

replication

hey anybody knows where i will get detail information on
SQLServer 2000 Replication?
i want to go through all replication types?
Please let me know
thanks and regards
hrishikeshCheck
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/replsql/replover_694n.asp.
--
Dejan Sarka, SQL Server MVP
FAQ from Neil & others at: http://www.sqlserverfaq.com
Please reply only to the newsgroups.
PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"hrishikesh" <musaleh@.mahindrabt.com> wrote in message
news:094901c36df2$58d6c810$a301280a@.phx.gbl...
> hey anybody knows where i will get detail information on
> SQLServer 2000 Replication?
> i want to go through all replication types?
> Please let me know
> thanks and regards
> hrishikesh
>