Queue Reader ODBC Error: Login failed for user "sa"

After implementing a password for the sa account, I'm getting the error:
ODBC Error: Login failed for user "sa"
I thought that there was stored procedure where I could set the password for
the Queue Reader Agent but I can't find it. Can anyone assist me here or
have any insight into this error?
Thanks in advance.
does this help?
http://support.microsoft.com/default...&Product=sql2k
"Salty Dog" <Salty Dog@.discussions.microsoft.com> wrote in message
news:7B1EB304-FC0E-4495-AB1E-44AC6666634E@.microsoft.com...
> After implementing a password for the sa account, I'm getting the error:
> ODBC Error: Login failed for user "sa"
> I thought that there was stored procedure where I could set the password
> for
> the Queue Reader Agent but I can't find it. Can anyone assist me here or
> have any insight into this error?
> Thanks in advance.
|||This looks like the information that I need. Thank you so much and I will
get back after I apply.
"Hilary Cotter" wrote:

> does this help?
> http://support.microsoft.com/default...&Product=sql2k
> "Salty Dog" <Salty Dog@.discussions.microsoft.com> wrote in message
> news:7B1EB304-FC0E-4495-AB1E-44AC6666634E@.microsoft.com...
>
>
|||Still the same error. I've recreated the Publisher and Subscriptions several
time and still not go. I have Subscription security using sa with password
instead of NT authentication. I'm really stumped or could you tell?
I'm configured for Immediate with Queued for failover. This was working
prior to adding a password. Any other help you can give me?
Another note: Prior to a complete startover of creating the Publisher and
all, I was getting the same error. The crazy thing was that the Red Error Xs
would disappear every once in a while and processing would resume like
everything was OK for just a few seconds. It would stay down longer than
logged on/up and running.
"Salty Dog" wrote:
[vbcol=seagreen]
> This looks like the information that I need. Thank you so much and I will
> get back after I apply.
> "Hilary Cotter" wrote:
|||More info...
The same symptom of it works a bit and then fails is happening again. I
think that this is just indicating that everything else is working except
communication between the subscriber and distributor/publisher so this is
probably not relevant.
The Queue Reader logon is still not passing the password. All other agents
are running fine. Still stumped and still really appreciating your help.
"Salty Dog" wrote:

> After implementing a password for the sa account, I'm getting the error:
> ODBC Error: Login failed for user "sa"
> I thought that there was stored procedure where I could set the password for
> the Queue Reader Agent but I can't find it. Can anyone assist me here or
> have any insight into this error?
> Thanks in advance.
|||authentication is done on a exe level. Can you right click on your queue
reader agent, select agent properties, run steps, and click on the run agent
command. What is your sa password there? It should be something encrypted.
Is there no way you can use trusted authentication to bypass this problem?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Salty Dog" <SaltyDog@.discussions.microsoft.com> wrote in message
news:805E9ECC-CD66-489C-8977-0B2DF77CD4C6@.microsoft.com...
> Still the same error. I've recreated the Publisher and Subscriptions
several
> time and still not go. I have Subscription security using sa with
password
> instead of NT authentication. I'm really stumped or could you tell?
> I'm configured for Immediate with Queued for failover. This was working
> prior to adding a password. Any other help you can give me?
> Another note: Prior to a complete startover of creating the Publisher and
> all, I was getting the same error. The crazy thing was that the Red Error
Xs[vbcol=seagreen]
> would disappear every once in a while and processing would resume like
> everything was OK for just a few seconds. It would stay down longer than
> logged on/up and running.
>
> "Salty Dog" wrote:
will[vbcol=seagreen]
http://support.microsoft.com/default...&Product=sql2k[vbcol=seagreen]
error:[vbcol=seagreen]
password[vbcol=seagreen]
here or[vbcol=seagreen]