Hi,
I have problems with merge replication over modem connection.
It works fine over LAN but with modem connection I got error:
"The merge process encountered an unexpected network error.".
I have tried to modified timeout, query timeout etc. - nothing helps.
Problems started for few days ago. We have been using merge replication for
the last two years without any problems.
Additional information:
Server: SQL Server 2000, SP3, Win 2K SP4, dual processor, 1 GB Memory
150 Clients: MSDE SP3, Win 2K SP4
Anyone has seen this problem before?
Thanks and Best Regards,
Rafael
All the time. Are you using the slow link profile?
If you still get this using the slow link profile you are likely
encountering network problems, or have an unstable line. Try to drop your
packet size.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"raffe" <raffe@.community.nospam> wrote in message
news:D0096C0B-3846-4948-9835-4E293378E14D@.microsoft.com...
> Hi,
> I have problems with merge replication over modem connection.
> It works fine over LAN but with modem connection I got error:
> "The merge process encountered an unexpected network error.".
> I have tried to modified timeout, query timeout etc. - nothing helps.
> Problems started for few days ago. We have been using merge replication
for
> the last two years without any problems.
> Additional information:
> Server: SQL Server 2000, SP3, Win 2K SP4, dual processor, 1 GB Memory
> 150 Clients: MSDE SP3, Win 2K SP4
> Anyone has seen this problem before?
> Thanks and Best Regards,
> Rafael
|||Thanks for your answer.
I have tested with slow link profile, I have creted my own profile with very
small packet size and nothing helps. I now that it worked fine last week and
there is still a lot of clients without any replicatiopn problems.
Raffe
"Hilary Cotter" wrote:
> All the time. Are you using the slow link profile?
> If you still get this using the slow link profile you are likely
> encountering network problems, or have an unstable line. Try to drop your
> packet size.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> Now available for purchase at:
> http://www.nwsu.com/0974973602.html
>
> "raffe" <raffe@.community.nospam> wrote in message
> news:D0096C0B-3846-4948-9835-4E293378E14D@.microsoft.com...
> for
>
>
|||can you start logging to try to find out exactly why it is timing out like
this?
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"raffe" <raffe@.community.nospam> wrote in message
news:ACCC9978-A042-40B3-8A96-3168A77CF4ED@.microsoft.com...[vbcol=seagreen]
> Thanks for your answer.
> I have tested with slow link profile, I have creted my own profile with
> very
> small packet size and nothing helps. I now that it worked fine last week
> and
> there is still a lot of clients without any replicatiopn problems.
> Raffe
> "Hilary Cotter" wrote:
|||How can I enable logging for merge agents?
"Hilary Cotter" wrote:
> can you start logging to try to find out exactly why it is timing out like
> this?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> Now available for purchase at:
> http://www.nwsu.com/0974973602.html
> "raffe" <raffe@.community.nospam> wrote in message
> news:ACCC9978-A042-40B3-8A96-3168A77CF4ED@.microsoft.com...
>
>
|||Hi Raffe,
I think Hilary means the Agent Logs described in the following knowledge
base article
HOW TO: Enable Replication Agents for Logging to Output Files in SQL Server
http://support.microsoft.com/kb/312292
However, I would like to set your expectation that replication issues tend
to be very complex and hard to troubleshoot in newsgroups. If you need
instance and insight assistance, I recommend that you open a Support
incident with Microsoft Product Support Services (PSS) so that a dedicated
Support Professional can work with you in a more timely and efficient
manner. If you need any help in this regard, please let me know.
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
Showing posts with label connection. Show all posts
Showing posts with label connection. Show all posts
Wednesday, March 28, 2012
Monday, March 26, 2012
Merge replication using files.
Is it possible to use merge replication without direct connection from suscriber/publisher? I'm trying to find a solution to use files for send/receive merge-replication info from/to server.
^_^,
Thank You.
There is currently no support for Merge replication with files.
Are you concerned about the snapshot fules or you want all of the syncs to be using files? If the former, you should look at alt_snapshot_folder. If the latter, there is no support as of now.
|||I needed for all syncs :(.
Do you feel there's a way to bypass merge-web-synchronization and use files to do sync.?
I don't know the communication process, but simplifying, maybe we can merge request/s in an ouput file, and response/s in an input file ...
Than you.
|||Hi,
Thanks for your suggestion. This is not a new idea and has been floating in our minds for some time. We may probably take another look at it for the next release but it may not make it.
Monday, March 19, 2012
Merge replication over VPN
I currently have a client who needs to replicate a database between a server
in the office and a computer at home using a VPN connection.
Here is the currnet setup:
-Merge Replication
-Both the server and the client have SQLSERVERAgent logged in with the same
username and password for pass-through authentication
-Subscriber impersonates SqlServerAgent
-Anonymous subscription
The snapshot has been created successfully on the server and I am able to
register the client on the server's Enterprise Manager (so they can see each
other). The replication starts and runs for quite a while (most of the work
is done). Eventually, it fails with the message
//<servername>/<sharename>/<filname>.dri could not be propagated to the
subscriber. With no further details. I don't think it is security related,
because most of the work is already done.
Any ideas what I'm missing?
You might try, from the client, to see if you can browse this share. When I
have set it up, it required an entry in the HOSTS file to map the IP address
to the NETBIOS name.
HTH,
Paul Ibison
|||The share is visible. I fixed that with an entry in the HOSTS file in the
beginning.
"Paul Ibison" wrote:
> You might try, from the client, to see if you can browse this share. When I
> have set it up, it required an entry in the HOSTS file to map the IP address
> to the NETBIOS name.
> HTH,
> Paul Ibison
>
|||OK, if it is running, transferring the snapshot and fails after a while, you
might try increating the -QueryTimeout parameter of the merge agent's
profile.
HTH,
Paul Ibison
|||I did that already as well after having a timeout problem. The current
problem just says that the file could not be propagated to the subscriber.
"Paul Ibison" wrote:
> OK, if it is running, transferring the snapshot and fails after a while, you
> might try increating the -QueryTimeout parameter of the merge agent's
> profile.
> HTH,
> Paul Ibison
>
>
|||Problem Solved:
It turns out that there is no guarantee that the order that records are
inserted during replication will be the same as when they were inserted
originally. Therefore, it is possible that a chile record can be inserted
before its parent, causing a conflict with the foreign key constraint.
After setting all foreign key constraints to "not for replication", the
client took the snapshot without a problem.
"b1@.ckh013" wrote:
> I currently have a client who needs to replicate a database between a server
> in the office and a computer at home using a VPN connection.
> Here is the currnet setup:
> -Merge Replication
> -Both the server and the client have SQLSERVERAgent logged in with the same
> username and password for pass-through authentication
> -Subscriber impersonates SqlServerAgent
> -Anonymous subscription
> The snapshot has been created successfully on the server and I am able to
> register the client on the server's Enterprise Manager (so they can see each
> other). The replication starts and runs for quite a while (most of the work
> is done). Eventually, it fails with the message
> //<servername>/<sharename>/<filname>.dri could not be propagated to the
> subscriber. With no further details. I don't think it is security related,
> because most of the work is already done.
> Any ideas what I'm missing?
in the office and a computer at home using a VPN connection.
Here is the currnet setup:
-Merge Replication
-Both the server and the client have SQLSERVERAgent logged in with the same
username and password for pass-through authentication
-Subscriber impersonates SqlServerAgent
-Anonymous subscription
The snapshot has been created successfully on the server and I am able to
register the client on the server's Enterprise Manager (so they can see each
other). The replication starts and runs for quite a while (most of the work
is done). Eventually, it fails with the message
//<servername>/<sharename>/<filname>.dri could not be propagated to the
subscriber. With no further details. I don't think it is security related,
because most of the work is already done.
Any ideas what I'm missing?
You might try, from the client, to see if you can browse this share. When I
have set it up, it required an entry in the HOSTS file to map the IP address
to the NETBIOS name.
HTH,
Paul Ibison
|||The share is visible. I fixed that with an entry in the HOSTS file in the
beginning.
"Paul Ibison" wrote:
> You might try, from the client, to see if you can browse this share. When I
> have set it up, it required an entry in the HOSTS file to map the IP address
> to the NETBIOS name.
> HTH,
> Paul Ibison
>
|||OK, if it is running, transferring the snapshot and fails after a while, you
might try increating the -QueryTimeout parameter of the merge agent's
profile.
HTH,
Paul Ibison
|||I did that already as well after having a timeout problem. The current
problem just says that the file could not be propagated to the subscriber.
"Paul Ibison" wrote:
> OK, if it is running, transferring the snapshot and fails after a while, you
> might try increating the -QueryTimeout parameter of the merge agent's
> profile.
> HTH,
> Paul Ibison
>
>
|||Problem Solved:
It turns out that there is no guarantee that the order that records are
inserted during replication will be the same as when they were inserted
originally. Therefore, it is possible that a chile record can be inserted
before its parent, causing a conflict with the foreign key constraint.
After setting all foreign key constraints to "not for replication", the
client took the snapshot without a problem.
"b1@.ckh013" wrote:
> I currently have a client who needs to replicate a database between a server
> in the office and a computer at home using a VPN connection.
> Here is the currnet setup:
> -Merge Replication
> -Both the server and the client have SQLSERVERAgent logged in with the same
> username and password for pass-through authentication
> -Subscriber impersonates SqlServerAgent
> -Anonymous subscription
> The snapshot has been created successfully on the server and I am able to
> register the client on the server's Enterprise Manager (so they can see each
> other). The replication starts and runs for quite a while (most of the work
> is done). Eventually, it fails with the message
> //<servername>/<sharename>/<filname>.dri could not be propagated to the
> subscriber. With no further details. I don't think it is security related,
> because most of the work is already done.
> Any ideas what I'm missing?
Friday, March 9, 2012
Merge Replication Error: 'Failure to connect to SQL Server with provided connection
Hi!
Im trying to create a merge replication publication for a SQL Mobile
Application .
Everything works fine creating the publication and I'm able to do
the
http://xxx.xxx.xxx.xxx/aaaaaaa/sqlcesa30.dll, and it display's the
"sql server mobile server agent 3.0".
Im trying to create a merge replication publication for a SQL Mobile
Application .
Everything works fine creating the publication and I'm able to do
the
http://xxx.xxx.xxx.xxx/aaaaaaa/sqlcesa30.dll, and it display's the
"sql server mobile server agent 3.0".
But when I run the application on the PDA and its doing the
replication it appears the following error:
'Failure to connect to SQL Server with provided connection
information . SQL Server does not exist , access is denied because
the
IIS user is not a valid user on the SQL Server , or the password is
incorrect' .
any idea of which could be the reason...?
Thanks in advance!!!We found the solution: to put also the name of the Sql Server Instance
as the publisher: Sql_Server\Sql_Server_Instance
On Mar 5, 9:11 am, "CFTK" <crodriguezdepa...@.gmail.comwrote:
Quote:
Originally Posted by
Hi!
Im trying to create a merge replication publication for a SQL Mobile
Application .
Everything works fine creating the publication and I'm able to do
thehttp://xxx.xxx.xxx.xxx/aaaaaaa/sqlcesa30.dll, and it display's the
"sql server mobile server agent 3.0".
>
But when I run the application on the PDA and its doing the
replication it appears the following error:
'Failure to connect to SQL Server with provided connection
information . SQL Server does not exist , access is denied because
the
IIS user is not a valid user on the SQL Server , or the password is
incorrect' .
>
any idea of which could be the reason...?
>
Thanks in advance!!!
Subscribe to:
Posts (Atom)