SQL Server Express 2014 Merge Replication

Paul Bill 66

I have a address table that has a geography field in it that allows nulls. I have added a field to the table so the geography field is now second to last in the table. I can initially sync the mobile device without issues. However if I add a address to the table and try to sync I receive the following error:

The Merge Agent failed because the schema of the article at the Publisher does not match the schema of the article at the Subscriber. This can occur when there are pending DDL changes waiting to be applied at the Subscriber. Restart the Merge Agent to apply the DDL changes and synchronize the subscription.
The Merge Agent failed because the schema of the article at the Publisher does not match the schema of the article at the Subscriber. This can occur when there are pending DDL changes waiting to be applied at the Subscriber. Restart the Merge Agent to apply the DDL changes and synchronize the subscription.
Error converting data type varchar to geometry.

Both the server and the mobile device have 2014 SQL Server and their compatibility level is set to the same, the mobile device is SQL 2014 Express.

How do I fix this issue? Where do I fix this issue, on the server where the publication is or on the mobile device where the subscription is?

Any help is appreciated.

Thanks.

Cris Zhan-MSFT 6,616 Reputation points

2020-12-14T09:48:23.467+00:00

Hi @Paul Bill ,
May I ask for the detailed version information of subscriber and publisher. (select @@version)
Does restarting the merge agent work?

here is a similar case that might help::
https://serverfault.com/questions/180791/merge-replication-with-geometry-data-type
Paul Bill 66 Reputation points

2020-12-14T21:12:29.357+00:00

The server version is:

Microsoft SQL Server 2014 (SP2-CU18) (KB4500180) - 12.0.5687.1 (X64)
Jul 20 2019 21:27:07
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)

The local version for 32bit instance of SQL Server express(Installed for our 32bit version of our application) is:

Microsoft SQL Server 2014 - 12.0.2000.8 (Intel X86)
Feb 20 2014 19:20:46
Copyright (c) Microsoft Corporation
Express Edition on Windows NT 6.3 <X64> (Build 18363: ) (WOW64)

The local version for 64bit instance of SQL Server express(installed for our 64 bit version of our application) is:

Microsoft SQL Server 2014 (SP2-GDR) (KB4505217) - 12.0.5223.6 (X64)
May 26 2019 20:36:50
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.3 <X64> (Build 19041: )

And no, restarting the merge agent did not help, same error.
Paul Bill 66 Reputation points

2020-12-14T21:55:45.153+00:00

The express editions are downloaded directly from Microsoft depending on a 32 or 64 bit install of our software.
Cris Zhan-MSFT 6,616 Reputation points

2020-12-15T03:03:49.067+00:00

Hi @Paul Bill ,

Thanks for the detailed information. I noticed that there are three editions of SQL Server: Standard, Express, Enterprise.
Are there two subscribers in this merge replication topology? Does the above problem exist on both subscribers? Push or Pull subscriptions(client and server subscriptions)?
A Subscriber to a merge publication can be all versions equal to or lower than the Publisher version. In order to prevent any problems from being fixed in the new SP or CU, please try to upgrade the SQL Server version on the subscriber.

And did you check the case I mentioned in the last reply.

Best Regards,
Paul Bill 66 Reputation points

2020-12-16T12:30:41.827+00:00

My mistake, I took the wrong 64 bit, it should be an express edition downloaded like the 32 bit from Microsoft.com just 64 bit. There are multiple subscribers to the database and there are 32 and 64 bit versions of SQL express installed on the local devices syncing to the server. I did try the option in the link above but it did not work. I am still getting the same error. I didn't do it for all the tables in my database, just the address table where the spatial field is located.
Cris Zhan-MSFT 6,616 Reputation points

2020-12-17T03:13:59.807+00:00

Hi @Paul Bill ,
So it cannot be done on all subscribers, regardless of the 34-bit or 64-bit version. You can try a test table without a spatial field and another test table with a spatial field. To determine whether the problem is only related to the spatial field.

Share via

SQL Server Express 2014 Merge Replication