Replication - SQLServer Agent uses System Account

When I attempt to set up replication on my local box, I receive the error -'SQLServer Agent uses the Systems Account, which causes replication betweem servers to fail'.
Why does this happen? And can I overcome this?
Thanks :)
BiancaStart SQLServerAgent service using a domain account. This account must have the appropriate rights on teh Publisher, Distributor and Subscriber computers (depending on the replication type)

Originally posted by Bianca_J
When I attempt to set up replication on my local box, I receive the error -'SQLServer Agent uses the Systems Account, which causes replication betweem servers to fail'.

Why does this happen? And can I overcome this?

Thanks :)

Bianca|||Thank you for your post :)

What is a Domain Account?

Is this set up in Windows 2000? And if I set up a Domain Account in my local Windows 2000 box - how do I have right over a remore server?

Thanks

Bianca

Replication - Publisher moving to a different server

My disclaimer: Ive never done this. These are just
theories.
I would have to imagine that as long as the new box has
the same name as the old, and the data files go to the
same location on the destination as they were on the
source, you should be good. You should be able just to
backup/ restore master/ msdb and the user db's should be
alive and in-tact. No matter what advice you get here, do
this in a test environment and get backups before you do
anything.

>--Original Message--
>Hi,
>I need to move my publisher to a different database as
the current server on
>which it is running is slow compared to my current
requirements.
>But I have 2 subscribers to this server. I have merge
replication in SQL
>Server 2k with sp3 on.
>Can someone advice me as to how to have a smooth
transition? I cannot just
>replace the harddisk as the new server has a much
powerful harddisk.
>Is it possible for me to just restore the backup of the
current publisher on
>the new server alongwith the master and msdb, and
replication starts? I will
>take care to name the new server as the old one and
remove the old one from
>the network.
>Can someone please help me with the same?
>Thank you in advance.
>Regards,
>Karthik
>
>.
>
Hi Chris,
Thank you for the advice. I will test it on on a different machine and let
you know as to how things went.
Thank you once again.
Regards,
Karthik
"ChrisR" wrote:

> My disclaimer: Ive never done this. These are just
> theories.
> I would have to imagine that as long as the new box has
> the same name as the old, and the data files go to the
> same location on the destination as they were on the
> source, you should be good. You should be able just to
> backup/ restore master/ msdb and the user db's should be
> alive and in-tact. No matter what advice you get here, do
> this in a test environment and get backups before you do
> anything.
>
>
> the current server on
> requirements.
> replication in SQL
> transition? I cannot just
> powerful harddisk.
> current publisher on
> replication starts? I will
> remove the old one from
>

replicating SQL 2000 to SQL 2005 database

Hi All,
I am having some memory issues and SSL issues with my SQL 2000 box. I had
SQL 2005 installed on this box, I uninstalled it when I had a crash of my
production server. I installed SQL 2000 on this box and moved everything
over. Everything including my replication was working fine then all of a
suddend we were not able to connect due to SSL issues, then we started
getting Out of memory issues. in my research I have found a hot fix for SQL
2000, and I installed it. the fix was for the memory issue in SQL 2000 but I
dont think it will completely cure my server. Everything I read also said
SQL2005 SP1 fixes these issues.
Now for the question if your all still with me
I have my 20 locations running SQL 2000 and I would like to upgrade my main
server to SQL 2005. Are there any known issues doing this? My publisher and
Subcscribers wil be coming from this SQL2005 machine.
TIA,
Joe
On Feb 12, 4:05 pm, jaylou <jay...@.discussions.microsoft.com> wrote:
> Hi All,
> I am having some memory issues and SSL issues with my SQL 2000 box. I had
> SQL 2005 installed on this box, I uninstalled it when I had a crash of my
> production server. I installed SQL 2000 on this box and moved everything
> over. Everything including my replication was working fine then all of a
> suddend we were not able to connect due to SSL issues, then we started
> getting Out of memory issues. in my research I have found a hot fix for SQL
> 2000, and I installed it. the fix was for the memory issue in SQL 2000 but I
> dont think it will completely cure my server. Everything I read also said
> SQL2005 SP1 fixes these issues.
> Now for the question if your all still with me
> I have my 20 locations running SQL 2000 and I would like to upgrade my main
> server to SQL 2005. Are there any known issues doing this? My publisher and
> Subcscribers wil be coming from this SQL2005 machine.
> TIA,
> Joe
I think I've seen this before... the ssl certificates are created by
domain controllers. In Active Directory's meta-data you have to delete
the oldest entry for the domain controller that was used to
authenticate your sql server account.
|||Thank you I will look into this.
"mrdba2001@.gmail.com" wrote:

> On Feb 12, 4:05 pm, jaylou <jay...@.discussions.microsoft.com> wrote:
> I think I've seen this before... the ssl certificates are created by
> domain controllers. In Active Directory's meta-data you have to delete
> the oldest entry for the domain controller that was used to
> authenticate your sql server account.
>