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 : The process coule not read file?

Hi.everyone.I use two computer in workgroup.I use A to be a publisher and distributor ,B to a Subscrible.When i create a snop in A computer and Create snopshot in "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\repldata\unc",when I use "view Synchronization Status" in B computer, the show "job already success start",but in A computer sqlserver error log show "Message
Replication-: agent LIUQINA\SERVER2005-TestTran-Tran-LIUQIANHOME\HOME-6 failed. The process could not read file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\ReplData\unc\LIUQINA$SERVER2005_TESTTRAN_TRAN\20070409150285\name_2.pre' due to OS error 3.". The publisher snapshot agent is servername\administrator.

I find a lot of message in internet ,but no one can help me .I try use same account and password in two computer.but no help.

Please tell me why and how to solve it ? Thanks.

Hello liuqian5036

You must use a UNC (Universal Naming Convention) for the path. A local path is not a valid path for the snapshot folder. For example, you should use \\<ServerName>\ReplData instead of "C:\....". You should share this folder on the network and give the snapshot account the necessary access rights to reach that folder. (read, write and modify is enough)

This address is specified when you configure the distributor. So you may go to the Replication folder in SQL Server instance you want to work on and then right click on the Replication folder and click Distributor Properties and click Publishers... item in the left panel. You will see Distribution Database column in the view and <Distributor Name>. Click the "..." just at the right side of it and change "Default Snapshot Folder" path as i told you above.

Ekrem ?nsoy

MCP, MCDST, MCDBA, MCAD.Net, MCSD.Net, MCSA, MCSE

|||Thank you very much,enaksanamun .but i have another question,When i run subscription ,I can see the replication is success,but In "View Synchronization Status" dialog it always run don't tell me it success.Why?|||

You are welcome liuqian5036.

I need you to tell me the story more specific please. For example, what kind of replication do you use? (Snapshot, Transactional, Merge).

What do you see on the Synchronization Status window? OK icon or Error icon? And please check the history out. Write here what it says on the history.

Ekrem ?nsoy

MCP, MCDST, MCDBA, MCAD.Net, MCSD.Net, MCSA, MCSE

|||Hi.Ekrem.Thank you.I am sorry to say I mistake the conception of "Synchronization Status Window",It's ok,no problem.Thank you help.

replication

wot should be the ans of the below scenario..
You are the administrator of a SQL Server 2000 computer. You want to set up snapshot replication on the server. The server will serve as Publisher and Distributor for a minimum of 40/50 Subscribers. Currently, you want to publish 3GB/4GB of data, but the data is expected to grow over time. Subscribers will receive a new snapshot each month. You want to minimize the workload on the Publisher/Distributor. Which two actions should you take to configure snapshot replication? (Each correct answer presents part of the solution. Choose two)
a. Store the snapshot in the default folder on the Publisher/Distributor.
b. Store the snapshot in an alternative folder on the Publisher/Distributor.
c. Store the snapshot in a shared folder on a file server.
d. Create pull subscriptions.
e. Create push subscriptions.I would store the snapshot on a file server
and create pull subscriptions
--
Dandy Weyn, Belgium
MCSE, MCSA, MCDBA, MCT
http://www.dandyman.net
Check my SQL Server resource pages (currently under construction)
http://www.dandyman.net/sql
"rahul" <anonymous@.discussions.microsoft.com> wrote in message
news:A26AAAD3-6275-4C3D-90D9-F97CEB0FE429@.microsoft.com...
> wot should be the ans of the below scenario...
> You are the administrator of a SQL Server 2000 computer. You want to set
up snapshot replication on the server. The server will serve as Publisher
and Distributor for a minimum of 40/50 Subscribers. Currently, you want to
publish 3GB/4GB of data, but the data is expected to grow over time.
Subscribers will receive a new snapshot each month. You want to minimize the
workload on the Publisher/Distributor. Which two actions should you take to
configure snapshot replication? (Each correct answer presents part of the
solution. Choose two)
>
> a. Store the snapshot in the default folder on the Publisher/Distributor.
> b. Store the snapshot in an alternative folder on the
Publisher/Distributor.
> c. Store the snapshot in a shared folder on a file server.
> d. Create pull subscriptions.
> e. Create push subscriptions.
>|||Although I am not a replication expert, I would choose c and d.
Pull subscriptions ( by default) cause the distribution process to run at
the subscriber ( and not the publisher) which offloads work from the
publisher... ( As a side note, SQL 2000 allows a push subscription to have
the subscriber do his own work as well, it is called remote activation..)
Storing the snapshot files somewhere OTHER than the publisher/distributor
simply means that the publisher does NOT have to do IO during the initial
sync with the subscriber..
Hope this help.s
"rahul" <anonymous@.discussions.microsoft.com> wrote in message
news:A26AAAD3-6275-4C3D-90D9-F97CEB0FE429@.microsoft.com...
> wot should be the ans of the below scenario...
> You are the administrator of a SQL Server 2000 computer. You want to set
up snapshot replication on the server. The server will serve as Publisher
and Distributor for a minimum of 40/50 Subscribers. Currently, you want to
publish 3GB/4GB of data, but the data is expected to grow over time.
Subscribers will receive a new snapshot each month. You want to minimize the
workload on the Publisher/Distributor. Which two actions should you take to
configure snapshot replication? (Each correct answer presents part of the
solution. Choose two)
>
> a. Store the snapshot in the default folder on the Publisher/Distributor.
> b. Store the snapshot in an alternative folder on the
Publisher/Distributor.
> c. Store the snapshot in a shared folder on a file server.
> d. Create pull subscriptions.
> e. Create push subscriptions.
>

replication

wot should be the ans of the below scenario...
You are the administrator of a SQL Server 2000 computer. You want to set up
snapshot replication on the server. The server will serve as Publisher and D
istributor for a minimum of 40/50 Subscribers. Currently, you want to publis
h 3GB/4GB of data, but the
data is expected to grow over time. Subscribers will receive a new snapshot
each month. You want to minimize the workload on the Publisher/Distributor.
Which two actions should you take to configure snapshot replication? (Each c
orrect answer presents part
of the solution. Choose two)
a. Store the snapshot in the default folder on the Publisher/Distributor.
b. Store the snapshot in an alternative folder on the Publisher/Distributor.
c. Store the snapshot in a shared folder on a file server.
d. Create pull subscriptions.
e. Create push subscriptions.I would store the snapshot on a file server
and create pull subscriptions
Dandy Weyn, Belgium
MCSE, MCSA, MCDBA, MCT
http://www.dandyman.net
Check my SQL Server resource pages (currently under construction)
http://www.dandyman.net/sql
"rahul" <anonymous@.discussions.microsoft.com> wrote in message
news:A26AAAD3-6275-4C3D-90D9-F97CEB0FE429@.microsoft.com...

quote:

---

> wot should be the ans of the below scenario...
> You are the administrator of a SQL Server 2000 computer. You want to set

---

up snapshot replication on the server. The server will serve as Publisher
and Distributor for a minimum of 40/50 Subscribers. Currently, you want to
publish 3GB/4GB of data, but the data is expected to grow over time.
Subscribers will receive a new snapshot each month. You want to minimize the
workload on the Publisher/Distributor. Which two actions should you take to
configure snapshot replication? (Each correct answer presents part of the
solution. Choose two)

quote:

---

>
> a. Store the snapshot in the default folder on the Publisher/Distributor.
> b. Store the snapshot in an alternative folder on the

---

Publisher/Distributor.

quote:

---

> c. Store the snapshot in a shared folder on a file server.
> d. Create pull subscriptions.
> e. Create push subscriptions.
>

---

|||Although I am not a replication expert, I would choose c and d.
Pull subscriptions ( by default) cause the distribution process to run at
the subscriber ( and not the publisher) which offloads work from the
publisher... ( As a side note, SQL 2000 allows a push subscription to have
the subscriber do his own work as well, it is called remote activation..)
Storing the snapshot files somewhere OTHER than the publisher/distributor
simply means that the publisher does NOT have to do IO during the initial
sync with the subscriber..
Hope this help.s
"rahul" <anonymous@.discussions.microsoft.com> wrote in message
news:A26AAAD3-6275-4C3D-90D9-F97CEB0FE429@.microsoft.com...

quote:

---

> wot should be the ans of the below scenario...
> You are the administrator of a SQL Server 2000 computer. You want to set

---

up snapshot replication on the server. The server will serve as Publisher
and Distributor for a minimum of 40/50 Subscribers. Currently, you want to
publish 3GB/4GB of data, but the data is expected to grow over time.
Subscribers will receive a new snapshot each month. You want to minimize the
workload on the Publisher/Distributor. Which two actions should you take to
configure snapshot replication? (Each correct answer presents part of the
solution. Choose two)

quote:

---

>
> a. Store the snapshot in the default folder on the Publisher/Distributor.
> b. Store the snapshot in an alternative folder on the

---

Publisher/Distributor.

quote:

---

> c. Store the snapshot in a shared folder on a file server.
> d. Create pull subscriptions.
> e. Create push subscriptions.
>

---