Merge Replication Schema Sync Problems

I am using a merge publication set to synchronize schema changes. Why am I getting the following message when I try to sync after having added columns in the publication database using ALTER TABLE statements?

The schema definition of the destination table ... in the subscription database does not match the schema definition of the source table in the publication database. Reinitialize the subscription without a snapshot after ensuring that the schema definition of the destination table is the same as the source table.

Also, why doesn't reinitializing the subscription with @.upload_first = false not fix the problem?

I have encountered this problem with both merge replication and with transactional replication

When you add columns at the publisher they do not always get published correctly. You can check in the GUI for the properties of the article and will sometimes see that the new columns are not checked.

I have found that it is necessary to either use the GUI or TSQL to explicitly add the missing columns to the publication. If you have tried to merge resync before doing this then I think that you will need to reinitialise your subscriptions

In my experience this behaviour seems to happen frequently with transactional replication, but only occasionally with merge replication

reinit with upload first won't fix the problem if the merge is attempting to synchronize and enumerate data changes with different schemas on the publisher and subscriber

aero1

Merge Replication Problem (Urgent)

Dear All,
I have an error message when I'm trying to synchronize from SQL Server
Ce to SQL Server 2000.
The error message is
"The process could not deliver the snapshot to the subscriber"
I already know that I need to verify that the IIS user your SQL Server
CE Server Agent is running under has READ permissions to this folder.
But I don't know how to verify that?
You can see my sqlserverce authentication and IIS configuration on the
attachement.
Pls give me some ideas to solve it out?
Thanks
Robert Lie
Have a look at
http://msdn.microsoft.com/library/de...bleconnect.asp
"Robert Lie" wrote:

> Dear All,
> I have an error message when I'm trying to synchronize from SQL Server
> Ce to SQL Server 2000.
> The error message is
> "The process could not deliver the snapshot to the subscriber"
> I already know that I need to verify that the IIS user your SQL Server
> CE Server Agent is running under has READ permissions to this folder.
> But I don't know how to verify that?
> You can see my sqlserverce authentication and IIS configuration on the
> attachement.
> Pls give me some ideas to solve it out?
> Thanks
> Robert Lie
>
>
>
>
|||You need to use an alternate snapshot share which you have specified in your
vd creation wizard. I would use anonymous authentication in your code.
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
"Robert Lie" <robert.lie24@.gmail.com> wrote in message
news:u%23dxwxhoFHA.2904@.tk2msftngp13.phx.gbl...
> Dear All,
> I have an error message when I'm trying to synchronize from SQL Server
> Ce to SQL Server 2000.
> The error message is
> "The process could not deliver the snapshot to the subscriber"
> I already know that I need to verify that the IIS user your SQL Server
> CE Server Agent is running under has READ permissions to this folder.
> But I don't know how to verify that?
> You can see my sqlserverce authentication and IIS configuration on the
> attachement.
> Pls give me some ideas to solve it out?
> Thanks
> Robert Lie
>
>
>
>


sql

merge replication only need passwrd first time

Hello
I have an applicatiuon on a pda where i can synchronize the pda with
sql server 2000
When I start the application on open the synchronize window i have to
enter a user id and password.
repl.InternetLogin = userId
repl.InternetPassword = Password
I start the synchronization and it works.
The second time i synchronize it still works even with no password.
Why is that? I have to stop the application and start it again for it
to work.
If I enetr a wrong password when I synchronize the first time, I gett e
message saying: Authentication failed on the computer running IIS
I would like to get this message all the time when I synchronize with
an incorrect password.
What can I be doing wrong.
What form of authentication are you using on your IIS Server. Is it possible
that you have a blank password for the account userID?
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
<jensenove@.netscape.net> wrote in message
news:1144351127.584971.98050@.t31g2000cwb.googlegro ups.com...
> Hello
> I have an applicatiuon on a pda where i can synchronize the pda with
> sql server 2000
> When I start the application on open the synchronize window i have to
> enter a user id and password.
> repl.InternetLogin = userId
> repl.InternetPassword = Password
>
> I start the synchronization and it works.
> The second time i synchronize it still works even with no password.
> Why is that? I have to stop the application and start it again for it
> to work.
> If I enetr a wrong password when I synchronize the first time, I gett e
> message saying: Authentication failed on the computer running IIS
> I would like to get this message all the time when I synchronize with
> an incorrect password.
> What can I be doing wrong.
>

Merge replication issues

We are getting a conflict error message "cannot synchronize, row was updated
outside of replication".
We cannot figure out what is causing this.
Can having different foreign key constraints at a publisher and subscriber
level cause problems with merge replication?
Sorry for the lack of information, but hopefully someone can help!
I have not seen that error message, but based upon my own limited
experiences, I can assure you that different constraints could certainly
create issues.
"llihp" <phill_dutton@.hotmail.com> wrote in message
news:428cb301_1@.x-privat.org...
> We are getting a conflict error message "cannot synchronize, row was
> updated
> outside of replication".
> We cannot figure out what is causing this.
> Can having different foreign key constraints at a publisher and subscriber
> level cause problems with merge replication?
> Sorry for the lack of information, but hopefully someone can help!
>
|||perhaps the row was updated by a process which did not trigger the triggers,
i.e. bcp, dts.
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
"llihp" <phill_dutton@.hotmail.com> wrote in message
news:428cb301_1@.x-privat.org...
> We are getting a conflict error message "cannot synchronize, row was
updated
> outside of replication".
> We cannot figure out what is causing this.
> Can having different foreign key constraints at a publisher and subscriber
> level cause problems with merge replication?
> Sorry for the lack of information, but hopefully someone can help!
>
|||"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eYHGHAPXFHA.2348@.TK2MSFTNGP14.phx.gbl...
> perhaps the row was updated by a process which did not trigger the
triggers,
> i.e. bcp, dts.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
I'm not sure what bcp is(?), but we aren't using any DTS packages within the
application.
Basically we are running a VB application at the sites, and this is
manipulating all the data within the database which is then susposed to be
sent back to the central server. We are having no issues with inserted rows
being replicated, it is only updates which are proving problematic.
|||Hi,
I am also getting the same error. I have multiple publishers with a central
subscriber ( using merge property -exchangetype 2). Please let me know if
there is any answere to it.
One stange thing that I have noticed is following:
I have Publications on Same Articles at 4 sites . Some articles have 4
insert, 4 update and 4 delete triggers but some articles get only 1 trigger
for update, 1 for delete and 1 for insert. Why is this so?
"llihp" wrote:

> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:eYHGHAPXFHA.2348@.TK2MSFTNGP14.phx.gbl...
> triggers,
> I'm not sure what bcp is(?), but we aren't using any DTS packages within the
> application.
> Basically we are running a VB application at the sites, and this is
> manipulating all the data within the database which is then susposed to be
> sent back to the central server. We are having no issues with inserted rows
> being replicated, it is only updates which are proving problematic.
>
>
|||Are all the triggers replication related? There should only be one trigger.
You might need to regenerate and resend your snapshot.
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
"Vikas Kohli" <VikasKohli@.discussions.microsoft.com> wrote in message
news:C682F2C2-AFAD-42FC-90C1-F81B1BE12928@.microsoft.com...
> Hi,
> I am also getting the same error. I have multiple publishers with a
central
> subscriber ( using merge property -exchangetype 2). Please let me know if
> there is any answere to it.
> One stange thing that I have noticed is following:
> I have Publications on Same Articles at 4 sites . Some articles have 4
> insert, 4 update and 4 delete triggers but some articles get only 1
trigger[vbcol=seagreen]
> for update, 1 for delete and 1 for insert. Why is this so?
> "llihp" wrote:
the[vbcol=seagreen]
be[vbcol=seagreen]
rows[vbcol=seagreen]

Merge replication and SSL

Hi Readers,

I am currently working on a merge replication szenario. I managed to synchronize some SQL Server 2005 database tables with my SQL Server 2005 Mobile Edition database.

Now I want to focus on security. I know that I want do do basic authentication together with SSL. I used selfssl from the iis resource kit to produce a certificate for the iis.

How do I install the ssl certificate on the mobile device? Do I need some tools? Do I need to export that certificate and if yes, how do I do that?

Can you give me some general hints how to solve this as I am totally stuck and don't know where to start.

Regards
Tobias

Tobias,

Here is what you'll need to do:

1. get a test certificate from Verisign - this process will generate a .CER file. I have had trouble getting this to work with certificates generated by the IIS Resource Kit and you can get test certs from Verisign for free. click on Free SSL Trial Certificate on this site: http://www.verisign.com/products-services/security-services/ssl/index.html

2. copy the .CER file to the mobile device. Once there, simply tap on the .CER file and PPC2003 and later devices will ask you if you want to install this certificate on the device - say yes.

3. re-run the SQL Mobile Configure Web Replication wizard on the server and provide the information about your SSL cert - specify that SSL is required and you wish to use Basic Auth

4. in your mobile app, be sure to change the replication url from http to https and provide the InternetUser and InternetPassword properties to get through Basic Auth.

First test that you can get to https://{serverIP}/{virt dir}/sqlcesa30.dll in Pocket IE on your device - of course you will be prompted for Basic Auth credentials - but this will verify that yoru transport and the SSL encryption on that transport are working. Then transition to testing your actual mobile device.

-Darren

|||

I want to add one more thing to this - it would appear that Verisign SSL certificates on Windows Mobile 5 devices are problematic for merge replication between SQL Mobile and SQL Server 2005. Certificates from Thawte http://www.thawte.com/ work fine. I am pursuing a better explanation as to why this is and will keep everyone posted. This is only true for Windows Mobile 5 devices - Verisign certs work just fine with merge replication on PPC2003 devices.

Darren