I am getting the following error and can not figure out how to fix it. Please help.
SQL Server Enterprise Manager could not configure 'SERVER1' as the distributor for 'SERVER2'
Error 18482: Could not connect to server 'SERVER1' because 'SERVER2' is not defined as a remote server.
sp_helpserver on SERVER1
SERVER2 SERVER2 rpc out,use remote collation 2 NULL 0 0
repl_distributor SERVER1 rpc,dist,rpc out,system,use remote collation 1 NULL 0 0
ser SERVER1 rpc,rpc out,data access,use remote collation 0 NULL 0 0
sp_helpserver on SERVER2
SERVER2 SERVER2 rpc,rpc out,use remote collation 0 NULL 0 0
PE3 PE3 rpc out,use remote collation 2 NULL 0 0
SERVER1 SERVER1 rpc out,use remote collation 3 NULL 0 0
repl_distributor SERVER1 rpc,rpc out,system,use remote collation 1 NULL 0 0
on SERVER2
use master
select * from sysservers
0 1089 SERVER2 SQL Server SQLOLEDB SERVER2 NULL NULL 2003-11-19 01:44:51.920 NULL NULL NULL NULL 0 0 SERVER2 0 1 0 0 0 0 1 0 0 0 1 0 NULL
1 1601 repl_distributor SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-16 10:33:17.007 NULL NULL NULL NULL 0 0 SERVER1 0 1 0 0 0 0 1 0 0 1 1 0 NULL
3 1088 SERVER1 SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-15 14:07:05.963 NULL NULL NULL NULL 0 0 SERVER1 0 0 0 0 0 0 1 0 0 0 1 0 NULL
on SERVER1
use master
select * from sysservers
0 1249 SERVER1 SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-16 10:20:40.747 NULL NULL NULL NULL 0 0 SERVER1 1 1 0 0 0 0 1 1 0 0 1 0 NULL
1 1609 repl_distributor SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-16 10:30:58.750 NULL NULL NULL NULL 0 0 SERVER1 0 1 0 0 1 0 1 0 0 1 1 0 NULL
2 1088 SERVER2 SQL Server SQLOLEDB SERVER2 NULL NULL 2007-03-16 10:24:04.343 NULL NULL NULL NULL 0 0 SERVER2 0 0 0 0 0 0 1 0 0 0 1 0 NULL
Thanks,
Chris T.
Have you configured your publisher to publish to the distributor? Connect to the distributor in EM and configure it in the Tools - Replication - Configure Distributor, Publishers and Subscribers, do it in the Publishers tab. Ensure you enter an administrative link password.
Then on your publisher disable replication and then re-enable it to use the remote distributor. Enter the administrative link password in this dialog.
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
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message news:OLPnLFjaHHA.2436@.TK2MSFTNGP06.phx.gbl...
I am getting the following error and can not figure out how to fix it. Please help.
SQL Server Enterprise Manager could not configure 'SERVER1' as the distributor for 'SERVER2'
Error 18482: Could not connect to server 'SERVER1' because 'SERVER2' is not defined as a remote server.
sp_helpserver on SERVER1
SERVER2 SERVER2 rpc out,use remote collation 2 NULL 0 0
repl_distributor SERVER1 rpc,dist,rpc out,system,use remote collation 1 NULL 0 0
ser SERVER1 rpc,rpc out,data access,use remote collation 0 NULL 0 0
sp_helpserver on SERVER2
SERVER2 SERVER2 rpc,rpc out,use remote collation 0 NULL 0 0
PE3 PE3 rpc out,use remote collation 2 NULL 0 0
SERVER1 SERVER1 rpc out,use remote collation 3 NULL 0 0
repl_distributor SERVER1 rpc,rpc out,system,use remote collation 1 NULL 0 0
on SERVER2
use master
select * from sysservers
0 1089 SERVER2 SQL Server SQLOLEDB SERVER2 NULL NULL 2003-11-19 01:44:51.920 NULL NULL NULL NULL 0 0 SERVER2 0 1 0 0 0 0 1 0 0 0 1 0 NULL
1 1601 repl_distributor SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-16 10:33:17.007 NULL NULL NULL NULL 0 0 SERVER1 0 1 0 0 0 0 1 0 0 1 1 0 NULL
3 1088 SERVER1 SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-15 14:07:05.963 NULL NULL NULL NULL 0 0 SERVER1 0 0 0 0 0 0 1 0 0 0 1 0 NULL
on SERVER1
use master
select * from sysservers
0 1249 SERVER1 SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-16 10:20:40.747 NULL NULL NULL NULL 0 0 SERVER1 1 1 0 0 0 0 1 1 0 0 1 0 NULL
1 1609 repl_distributor SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-16 10:30:58.750 NULL NULL NULL NULL 0 0 SERVER1 0 1 0 0 1 0 1 0 0 1 1 0 NULL
2 1088 SERVER2 SQL Server SQLOLEDB SERVER2 NULL NULL 2007-03-16 10:24:04.343 NULL NULL NULL NULL 0 0 SERVER2 0 0 0 0 0 0 1 0 0 0 1 0 NULL
Thanks,
Chris T.
|||Good morning Hilary,
Yes I enabled SERVER1 as the distributor and set a link password. I then went to SERVER2 and tried to publish a database I set the link password through the wizard. I am trying to setup SERVER1 as the distributor for SERVER2.
I am still receiving the error I have both servers setup as remote servers on both systems.
SQL Server Enterprise Manager could not configure 'SERVER1' as the distributor for 'SERVER2'
Error 18482: Could not connect to server 'SERVER1' because 'SERVER2' is not defined as a remote server.
Thanks,
Chris T.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:uYGrpLjaHHA.4772@.TK2MSFTNGP05.phx.gbl...
Have you configured your publisher to publish to the distributor? Connect to the distributor in EM and configure it in the Tools - Replication - Configure Distributor, Publishers and Subscribers, do it in the Publishers tab. Ensure you enter an administrative link password.
Then on your publisher disable replication and then re-enable it to use the remote distributor. Enter the administrative link password in this dialog.
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
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message news:OLPnLFjaHHA.2436@.TK2MSFTNGP06.phx.gbl...
I am getting the following error and can not figure out how to fix it. Please help.
SQL Server Enterprise Manager could not configure 'SERVER1' as the distributor for 'SERVER2'
Error 18482: Could not connect to server 'SERVER1' because 'SERVER2' is not defined as a remote server.
sp_helpserver on SERVER1
SERVER2 SERVER2 rpc out,use remote collation 2 NULL 0 0
repl_distributor SERVER1 rpc,dist,rpc out,system,use remote collation 1 NULL 0 0
ser SERVER1 rpc,rpc out,data access,use remote collation 0 NULL 0 0
sp_helpserver on SERVER2
SERVER2 SERVER2 rpc,rpc out,use remote collation 0 NULL 0 0
PE3 PE3 rpc out,use remote collation 2 NULL 0 0
SERVER1 SERVER1 rpc out,use remote collation 3 NULL 0 0
repl_distributor SERVER1 rpc,rpc out,system,use remote collation 1 NULL 0 0
on SERVER2
use master
select * from sysservers
0 1089 SERVER2 SQL Server SQLOLEDB SERVER2 NULL NULL 2003-11-19 01:44:51.920 NULL NULL NULL NULL 0 0 SERVER2 0 1 0 0 0 0 1 0 0 0 1 0 NULL
1 1601 repl_distributor SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-16 10:33:17.007 NULL NULL NULL NULL 0 0 SERVER1 0 1 0 0 0 0 1 0 0 1 1 0 NULL
3 1088 SERVER1 SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-15 14:07:05.963 NULL NULL NULL NULL 0 0 SERVER1 0 0 0 0 0 0 1 0 0 0 1 0 NULL
on SERVER1
use master
select * from sysservers
0 1249 SERVER1 SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-16 10:20:40.747 NULL NULL NULL NULL 0 0 SERVER1 1 1 0 0 0 0 1 1 0 0 1 0 NULL
1 1609 repl_distributor SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-16 10:30:58.750 NULL NULL NULL NULL 0 0 SERVER1 0 1 0 0 1 0 1 0 0 1 1 0 NULL
2 1088 SERVER2 SQL Server SQLOLEDB SERVER2 NULL NULL 2007-03-16 10:24:04.343 NULL NULL NULL NULL 0 0 SERVER2 0 0 0 0 0 0 1 0 0 0 1 0 NULL
Thanks,
Chris T.
|||In this output:
sp_helpserver on SERVER1
this entry does not look correct:
ser SERVER1 rpc,rpc out,data access,use remote collation 0 NULL 0 0
It appears that SERVER1 has been defined as ser on this server. What does select * from sysservers look like on SERVER1?
What does select @.@.servername return on SERVER1?
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message news:%23FiEphjaHHA.2436@.TK2MSFTNGP06.phx.gbl...
Good morning Hilary,
Yes I enabled SERVER1 as the distributor and set a link password. I then went to SERVER2 and tried to publish a database I set the link password through the wizard. I am trying to setup SERVER1 as the distributor for SERVER2.
I am still receiving the error I have both servers setup as remote servers on both systems.
SQL Server Enterprise Manager could not configure 'SERVER1' as the distributor for 'SERVER2'
Error 18482: Could not connect to server 'SERVER1' because 'SERVER2' is not defined as a remote server.
Thanks,
Chris T.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:uYGrpLjaHHA.4772@.TK2MSFTNGP05.phx.gbl...
Have you configured your publisher to publish to the distributor? Connect to the distributor in EM and configure it in the Tools - Replication - Configure Distributor, Publishers and Subscribers, do it in the Publishers tab. Ensure you enter an administrative link password.
Then on your publisher disable replication and then re-enable it to use the remote distributor. Enter the administrative link password in this dialog.
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
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message news:OLPnLFjaHHA.2436@.TK2MSFTNGP06.phx.gbl...
I am getting the following error and can not figure out how to fix it. Please help.
SQL Server Enterprise Manager could not configure 'SERVER1' as the distributor for 'SERVER2'
Error 18482: Could not connect to server 'SERVER1' because 'SERVER2' is not defined as a remote server.
sp_helpserver on SERVER1
SERVER2 SERVER2 rpc out,use remote collation 2 NULL 0 0
repl_distributor SERVER1 rpc,dist,rpc out,system,use remote collation 1 NULL 0 0
ser SERVER1 rpc,rpc out,data access,use remote collation 0 NULL 0 0
sp_helpserver on SERVER2
SERVER2 SERVER2 rpc,rpc out,use remote collation 0 NULL 0 0
PE3 PE3 rpc out,use remote collation 2 NULL 0 0
SERVER1 SERVER1 rpc out,use remote collation 3 NULL 0 0
repl_distributor SERVER1 rpc,rpc out,system,use remote collation 1 NULL 0 0
on SERVER2
use master
select * from sysservers
0 1089 SERVER2 SQL Server SQLOLEDB SERVER2 NULL NULL 2003-11-19 01:44:51.920 NULL NULL NULL NULL 0 0 SERVER2 0 1 0 0 0 0 1 0 0 0 1 0 NULL
1 1601 repl_distributor SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-16 10:33:17.007 NULL NULL NULL NULL 0 0 SERVER1 0 1 0 0 0 0 1 0 0 1 1 0 NULL
3 1088 SERVER1 SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-15 14:07:05.963 NULL NULL NULL NULL 0 0 SERVER1 0 0 0 0 0 0 1 0 0 0 1 0 NULL
on SERVER1
use master
select * from sysservers
0 1249 SERVER1 SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-16 10:20:40.747 NULL NULL NULL NULL 0 0 SERVER1 1 1 0 0 0 0 1 1 0 0 1 0 NULL
1 1609 repl_distributor SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-16 10:30:58.750 NULL NULL NULL NULL 0 0 SERVER1 0 1 0 0 1 0 1 0 0 1 1 0 NULL
2 1088 SERVER2 SQL Server SQLOLEDB SERVER2 NULL NULL 2007-03-16 10:24:04.343 NULL NULL NULL NULL 0 0 SERVER2 0 0 0 0 0 0 1 0 0 0 1 0 NULL
Thanks,
Chris T.
|||Randy,
What is ser ?
Answer 1:
select @.@.servername returns SERVER1
Answer 2:
on SERVER1
use master
select * from sysservers
0 1249 SERVER1 SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-16 10:20:40.747 NULL NULL NULL NULL 0 0 SERVER1 1 1 0 0 0 0 1 1 0 0 1 0 NULL
1 1609 repl_distributor SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-16 10:30:58.750 NULL NULL NULL NULL 0 0 SERVER1 0 1 0 0 1 0 1 0 0 1 1 0 NULL
2 1088 SERVER2 SQL Server SQLOLEDB SERVER2 NULL NULL 2007-03-16 10:24:04.343 NULL NULL NULL NULL 0 0 SERVER2 0 0 0 0 0 0 1 0 0 0 1 0 NULL
Any ideas?
Thanks,
Chris T.
"Rand Boyd" <rboyd@.hotmail.com> wrote in message news:uZiZ1jlaHHA.4508@.TK2MSFTNGP03.phx.gbl...
In this output:
sp_helpserver on SERVER1
this entry does not look correct:
ser SERVER1 rpc,rpc out,data access,use remote collation 0 NULL 0 0
It appears that SERVER1 has been defined as ser on this server. What does select * from sysservers look like on SERVER1?
What does select @.@.servername return on SERVER1?
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message news:%23FiEphjaHHA.2436@.TK2MSFTNGP06.phx.gbl...
Good morning Hilary,
Yes I enabled SERVER1 as the distributor and set a link password. I then went to SERVER2 and tried to publish a database I set the link password through the wizard. I am trying to setup SERVER1 as the distributor for SERVER2.
I am still receiving the error I have both servers setup as remote servers on both systems.
SQL Server Enterprise Manager could not configure 'SERVER1' as the distributor for 'SERVER2'
Error 18482: Could not connect to server 'SERVER1' because 'SERVER2' is not defined as a remote server.
Thanks,
Chris T.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:uYGrpLjaHHA.4772@.TK2MSFTNGP05.phx.gbl...
Have you configured your publisher to publish to the distributor? Connect to the distributor in EM and configure it in the Tools - Replication - Configure Distributor, Publishers and Subscribers, do it in the Publishers tab. Ensure you enter an administrative link password.
Then on your publisher disable replication and then re-enable it to use the remote distributor. Enter the administrative link password in this dialog.
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
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message news:OLPnLFjaHHA.2436@.TK2MSFTNGP06.phx.gbl...
I am getting the following error and can not figure out how to fix it. Please help.
SQL Server Enterprise Manager could not configure 'SERVER1' as the distributor for 'SERVER2'
Error 18482: Could not connect to server 'SERVER1' because 'SERVER2' is not defined as a remote server.
sp_helpserver on SERVER1
SERVER2 SERVER2 rpc out,use remote collation 2 NULL 0 0
repl_distributor SERVER1 rpc,dist,rpc out,system,use remote collation 1 NULL 0 0
ser SERVER1 rpc,rpc out,data access,use remote collation 0 NULL 0 0
sp_helpserver on SERVER2
SERVER2 SERVER2 rpc,rpc out,use remote collation 0 NULL 0 0
PE3 PE3 rpc out,use remote collation 2 NULL 0 0
SERVER1 SERVER1 rpc out,use remote collation 3 NULL 0 0
repl_distributor SERVER1 rpc,rpc out,system,use remote collation 1 NULL 0 0
on SERVER2
use master
select * from sysservers
0 1089 SERVER2 SQL Server SQLOLEDB SERVER2 NULL NULL 2003-11-19 01:44:51.920 NULL NULL NULL NULL 0 0 SERVER2 0 1 0 0 0 0 1 0 0 0 1 0 NULL
1 1601 repl_distributor SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-16 10:33:17.007 NULL NULL NULL NULL 0 0 SERVER1 0 1 0 0 0 0 1 0 0 1 1 0 NULL
3 1088 SERVER1 SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-15 14:07:05.963 NULL NULL NULL NULL 0 0 SERVER1 0 0 0 0 0 0 1 0 0 0 1 0 NULL
on SERVER1
use master
select * from sysservers
0 1249 SERVER1 SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-16 10:20:40.747 NULL NULL NULL NULL 0 0 SERVER1 1 1 0 0 0 0 1 1 0 0 1 0 NULL
1 1609 repl_distributor SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-16 10:30:58.750 NULL NULL NULL NULL 0 0 SERVER1 0 1 0 0 1 0 1 0 0 1 1 0 NULL
2 1088 SERVER2 SQL Server SQLOLEDB SERVER2 NULL NULL 2007-03-16 10:24:04.343 NULL NULL NULL NULL 0 0 SERVER2 0 0 0 0 0 0 1 0 0 0 1 0 NULL
Thanks,
Chris T.
|||It was listed in the output. It maybe that the output got cut off. The first column in the output is the internal SQL Server name. But if @.servername is correct then it should be OK.
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message news:u6L4zulaHHA.5020@.TK2MSFTNGP05.phx.gbl...
Randy,
What is ser ?
Answer 1:
select @.@.servername returns SERVER1
Answer 2:
on SERVER1
use master
select * from sysservers
0 1249 SERVER1 SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-16 10:20:40.747 NULL NULL NULL NULL 0 0 SERVER1 1 1 0 0 0 0 1 1 0 0 1 0 NULL
1 1609 repl_distributor SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-16 10:30:58.750 NULL NULL NULL NULL 0 0 SERVER1 0 1 0 0 1 0 1 0 0 1 1 0 NULL
2 1088 SERVER2 SQL Server SQLOLEDB SERVER2 NULL NULL 2007-03-16 10:24:04.343 NULL NULL NULL NULL 0 0 SERVER2 0 0 0 0 0 0 1 0 0 0 1 0 NULL
Any ideas?
Thanks,
Chris T.
"Rand Boyd" <rboyd@.hotmail.com> wrote in message news:uZiZ1jlaHHA.4508@.TK2MSFTNGP03.phx.gbl...
In this output:
sp_helpserver on SERVER1
this entry does not look correct:
ser SERVER1 rpc,rpc out,data access,use remote collation 0 NULL 0 0
It appears that SERVER1 has been defined as ser on this server. What does select * from sysservers look like on SERVER1?
What does select @.@.servername return on SERVER1?
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message news:%23FiEphjaHHA.2436@.TK2MSFTNGP06.phx.gbl...
Good morning Hilary,
Yes I enabled SERVER1 as the distributor and set a link password. I then went to SERVER2 and tried to publish a database I set the link password through the wizard. I am trying to setup SERVER1 as the distributor for SERVER2.
I am still receiving the error I have both servers setup as remote servers on both systems.
SQL Server Enterprise Manager could not configure 'SERVER1' as the distributor for 'SERVER2'
Error 18482: Could not connect to server 'SERVER1' because 'SERVER2' is not defined as a remote server.
Thanks,
Chris T.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:uYGrpLjaHHA.4772@.TK2MSFTNGP05.phx.gbl...
Have you configured your publisher to publish to the distributor? Connect to the distributor in EM and configure it in the Tools - Replication - Configure Distributor, Publishers and Subscribers, do it in the Publishers tab. Ensure you enter an administrative link password.
Then on your publisher disable replication and then re-enable it to use the remote distributor. Enter the administrative link password in this dialog.
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
"Chris T." <tatroc@.donotspam.gmail.com> wrote in message news:OLPnLFjaHHA.2436@.TK2MSFTNGP06.phx.gbl...
I am getting the following error and can not figure out how to fix it. Please help.
SQL Server Enterprise Manager could not configure 'SERVER1' as the distributor for 'SERVER2'
Error 18482: Could not connect to server 'SERVER1' because 'SERVER2' is not defined as a remote server.
sp_helpserver on SERVER1
SERVER2 SERVER2 rpc out,use remote collation 2 NULL 0 0
repl_distributor SERVER1 rpc,dist,rpc out,system,use remote collation 1 NULL 0 0
ser SERVER1 rpc,rpc out,data access,use remote collation 0 NULL 0 0
sp_helpserver on SERVER2
SERVER2 SERVER2 rpc,rpc out,use remote collation 0 NULL 0 0
PE3 PE3 rpc out,use remote collation 2 NULL 0 0
SERVER1 SERVER1 rpc out,use remote collation 3 NULL 0 0
repl_distributor SERVER1 rpc,rpc out,system,use remote collation 1 NULL 0 0
on SERVER2
use master
select * from sysservers
0 1089 SERVER2 SQL Server SQLOLEDB SERVER2 NULL NULL 2003-11-19 01:44:51.920 NULL NULL NULL NULL 0 0 SERVER2 0 1 0 0 0 0 1 0 0 0 1 0 NULL
1 1601 repl_distributor SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-16 10:33:17.007 NULL NULL NULL NULL 0 0 SERVER1 0 1 0 0 0 0 1 0 0 1 1 0 NULL
3 1088 SERVER1 SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-15 14:07:05.963 NULL NULL NULL NULL 0 0 SERVER1 0 0 0 0 0 0 1 0 0 0 1 0 NULL
on SERVER1
use master
select * from sysservers
0 1249 SERVER1 SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-16 10:20:40.747 NULL NULL NULL NULL 0 0 SERVER1 1 1 0 0 0 0 1 1 0 0 1 0 NULL
1 1609 repl_distributor SQL Server SQLOLEDB SERVER1 NULL NULL 2007-03-16 10:30:58.750 NULL NULL NULL NULL 0 0 SERVER1 0 1 0 0 1 0 1 0 0 1 1 0 NULL
2 1088 SERVER2 SQL Server SQLOLEDB SERVER2 NULL NULL 2007-03-16 10:24:04.343 NULL NULL NULL NULL 0 0 SERVER2 0 0 0 0 0 0 1 0 0 0 1 0 NULL
Thanks,
Chris T.
Showing posts with label fix. Show all posts
Showing posts with label fix. Show all posts
Wednesday, March 28, 2012
Replication Error
Can anyone tell me how severe this error is and how to fix it? I have
received this error twice now within the month. The database seems fine and
replication continues at the next scheduled time without error.
Error: 14151, Severity: 18, State: 1
Replication-agentclassname: agent
dti000s1-Perception33-Perception33_pub-DTI000S6-6 failed. Article
'S_ReportTopic' failed data validation (rowcount and checksum)..
When this happens also get the following error as well for every table in
the database.
Error: 20574, Severity: 10, State: 1
Subscriber 'DTI000S6' subscription to article 'A_Result' in publication
'Perception33_pub' failed data validation..
This means that the following tables are out of sync - A_Result, and
S_ReportTopic.
Run a validation to do a row count and determine how badly out of sync you
are.
Are you running the continue of data consistency error profile? I would
disable this as it hides such consistency problems.
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
"msnews.microsoft.com" <jduncan@.tsi.jccbi.gov> wrote in message
news:eUtPrQqSFHA.2124@.TK2MSFTNGP14.phx.gbl...
> Can anyone tell me how severe this error is and how to fix it? I have
> received this error twice now within the month. The database seems fine
and
> replication continues at the next scheduled time without error.
> Error: 14151, Severity: 18, State: 1
> Replication-agentclassname: agent
> dti000s1-Perception33-Perception33_pub-DTI000S6-6 failed. Article
> 'S_ReportTopic' failed data validation (rowcount and checksum)..
> When this happens also get the following error as well for every table in
> the database.
> Error: 20574, Severity: 10, State: 1
> Subscriber 'DTI000S6' subscription to article 'A_Result' in publication
> 'Perception33_pub' failed data validation..
>
sql
received this error twice now within the month. The database seems fine and
replication continues at the next scheduled time without error.
Error: 14151, Severity: 18, State: 1
Replication-agentclassname: agent
dti000s1-Perception33-Perception33_pub-DTI000S6-6 failed. Article
'S_ReportTopic' failed data validation (rowcount and checksum)..
When this happens also get the following error as well for every table in
the database.
Error: 20574, Severity: 10, State: 1
Subscriber 'DTI000S6' subscription to article 'A_Result' in publication
'Perception33_pub' failed data validation..
This means that the following tables are out of sync - A_Result, and
S_ReportTopic.
Run a validation to do a row count and determine how badly out of sync you
are.
Are you running the continue of data consistency error profile? I would
disable this as it hides such consistency problems.
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
"msnews.microsoft.com" <jduncan@.tsi.jccbi.gov> wrote in message
news:eUtPrQqSFHA.2124@.TK2MSFTNGP14.phx.gbl...
> Can anyone tell me how severe this error is and how to fix it? I have
> received this error twice now within the month. The database seems fine
and
> replication continues at the next scheduled time without error.
> Error: 14151, Severity: 18, State: 1
> Replication-agentclassname: agent
> dti000s1-Perception33-Perception33_pub-DTI000S6-6 failed. Article
> 'S_ReportTopic' failed data validation (rowcount and checksum)..
> When this happens also get the following error as well for every table in
> the database.
> Error: 20574, Severity: 10, State: 1
> Subscriber 'DTI000S6' subscription to article 'A_Result' in publication
> 'Perception33_pub' failed data validation..
>
sql
Subscribe to:
Posts (Atom)