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 manager. Show all posts
Showing posts with label manager. Show all posts
Wednesday, March 28, 2012
Monday, March 12, 2012
Replication and Enterprise Manager
Hi
I have a very interesting situation with my replication. Replication works
great if I leave opened Enterprise Manager, but when I close it,
replication and SQL server does not work any more.
If I made a "mistake" and close EM, that the next morning SQL server does
not respond even if I reboot server. I must reinstall SQL service pack and
than it works. This was happened 5 time and now I am positivly shure that
this is the problem.
And yes ... this is SQL 2000 with SP3, Windows 2000 Server with Terminal
services installed.
Did anyone knows about this funny problem?
Thank you
what security context are your replication jobs running under? It sounds
like they are not running under a system administrator account.
To fix this right click on your agents and look at your agent properties.
Change the owner account to an account which is in the system administrator
role.
<dklancar@.nkbm.si> wrote in message
news:uxK3yvvFEHA.3188@.TK2MSFTNGP10.phx.gbl...
> Hi
> I have a very interesting situation with my replication. Replication works
> great if I leave opened Enterprise Manager, but when I close it,
> replication and SQL server does not work any more.
> If I made a "mistake" and close EM, that the next morning SQL server does
> not respond even if I reboot server. I must reinstall SQL service pack and
> than it works. This was happened 5 time and now I am positivly shure that
> this is the problem.
> And yes ... this is SQL 2000 with SP3, Windows 2000 Server with Terminal
> services installed.
> Did anyone knows about this funny problem?
> Thank you
|||Thank you for response, but I must tell you, that all agent are running as
user listed in the system admin role.
Thank you again.
|||If SQL Server won't start, is there anything listed in hte Windows Application Log or the SQL Server log that sheds any light?
Regards,
Paul Ibison
I have a very interesting situation with my replication. Replication works
great if I leave opened Enterprise Manager, but when I close it,
replication and SQL server does not work any more.
If I made a "mistake" and close EM, that the next morning SQL server does
not respond even if I reboot server. I must reinstall SQL service pack and
than it works. This was happened 5 time and now I am positivly shure that
this is the problem.
And yes ... this is SQL 2000 with SP3, Windows 2000 Server with Terminal
services installed.
Did anyone knows about this funny problem?
Thank you
what security context are your replication jobs running under? It sounds
like they are not running under a system administrator account.
To fix this right click on your agents and look at your agent properties.
Change the owner account to an account which is in the system administrator
role.
<dklancar@.nkbm.si> wrote in message
news:uxK3yvvFEHA.3188@.TK2MSFTNGP10.phx.gbl...
> Hi
> I have a very interesting situation with my replication. Replication works
> great if I leave opened Enterprise Manager, but when I close it,
> replication and SQL server does not work any more.
> If I made a "mistake" and close EM, that the next morning SQL server does
> not respond even if I reboot server. I must reinstall SQL service pack and
> than it works. This was happened 5 time and now I am positivly shure that
> this is the problem.
> And yes ... this is SQL 2000 with SP3, Windows 2000 Server with Terminal
> services installed.
> Did anyone knows about this funny problem?
> Thank you
|||Thank you for response, but I must tell you, that all agent are running as
user listed in the system admin role.
Thank you again.
|||If SQL Server won't start, is there anything listed in hte Windows Application Log or the SQL Server log that sheds any light?
Regards,
Paul Ibison
Wednesday, March 7, 2012
Replication - can subscriber objects be pre-existing?
My manager does not want to go through the process of moving 40 GB of data to the subscriber database over the network as would occur during the initialization phase of replication (exact method of replication has yet to be determined). The subscriber db is for Web Access and will be read-only. He wants to back up a db and use tapes to restore the db on the subscriber db server, and then activate replication. I have told him that you have to allow SQL Server to create the objects on the subscriber side and you have to allow SQL Server to control the data flow, that manually creating the objects on the subscriber side will not work. He says that I am incorrect.
Who is right? I haven't been able to find an answer from the Microsoft site and news groups.
Thanks,I hate to be the bearer of bad news for you, but your manager is correct in this instance.
Here's the link to get you started:
http://support.microsoft.com/kb/320499/en-us
It really does speed things up!
Tom
Who is right? I haven't been able to find an answer from the Microsoft site and news groups.
Thanks,I hate to be the bearer of bad news for you, but your manager is correct in this instance.
Here's the link to get you started:
http://support.microsoft.com/kb/320499/en-us
It really does speed things up!
Tom
Replication - Can not create Publication database
Hi,
I am trying to use Enterprise Manager Wizard to create a new
Publication database but I got the following message.
Error 2812: Could not find stored procedure
MyDB.dbo.sp_MSadd_logreader_agent
There seems that some replication stored procedures.
Any help?
Thanks in Advance"Ned" <nedabada@.yahoo.ca> wrote in message
news:3578739c.0501071331.3e845f66@.posting.google.c om...
> Hi,
> I am trying to use Enterprise Manager Wizard to create a new
> Publication database but I got the following message.
> Error 2812: Could not find stored procedure
> MyDB.dbo.sp_MSadd_logreader_agent
> There seems that some replication stored procedures.
> Any help?
> Thanks in Advance
You might get a better answer in microsoft.public.sqlserver.replication.
There are also lots of similar posts in the past, although I don't know if
any will apply to your situation exactly - Google "sql 2000 replication
error 2812" or something similar.
Simon
Subscribe to:
Posts (Atom)