Re: Subscriber Security Settings for Distributor and Publisher log
From: Hilary Cotter (hilaryk_at_att.net)
Date: 06/24/04
- Next message: Hilary Cotter: "Re: Replication between sqlserver2000 and postgresql"
- Previous message: Mingqing Cheng [MSFT]: "Re: Pre-Publishing Steps"
- In reply to: Warren Patterson: "Re: Subscriber Security Settings for Distributor and Publisher log"
- Next in thread: Mingqing Cheng [MSFT]: "RE: Subscriber Security Settings for Distributor and Publisher login become corrupted"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 23 Jun 2004 21:15:04 -0400
not that I know of.
-- Hilary Cotter Looking for a book on SQL Server replication? http://www.nwsu.com/0974973602.html "Warren Patterson" <des@newsgroups.nospam> wrote in message news:u8Yi%23dPWEHA.2928@tk2msftngp13.phx.gbl... > Hi Hilary, > > Thanks for your reply. > > I cant check the agent properties from here, as the subscriber is in another > country and I dont have access to that machine :-( > > Is there another way? > > I have access to the puhblisher only. > > > > > > > "Hilary Cotter" <hilaryk@att.net> wrote in message > news:726392A5-CA37-48B5-83FF-E0D938F68AF5@microsoft.com... > > Here's something weird I have seen. Some people will jump all over me for > even suggesting it, but I have wittnessed it happening. > > > > Replication authentication is done at the component level, ie distrib.exe, > logread.exe, replmerg.exe. > > > > It is done through SQL Server authentication or NT Authentication. When > using Authentication it authenticates using the account that your SQL Server > agent account runs under. > > > > Now, here is where it gets tricky. If you are logged on to EM using an > account which is a sysadmin account on a pull subscriber, and you make a > change to the replication agent or publication/susbcription, or stop and > start the agent, it seems that the agent will then run under your account if > you are using nt authentication, or whatever account is the "owner". So if > you check your agent properties, check to see that the owner account is the > sa account or administrator account. > > > > -- > > Looking for a SQL Server replication book? > > http://www.nwsu.com/0974973602.html > > > > > > > > > > "Warren Patterson" wrote: > > > > > Hi Hilary, > > > > > > Thanks for your reply. > > > > > > I have setup the publisher/subscriber/distributor correctly....i hope. > > > Everything was working great then this problem. Its not the first time I > > > have encountered this problem. It happened on a few occasions in our > test > > > environment, but we never thought it too much of a concern at that > stage. > > > > > > I am using Sql Server Authentication for both publisher and Distributor > > > login for all subscribers. They are pull subscriptions and the > Replication > > > type is Merge Replication. > > > > > > "If" it happens again I will try and get the log files. The problem is > the > > > remoteness of the subscribers. We cant access the machine, the > subscriber > > > initiates all connections from its side. I was just lucky somebody was > at > > > the site so I could talk them through retyping in the passwords. > > > > > > Thanks again > > > Warren Patterson > > > > > > > > > > > > "Hilary Cotter" <hilaryk@att.net> wrote in message > > > news:84358A72-7064-476E-BE34-0D042E41D69B@microsoft.com... > > > > You have to be a little careful here. > > > > > > > > First of all - once you have a correctly configured > > > publisher/subscriber/distributor and you have built and distributed your > > > publication, you should not run into this problem. > > > > > > > > The password (if you are using SQL Server Authentication) is saved in > > > encrypted format, but as unicode. The string is saved in the msdb > database, > > > and for only this to be corrupted strains credulity. If you are using > NT > > > authentication your domain controller is handling the authentication. > > > > > > > > You are possibly running into another problem, which may or may not > show > > > up as the "login failure" error message. > > > > > > > > Next time you get this error, please post the exact message here, or > post > > > it here now if you still have it along with the error number. This will > be > > > helpful with further diagnosis. > > > > > > > > > > > > -- > > > > Looking for a SQL Server replication book? > > > > http://www.nwsu.com/0974973602.html > > > > > > > > > > > > > > > > > > > > "Warren Patterson" wrote: > > > > > > > > > Hi guys, > > > > > > > > > > I have setup merge replication with subscribers all synching up > fine, > > > but > > > > > all of a sudden one of teh subscribers wouldnt connect to the > > > distributor, > > > > > it would say failed login. > > > > > > > > > > I have since discovered how to make it work again, but the solution > > > concerns > > > > > me. > > > > > > > > > > Seems that on the Subscriber if you go to its security settings > > > (Publisher > > > > > and > > > > > Distributor login) and retype in the passwords and save it, it > connects > > > to > > > > > the publisher/distributor perfectly, seems the passwords become > corrupt > > > or > > > > > something. > > > > > > > > > > I suspect this is a bug, do you know of it or what causes it? This > isnt > > > the > > > > > first time this has happened. > > > > > > > > > > Any help in this regard is greatly appreciated. > > > > > > > > > > Kind Regards > > > > > Warren Patterson > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
- Next message: Hilary Cotter: "Re: Replication between sqlserver2000 and postgresql"
- Previous message: Mingqing Cheng [MSFT]: "Re: Pre-Publishing Steps"
- In reply to: Warren Patterson: "Re: Subscriber Security Settings for Distributor and Publisher log"
- Next in thread: Mingqing Cheng [MSFT]: "RE: Subscriber Security Settings for Distributor and Publisher login become corrupted"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
