Cannot sync when Auto Identity Ranges Enabled?

I have been pulling my hair out with this for some time now:
I have a small db which I need to merge replicate with a number of PocketPC
devices. NT Authentication is used.
If I do not enable the automatic identity range option, the PocketPC clients
can connect without error. However, if I enable this (which I need to), the
PocketPC user gets a host of errors:
1. (Code 80004005) A call to SQL Server Reconciler failed.
2. (Code 80045007) The merge process could not retrieve article information
for publication 'Survey'
3. (Code 0) {call sp_MShelpmergearticles(?,8000000,?)}
4. (Code 4833) Could not connect to server 'SERVER1' because 'SQLAdmin' is
not defined as a remote login at the server.
SQLAdmin is our Service startup account. It is a member of the Administrator
group.
The user account being used to connect is a standard domain user account.
If I add the user to the Administrators group the process succeeds
everytime. I have checked permissions on the SQLCE folder, and snapshot
folders and AFAIK they are correct (i.e. the user has write permission).
It looks like a permission problem, but I dont know where. It seems the only
solution to this is to add the user to the Administrators group (totally
unacceptable!).
Any suggestions because I am at a complete loss?
Cheers,
James Goodman
Did you re-run your merge agent? I've had no problem using a domain user
account, particularly if set up for anonymous subscribers. Also, you should
be getting a 280xx error number back from the errors collection in the .Net
code. The MSDN site has a list that precisely defines what each of those
errors mean.
"James Goodman" <jamesATnorton-associates.co.ukREMOVE> wrote in message
news:ufn1ZWObFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have been pulling my hair out with this for some time now:
> I have a small db which I need to merge replicate with a number of
> PocketPC devices. NT Authentication is used.
> If I do not enable the automatic identity range option, the PocketPC
> clients can connect without error. However, if I enable this (which I need
> to), the PocketPC user gets a host of errors:
> 1. (Code 80004005) A call to SQL Server Reconciler failed.
> 2. (Code 80045007) The merge process could not retrieve article
> information for publication 'Survey'
> 3. (Code 0) {call sp_MShelpmergearticles(?,8000000,?)}
> 4. (Code 4833) Could not connect to server 'SERVER1' because 'SQLAdmin' is
> not defined as a remote login at the server.
> SQLAdmin is our Service startup account. It is a member of the
> Administrator group.
> The user account being used to connect is a standard domain user account.
>
> If I add the user to the Administrators group the process succeeds
> everytime. I have checked permissions on the SQLCE folder, and snapshot
> folders and AFAIK they are correct (i.e. the user has write permission).
> It looks like a permission problem, but I dont know where. It seems the
> only solution to this is to add the user to the Administrators group
> (totally unacceptable!).
>
> Any suggestions because I am at a complete loss?
> --
> Cheers,
> James Goodman
>

Cannot replicate non dbo table when dbo table exists

I attempt to replicate a non dbo table, e.g. user1.table1. In the mean time
dbo.table1 exists in both publisher and subscriber and is replicated. When
the replication ran, it drop the dbo.table1 in subscriber and created new
dbo.table1 from user1.table1. How do I replicate non dbo tables when dbo
tables with same names exist?
Thanks!
right click on your publication, select properties, click on the articles
tab, click the browse button, in the general tab make sure that the
destination owner name is the name of the owner you want on the subscriber.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Charts" <Acharts@.newsgroup.nospam> wrote in message
news:FDF72545-7875-491E-B51F-9CECEE79FB4C@.microsoft.com...
>I attempt to replicate a non dbo table, e.g. user1.table1. In the mean
>time
> dbo.table1 exists in both publisher and subscriber and is replicated. When
> the replication ran, it drop the dbo.table1 in subscriber and created new
> dbo.table1 from user1.table1. How do I replicate non dbo tables when dbo
> tables with same names exist?
> Thanks!
>
|||Thanks so much and I'll follow up.
"Charts" wrote:

> I attempt to replicate a non dbo table, e.g. user1.table1. In the mean time
> dbo.table1 exists in both publisher and subscriber and is replicated. When
> the replication ran, it drop the dbo.table1 in subscriber and created new
> dbo.table1 from user1.table1. How do I replicate non dbo tables when dbo
> tables with same names exist?
> Thanks!
>