RE: CTP3 Failure - Creating a Remote Distributor (error during dec

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Gryphyn,

It appears that simply changing the SQL Server service account from a domain
account to the localsystem account even before the distributor is set up had
caused the problem that you saw. While the CTP readme states that changing
service account is not supported, you can workaround the issue without
re-installing SQL Server using the Local System account (which seems
impossible to do in your case) by executing the following command:

alter service master key with old_account =
'yourdomainaccountforsettingupctp', old_password = 'yourdomainaccountpassowrd'

I have yet to find out exactly why the scenario was "working" for you in the
Feb CTP, but I suspect that this has something to do with tightening of the
encryption key management system.

HTH

-Raymond
"Gryphyn" wrote:

> Raymond,
>
> In response to your queries.
>
> 1) Was the remote distributor service account changed in any way?
> No.
> 2) Are the remote distributor and the publisher machines in the same domain?
> Yes.
> 3) Did you attach the old master\distribution database files to the latest
> CTP server when you upgraded?
> No.
> 4) Are the remote distributor and the publisher running the same version of
> the CTP?
> Yes/No.
> 5) Are the distributor and publisher SQL Server Service running under domain
> accounts or local system accounts?
> Local System
> 6) Have you ever been told to turn on certain server trace flags?
> No.
> 7) Are you using any virtualization products such as VirtualPC by any chance?
> No.
>
> Now to explain some of them...
>
> 1) All activity/actions are done from LocalHost to RemoteHost. Everything on
> RemoteHost has been done via the command prompt utilities (except service
> security - see later) including the installation. [after upgrading to XP-SP2-
> new minimum spec]
>
> 2) Both Local & Remote Hosts are on the same domain and both are using
> (connected to) a domain/machine administator account (mine)
>
> 3a) All CTP2 instances, services, datafiles and programfiles were removed
> from RemoteHost BEFORE attempting the Remote installation/setup. (this
> included the removal of .NET & such - as stated in the CTP2 uninstall
> procedures)
> *I didn't do a sweep of the Registry to clean up any orphaned entries.
>
> 3b) I only have instances created via a Remote install [Note: they are ALL
> named instances]
>
> 4a) LocalHost has SS2000 & SS2005CTP3, although only the CTP3 utilities are
> used for the Remote installation. (the new features Setup.exe & sqlcmd.exe)
> The Remote host only has the remotely installed features
> ADDLOCAL=SQL_Engine,Client_Components,SQL_Tools90,SQL_Replication,ReplMonitor,SQL_AdventureWorksSamples
>
> 4b) Without the Distributor, creating a Publisher is meaningless (as you
> need to assign a distributor)
>
> 5) Although a new setup.exe now REQUIRES security entries for AGTACCOUNT,
> SQLACCOUNT, SQLBROWSERACCOUNT, these were all done using my account (see 2
> above). After the remote instance installation was complete I changed these
> all to LocalSystem (rather than my account)
>
> 6) This is the sort of help I was looking for, but I gather thats an
> official support call. I havent, as yet, gone to those lengths.
>
> 7) No third party vendors to consider, configuration is all MS.
>
> I've even looked at all the Surface Area stuff and allowed everything, still
> to no avail.
>
> It was all working with CTP2, that's the strange part.
>
> Thanks
> Gryphyn
>
> PS. I'll cross post the the newsgroup below - finding the right newsgroup is
> a quagmire almost-the-right-one links.
>
> "Raymond Mak [MSFT]" wrote:
>
> > One of the most well-known reasons behind the error that you saw has to do
> > with changes in the SQL Server service account after replication has been set
> > up (account name and\or password). But given that multiple people have
> > reported similar issues with the latest CTP (April), I tend to suspect that
> > there is something more behind this. Unfortunately, we have so far been
> > unable to duplicate the error in our lab and so it would be great if you can
> > tell us whether any of the following apply to your scenario:
> >
> > 1) Was the remote distributor sevrvice account changed in any way?
> > 2) Are the remote distributor and the publisher machines in the same domain?
> > 3) Did you attach the old master\distribution database files to the latest
> > CTP server when you upgraded?
> > 4) Are the remote distributor and the publisher running the same version of
> > the CTP?
> > 5) Are the distributor and publisher SQL Server Service running under domain
> > accounts or local system accounts?
> > 6) Have you ever been told to turn on certain server trace flags?
> > 7) Are you using any virtualization products such as VirtualPC by any chance?
> >
> > If you have done 3) at the distributor during upgrade, it would be
> > interesting to see if dropping and re-establishing the remote publisher at
> > the distributor resolves the issue (reseting the password etc.). BTW, we do
> > have newsgroups set up for everything related to SQL2005 @
> > http://communities.microsoft.com/newsgroups/default.asp?icp=sqlserver2005&slcid=us
> > (it is fully accessible to me but may require Passport\beta account sign-up
> > etc. from you) which are preferred for reporting problems in SQL2005.
> >
> > HTH
> >
> > -Raymond
> >
> >
> > "Gryphyn" wrote:
> >
> > > TITLE: Microsoft.SqlServer.ConnectionInfo
> > > ----------------------------------------
> > > SQL Server could not configure 'RemoteHost\REPL_DIST' as a Distributor.
> > > ----------------------------------------
> > > ADDITIONAL INFORMATION:
> > > An exception occurred while executing a Transact-SQL statement or batch.
> > > (Microsoft.SqlServer.ConnectionInfo)
> > > ----------------------------------------
> > > 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)
> > > For help, click:
> > > http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=09.00.1116&EvtSrc=MSSQLServer&EvtID=15466&LinkId=20476
> > >
> > > in CTP2 the following worked fine.
> > > --OnRemoteHost
> > > use master
> > > exec sp_adddistributor
> > > @distributor = N'RemoteHost\REPL_DIST',
> > > @password = N'PassWord1'
> > > GO
> > >
> > > I get the same error when using the Wizard to create a remote distributor.
> > > I'm and Admin on both LocalHost & RemoteHost
> > > The RemoteHost XP-SP2 has firewall disabled.
> > >
> > > Just looking for some clues (The help link isn't)
> > >
> > > Cheers
> > > Gryphyn
> > >
.

Relevant Pages

  • RE: CTP3 Failure - Creating a Remote Distributor (error during dec
    ... After the remote instance installation was complete I changed these ... > It appears that simply changing the SQL Server service account from a domain ... > account to the localsystem account even before the distributor is set up had ...
    (microsoft.public.sqlserver.replication)
  • Re: How to remote access Windows XP Pro computer?
    ... you happen to use Norton Internet Security please read the following link. ... link for the remote person to access their system. ... "Is LogMeIn secure and what is SSL? ... separate passwords to access both your LogMeIn account and your Target ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: RWW and Remote desktop stopped working on all clients
    ... After diggin through ALL the group policies, I found Remote ... Desktop DISABLED under the Account Lockout policy - I don't think I've even ... adminsitrator or another account with Domain Admin role; also the server ...
    (microsoft.public.windows.server.sbs)
  • Re: DomainLocalServer$ is not a valid user
    ... I have traced by SQL-profiler on remote computer. ... it's always traced the user account. ... Its Security is ... to use the current user credential to logon to the remote server. ...
    (microsoft.public.sqlserver.security)
  • Network share as a Publishing Point source
    ... Give the common user appropriate permissions on folders, ... publishing points, ... >original account would keep me from mapping a publishing ... >>>I tried setting up a remote share for WM9 Services, ...
    (microsoft.public.windowsmedia.server)