Merge replication turning me blue in the face

I have the most perplexing issue with merge replication. This is a
configuration that has worked well on several other systems, both XP Pro and
Windows Server. This installation is on an XP Pro box that is set up as
close to identical to the development machine as possible.
I'm getting the error, 80045003 "Initialializing SQL Server Reconciler has
filed."
When I look under the Misc. Agents, I have the message, "The job failed.
Unable to determine if the owner of job replication agents checkup has
server access (reason: could not obtain information about Windows NT
group\user [doman\username] SQL State 42000 error 8198).
I've added the domain user as dbo and given access to the master database.
I've added the distributor_admin as user to the database that I'm
replicating.
Any advice on where to look next would be appreciated.
Earl,
try changing all replication job owners to sa and see if that helps.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

merge replication licensing

This will be the setup:
1 server with:
windows server 2003 standard
sql server 2005 standard
30+ clients with:
windows xp pro
sql server express
I will set up a merge replication (pull) and use web synchronization over
https. No active directory will be used.
The clients connect to the replisapi.dll hosted in the servers IIS and
supply a single predifined windows server user (Basic Authentication) to run
the dll. The dll uses a single predefined sql user to manage all sql traffic.
What licenses will be required?
As I understand I will need either 30 sql device cals or a per processor
license (the break of point in my case would be 35 cals).
I will probably also need an Internet Connector license for IIS or 30
windows cals.
Is this correct?Assuming the server has 1 physical processor (can be multi core) then you
will need 1 sql server 2005 processor licence - workgroup or standard.
Windows Server 2003 Standard - just the 5 cal one is fine; you don't need a
server cal for each user connecting because they aren't really users of the
server, they are using a service on the server...
Tony
--
Tony Rogerson, SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson
[Ramblings from the field from a SQL consultant]
http://sqlserverfaq.com
[UK SQL User Community]
"mommi" <mommi@.discussions.microsoft.com> wrote in message
news:A7DDF8D6-3387-411F-BCF4-2169DF60F4F7@.microsoft.com...
> This will be the setup:
> 1 server with:
> windows server 2003 standard
> sql server 2005 standard
> 30+ clients with:
> windows xp pro
> sql server express
> I will set up a merge replication (pull) and use web synchronization over
> https. No active directory will be used.
> The clients connect to the replisapi.dll hosted in the servers IIS and
> supply a single predifined windows server user (Basic Authentication) to
> run
> the dll. The dll uses a single predefined sql user to manage all sql
> traffic.
> What licenses will be required?
> As I understand I will need either 30 sql device cals or a per processor
> license (the break of point in my case would be 35 cals).
> I will probably also need an Internet Connector license for IIS or 30
> windows cals.
> Is this correct?|||Thanks for the reply.
But doesn't IIS require some sort of a license? For instance if you put up a
webserver using IIS then you need either a processor license or an internet
connector license because you can't predict how many users are actually going
to visit you website at any given time...
I'm assuming my setup would require some sort of license for IIS because of
that.
"Tony Rogerson" wrote:
> Assuming the server has 1 physical processor (can be multi core) then you
> will need 1 sql server 2005 processor licence - workgroup or standard.
> Windows Server 2003 Standard - just the 5 cal one is fine; you don't need a
> server cal for each user connecting because they aren't really users of the
> server, they are using a service on the server...
> Tony
> --
> Tony Rogerson, SQL Server MVP
> http://sqlblogcasts.com/blogs/tonyrogerson
> [Ramblings from the field from a SQL consultant]
> http://sqlserverfaq.com
> [UK SQL User Community]
>
> "mommi" <mommi@.discussions.microsoft.com> wrote in message
> news:A7DDF8D6-3387-411F-BCF4-2169DF60F4F7@.microsoft.com...
> > This will be the setup:
> > 1 server with:
> > windows server 2003 standard
> > sql server 2005 standard
> >
> > 30+ clients with:
> > windows xp pro
> > sql server express
> >
> > I will set up a merge replication (pull) and use web synchronization over
> > https. No active directory will be used.
> > The clients connect to the replisapi.dll hosted in the servers IIS and
> > supply a single predifined windows server user (Basic Authentication) to
> > run
> > the dll. The dll uses a single predefined sql user to manage all sql
> > traffic.
> >
> > What licenses will be required?
> >
> > As I understand I will need either 30 sql device cals or a per processor
> > license (the break of point in my case would be 35 cals).
> > I will probably also need an Internet Connector license for IIS or 30
> > windows cals.
> > Is this correct?
>|||Nope - that's part of the server price.
Anyway, the SQL bit is right; perhaps you should ask in the windows server
group and they'll confirm any fears you have.
--
Tony Rogerson, SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson
[Ramblings from the field from a SQL consultant]
http://sqlserverfaq.com
[UK SQL User Community]
"mommi" <mommi@.discussions.microsoft.com> wrote in message
news:1A5908E0-4554-4E59-97A0-233552B8F853@.microsoft.com...
> Thanks for the reply.
> But doesn't IIS require some sort of a license? For instance if you put up
> a
> webserver using IIS then you need either a processor license or an
> internet
> connector license because you can't predict how many users are actually
> going
> to visit you website at any given time...
> I'm assuming my setup would require some sort of license for IIS because
> of
> that.
>
> "Tony Rogerson" wrote:
>> Assuming the server has 1 physical processor (can be multi core) then you
>> will need 1 sql server 2005 processor licence - workgroup or standard.
>> Windows Server 2003 Standard - just the 5 cal one is fine; you don't need
>> a
>> server cal for each user connecting because they aren't really users of
>> the
>> server, they are using a service on the server...
>> Tony
>> --
>> Tony Rogerson, SQL Server MVP
>> http://sqlblogcasts.com/blogs/tonyrogerson
>> [Ramblings from the field from a SQL consultant]
>> http://sqlserverfaq.com
>> [UK SQL User Community]
>>
>> "mommi" <mommi@.discussions.microsoft.com> wrote in message
>> news:A7DDF8D6-3387-411F-BCF4-2169DF60F4F7@.microsoft.com...
>> > This will be the setup:
>> > 1 server with:
>> > windows server 2003 standard
>> > sql server 2005 standard
>> >
>> > 30+ clients with:
>> > windows xp pro
>> > sql server express
>> >
>> > I will set up a merge replication (pull) and use web synchronization
>> > over
>> > https. No active directory will be used.
>> > The clients connect to the replisapi.dll hosted in the servers IIS and
>> > supply a single predifined windows server user (Basic Authentication)
>> > to
>> > run
>> > the dll. The dll uses a single predefined sql user to manage all sql
>> > traffic.
>> >
>> > What licenses will be required?
>> >
>> > As I understand I will need either 30 sql device cals or a per
>> > processor
>> > license (the break of point in my case would be 35 cals).
>> > I will probably also need an Internet Connector license for IIS or 30
>> > windows cals.
>> > Is this correct?
>>