I am trying to replicate over a dial-up connection a database between
a server running Sql Server 2000 on Windows 2000 server and two SQL
server 2000 personal edition on Windows XP pro.
For one site, the replication worked correclty. For the other one, the
replication process starts, but when trying to connect to the
subscriber (i.e Windows XP pro), after waiting 5 minutes the following
error message is displayed:
Merge Process could not retreive generation information at the
subscriber.
General Network error source <windows xp database> (data source) error
number 11.
Replication tries again automatically and same error is displayed.
All suggestions are welcome.
Best Regards
Patrick
Use the slow link profile for this problem subscribe. Right click on the
agent (expand replication monitor, replication agents, merge agents, locate
your agent), select agent profiles, select the slow link profile, accept
defaults and restart it.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Patrick" <pmenage@.intnet.mu> wrote in message
news:4b9f6ca1.0411250208.6f22429a@.posting.google.c om...
>I am trying to replicate over a dial-up connection a database between
> a server running Sql Server 2000 on Windows 2000 server and two SQL
> server 2000 personal edition on Windows XP pro.
> For one site, the replication worked correclty. For the other one, the
> replication process starts, but when trying to connect to the
> subscriber (i.e Windows XP pro), after waiting 5 minutes the following
> error message is displayed:
> Merge Process could not retreive generation information at the
> subscriber.
> General Network error source <windows xp database> (data source) error
> number 11.
> Replication tries again automatically and same error is displayed.
> All suggestions are welcome.
> Best Regards
> Patrick
|||I just found the solution. When I entered my user name in the dial-up
connection box I entered it with the remote machine name eg: PC1\User1.
But when I checked the user in the "add user to operating system" module
in Windows XP, the machine name was dropped, only the user name
appeared. So when connecting, I entered only the user name, and
everything worked fine.
Thank you for your support.
Best Regards
Patrick
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Showing posts with label subscriber. Show all posts
Showing posts with label subscriber. Show all posts
Thursday, March 29, 2012
Tuesday, March 27, 2012
General network error
I used push merge replication over internet.
I got the this error log at end of applying both schema and data to the subscriber.
General network error. Check your network documentation.
(Source: internet_ip_address\MSDE1 (Data source); Error number: 11)
The data were repliacted to subscriber.
Then, I deleted the subscription and re-created again, but selected
"the Subscriber already has the schema and data".
I got the following error:
The remote server is not defined as a subscription server
(Source: internet_ip_address\MSDE1 (Data source); Error number: 14010)
on your publisher go to Tools-Replication-Configure Publishers,
Distributors, and Subscribers, click on the Subscriber tab, and locate your
subscriber and click on the three dots (the browse button) to the right of
the subscriber and ensure that you are using the impersonate the SQL Server
account on the publisher.
Then restart your distribution agent.
"Ming Cheng" <mccheng@.msn.com> wrote in message
news:B0FA6FEE-D918-49D3-AA1F-1EDBBB36AF8F@.microsoft.com...
> I used push merge replication over internet.
> I got the this error log at end of applying both schema and data to the
subscriber.
> General network error. Check your network documentation.
> (Source: internet_ip_address\MSDE1 (Data source); Error number: 11)
> The data were repliacted to subscriber.
> Then, I deleted the subscription and re-created again, but selected
> "the Subscriber already has the schema and data".
> I got the following error:
> The remote server is not defined as a subscription server
> (Source: internet_ip_address\MSDE1 (Data source); Error number: 14010)
>
sql
I got the this error log at end of applying both schema and data to the subscriber.
General network error. Check your network documentation.
(Source: internet_ip_address\MSDE1 (Data source); Error number: 11)
The data were repliacted to subscriber.
Then, I deleted the subscription and re-created again, but selected
"the Subscriber already has the schema and data".
I got the following error:
The remote server is not defined as a subscription server
(Source: internet_ip_address\MSDE1 (Data source); Error number: 14010)
on your publisher go to Tools-Replication-Configure Publishers,
Distributors, and Subscribers, click on the Subscriber tab, and locate your
subscriber and click on the three dots (the browse button) to the right of
the subscriber and ensure that you are using the impersonate the SQL Server
account on the publisher.
Then restart your distribution agent.
"Ming Cheng" <mccheng@.msn.com> wrote in message
news:B0FA6FEE-D918-49D3-AA1F-1EDBBB36AF8F@.microsoft.com...
> I used push merge replication over internet.
> I got the this error log at end of applying both schema and data to the
subscriber.
> General network error. Check your network documentation.
> (Source: internet_ip_address\MSDE1 (Data source); Error number: 11)
> The data were repliacted to subscriber.
> Then, I deleted the subscription and re-created again, but selected
> "the Subscriber already has the schema and data".
> I got the following error:
> The remote server is not defined as a subscription server
> (Source: internet_ip_address\MSDE1 (Data source); Error number: 14010)
>
sql
Friday, March 9, 2012
Function sequence error - Merge Replication
We are replicating from 7 publishers to 1 subscriber all running MS SQL
Server 2000 SP3 using Merge Replication.
We are in the process of upgrading our application and due to that we had to
make
some changes to the database schema like add some columns, create a few new
tables, and triggers. We did all this through a script using stored
procedures on 2 of the publisher databases and then ran the snapshot agent.
That's when we started seeing the error.
Error Message: The process could not bulk copy out of table '[dbo].[Invoice]'.
Error details: Function sequence error
(Source: ODBC SQL Server Driver (ODBC); Error number: 0)
------
Does anyone know how to resolve this?
Do we need to do anything on the subscriber database because of the schema
change done on the publisher database ?
Thanks in advance,
I wish I could tell you how to solve this one. The good news is that it
seems to be transient.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Vikram" <Vikram@.discussions.microsoft.com> wrote in message
news:E1A11B74-CE85-4C1B-87F5-248919A882CE@.microsoft.com...
> We are replicating from 7 publishers to 1 subscriber all running MS SQL
> Server 2000 SP3 using Merge Replication.
> We are in the process of upgrading our application and due to that we had
to
> make
> some changes to the database schema like add some columns, create a few
new
> tables, and triggers. We did all this through a script using stored
> procedures on 2 of the publisher databases and then ran the snapshot
agent.
> That's when we started seeing the error.
> Error Message: The process could not bulk copy out of table
'[dbo].[Invoice]'.
> Error details: Function sequence error
> (Source: ODBC SQL Server Driver (ODBC); Error number: 0)
> ----
--
> Does anyone know how to resolve this?
> Do we need to do anything on the subscriber database because of the schema
> change done on the publisher database ?
>
> Thanks in advance,
>
Server 2000 SP3 using Merge Replication.
We are in the process of upgrading our application and due to that we had to
make
some changes to the database schema like add some columns, create a few new
tables, and triggers. We did all this through a script using stored
procedures on 2 of the publisher databases and then ran the snapshot agent.
That's when we started seeing the error.
Error Message: The process could not bulk copy out of table '[dbo].[Invoice]'.
Error details: Function sequence error
(Source: ODBC SQL Server Driver (ODBC); Error number: 0)
------
Does anyone know how to resolve this?
Do we need to do anything on the subscriber database because of the schema
change done on the publisher database ?
Thanks in advance,
I wish I could tell you how to solve this one. The good news is that it
seems to be transient.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Vikram" <Vikram@.discussions.microsoft.com> wrote in message
news:E1A11B74-CE85-4C1B-87F5-248919A882CE@.microsoft.com...
> We are replicating from 7 publishers to 1 subscriber all running MS SQL
> Server 2000 SP3 using Merge Replication.
> We are in the process of upgrading our application and due to that we had
to
> make
> some changes to the database schema like add some columns, create a few
new
> tables, and triggers. We did all this through a script using stored
> procedures on 2 of the publisher databases and then ran the snapshot
agent.
> That's when we started seeing the error.
> Error Message: The process could not bulk copy out of table
'[dbo].[Invoice]'.
> Error details: Function sequence error
> (Source: ODBC SQL Server Driver (ODBC); Error number: 0)
> ----
--
> Does anyone know how to resolve this?
> Do we need to do anything on the subscriber database because of the schema
> change done on the publisher database ?
>
> Thanks in advance,
>
Subscribe to:
Posts (Atom)