Sunday, 12 February 2012

Configuring Distributor

I keep getting the error message:
An error occurred during decryption.
There is no remote user 'distributor_admin' mapped to local user '(null)'
from the remote server 'repl_distributor'.
Changed database context to 'master'. (Microsoft SQL Server, Error: 15466)
I have tried a local server account (as BOL describes), I have tried using
my own SQL account (that has sa priviliges of course), I have even tried the
domain account that runs SQL Agent service (despite the note right there on
the screen that recommends not to!). I get this error at the end of all the
steps whether I try to create a new publication or if I try to configure the
publisher.
ANY help would be appreciated!!
Is this SQL 2005? And is it part of an upgrade? SQL Server 2000 used a
remote server called repl_distributor which uses the distributor admin
account. In SQL Server 2005 this has been replaced by a linked server. In
some cases I have seen the upgrade of a replication topology with a remote
distributor does not work successfully.
In my cases I had to add the linked server and password manually, IIRC.
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
"mrdj" <mrdj@.discussions.microsoft.com> wrote in message
news:A3B17D13-3D6F-4B84-970A-F8FDDCB16144@.microsoft.com...
>I keep getting the error message:
> An error occurred during decryption.
> There is no remote user 'distributor_admin' mapped to local user '(null)'
> from the remote server 'repl_distributor'.
> Changed database context to 'master'. (Microsoft SQL Server, Error: 15466)
> I have tried a local server account (as BOL describes), I have tried using
> my own SQL account (that has sa priviliges of course), I have even tried
> the
> domain account that runs SQL Agent service (despite the note right there
> on
> the screen that recommends not to!). I get this error at the end of all
> the
> steps whether I try to create a new publication or if I try to configure
> the
> publisher.
> ANY help would be appreciated!!
|||It is a fresh install. Add a linked serer to what? could you send me the
details of adding the linked sever I am completely lost.
"Hilary Cotter" wrote:

> Is this SQL 2005? And is it part of an upgrade? SQL Server 2000 used a
> remote server called repl_distributor which uses the distributor admin
> account. In SQL Server 2005 this has been replaced by a linked server. In
> some cases I have seen the upgrade of a replication topology with a remote
> distributor does not work successfully.
> In my cases I had to add the linked server and password manually, IIRC.
> --
> 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
>
> "mrdj" <mrdj@.discussions.microsoft.com> wrote in message
> news:A3B17D13-3D6F-4B84-970A-F8FDDCB16144@.microsoft.com...
>
>
|||Check to ensure there is a linked server called repl_distributor and it uses
the security context of distributor_admin
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
"mrdj" <mrdj@.discussions.microsoft.com> wrote in message
news:D77607EC-1CA2-4D9E-8822-F4DCAA1D4976@.microsoft.com...[vbcol=seagreen]
> It is a fresh install. Add a linked serer to what? could you send me the
> details of adding the linked sever I am completely lost.
> "Hilary Cotter" wrote:
|||I tried adding the linked server and it STILL failed! But I'm making progess
because now I know exactly where the error is occuring, when adding the
linked server:
Msg 15466, Level 16, State 2, Procedure sp_addlinkedsrvlogin, Line 91
An error occurred during decryption.
Funny, I tried looking up this error number when all this first happened
(notice below, the text is a little different from my original error) and I
got nothing in my serarch results from Microsoft. I was able to get this to
work on another server, so at least I know it is some internal setting
specific to this server...Any ideas?
REALLY appreciate your help so far!!
"Hilary Cotter" wrote:

> Check to ensure there is a linked server called repl_distributor and it uses
> the security context of distributor_admin
> --
> 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
>
> "mrdj" <mrdj@.discussions.microsoft.com> wrote in message
> news:D77607EC-1CA2-4D9E-8822-F4DCAA1D4976@.microsoft.com...
>
>
|||Hilary,
Should this linked server be created on the distributor, or the subscriber,
or both? I am seeing a similar error when trying to setup replication in my
production environment, although it worked fine in test (currently being
rebuilt, so I have no comparison to use atm). I am thinking this might be a
part of my problem.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uoTqv58THHA.3592@.TK2MSFTNGP03.phx.gbl...
> Check to ensure there is a linked server called repl_distributor and it
uses[vbcol=seagreen]
> the security context of distributor_admin
> --
> 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
>
> "mrdj" <mrdj@.discussions.microsoft.com> wrote in message
> news:D77607EC-1CA2-4D9E-8822-F4DCAA1D4976@.microsoft.com...
the[vbcol=seagreen]
In
>

No comments:

Post a Comment