"John Baima" <john@nospam.com> wrote in message
news:d343t0ta0k4p5833k2smt08q59or5cs543@4ax.com...
> I'm trying to setup a test transact replication using the Create
> Publication wizard. It first selects a distributor. When I indicate
> that it should make the publisher its own distributor, I get the
> message,
>
> SQL Server Agent on xxx.xxx.xxx.xxx currently uses the system account,
> which causes replication between servers to fail. In the following
> dialog box, specify another account for the Service startup account.
>
> That would be okay, except when I get the next dialog, the options
> under "Service startup account" are disabled. Do I need another
> account before I start the wizard? What properties should that account
> have? Do I need to connect with EM with a different account before I
> start the wizard? Thanks for any help
>
> -John

"John Baima" <john@nospam.com> wrote in message
news:dvd3t09bv78jhpjo0gucrurl7ottbnjb3l@4ax.com...
> BTW, is your book available at Amazon.com? I need it like yesterday.
> Thanks.
>
> -John
>
> "Hilary Cotter" <hilary.cotter@gmail.com> wrote:
>
> >Possibly.
> >
> >I would try to fix it through the control panel applet, with the caveat
that
> >this might break SQL FTS populations.
> >
> >Click Start, point to Setting, click Control Panel, click Administrative
> >tools, and click Services. Locate the MSSQLServer entry and change this
to
> >an account in the local admin group. Make the same change to the SQL
Server
> >Agent account. Then try to create your publication again.
>

"John Baima" <john@nospam.com> wrote in message
news:pkd3t0th9t6dpssg182bit039j78719ljn@4ax.com...
> Okay. Do the MSSQLServer and SQLServerAgent services need local
> accounts and be part of the local admin group? Or can they be network
> logins? Currently we use a network login for those accounts.
>
> While I'm only making a test replication, this is a production server.
>
>
> "Hilary Cotter" <hilary.cotter@gmail.com> wrote:
>
> >Possibly.
> >
> >I would try to fix it through the control panel applet, with the caveat
that
> >this might break SQL FTS populations.
> >
> >Click Start, point to Setting, click Control Panel, click Administrative
> >tools, and click Services. Locate the MSSQLServer entry and change this
to
> >an account in the local admin group. Make the same change to the SQL
Server
> >Agent account. Then try to create your publication again.
>

"Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
news:uqq9GDS7EHA.2572@tk2msftngp13.phx.gbl...
> No yet:(
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "John Baima" <john@nospam.com> wrote in message
> news:dvd3t09bv78jhpjo0gucrurl7ottbnjb3l@4ax.com...
> > BTW, is your book available at Amazon.com? I need it like yesterday.
> > Thanks.
> >
> > -John
> >
> > "Hilary Cotter" <hilary.cotter@gmail.com> wrote:
> >
> > >Possibly.
> > >
> > >I would try to fix it through the control panel applet, with the caveat
> that
> > >this might break SQL FTS populations.
> > >
> > >Click Start, point to Setting, click Control Panel, click
Administrative
> > >tools, and click Services. Locate the MSSQLServer entry and change this
> to
> > >an account in the local admin group. Make the same change to the SQL
> Server
> > >Agent account. Then try to create your publication again.
> >
>
>

"Hilary Cotter" <hilary.cotter@gmail.com> wrote:

>Possibly.
>
>I would try to fix it through the control panel applet, with the caveat that
>this might break SQL FTS populations.
>
>Click Start, point to Setting, click Control Panel, click Administrative
>tools, and click Services. Locate the MSSQLServer entry and change this to
>an account in the local admin group. Make the same change to the SQL Server
>Agent account. Then try to create your publication again.