Subscription can't be created
in [Replication]
|
From: Jack on 16 Dec 2009 07:41 A customer of ours receives the following message as soon as we try to add a subscription to a compact framework database. The process could not initialize 'Microsoft SQL Server DATETIME (Later Wins) Conflict Resolver'. Verify that the component is registered correctly Is anyone familiar with this problem and does anyone know a possible solution to solve this?
From: Jack on 17 Dec 2009 01:24 Here some more information. Maybe it is usefull. Sql Server is installed on a 64 bit Windows 2008 Server. Active Directory is active We already did some tests which might be helpful. a.. setting all conflict resolvers default of a publication --> Subscription wizard is able to create subscription b.. Changing just one conflict resolver to not default (of course we set correct parameters) --> trying to reinitialize the subscription leads to the error shown before. c.. Changing just one conflict resolver to not default (of course we set correct parameters) --> an error occurs during the subscription wizard (same error) and subscription won't be created. The strange thing is that this is happening only at one 64 bit Windows 2008 Server. All similar servers just work fine. Reinstalling SQL Server isn't an option, because it is a production Server of a customer. Does anyone have an idea what could be the cause of this and how to fix it? We are running out of options and the customer is becoming very impatient at the moment. We tried to search for a similar situation, but didn't find a solution. "Jack" <jgkersemakers(a)noemail.noemail> wrote in message news:eIbgQ0kfKHA.5608(a)TK2MSFTNGP05.phx.gbl... >A customer of ours receives the following message as soon as we try to add a > subscription to a compact framework database. > > The process could not initialize 'Microsoft SQL Server DATETIME (Later Wins) > Conflict Resolver'. Verify that the component is registered correctly > > Is anyone familiar with this problem and does anyone know a possible > solution to solve this? > >
From: hilary on 22 Dec 2009 06:25 Can I see the schema of the problem table? "Jack" <jgkersemakers(a)noemail.noemail> wrote in message news:uxmhKGufKHA.2188(a)TK2MSFTNGP04.phx.gbl... Here some more information. Maybe it is usefull. Sql Server is installed on a 64 bit Windows 2008 Server. Active Directory is active We already did some tests which might be helpful. a.. setting all conflict resolvers default of a publication --> Subscription wizard is able to create subscription b.. Changing just one conflict resolver to not default (of course we set correct parameters) --> trying to reinitialize the subscription leads to the error shown before. c.. Changing just one conflict resolver to not default (of course we set correct parameters) --> an error occurs during the subscription wizard (same error) and subscription won't be created. The strange thing is that this is happening only at one 64 bit Windows 2008 Server. All similar servers just work fine. Reinstalling SQL Server isn't an option, because it is a production Server of a customer. Does anyone have an idea what could be the cause of this and how to fix it? We are running out of options and the customer is becoming very impatient at the moment. We tried to search for a similar situation, but didn't find a solution. "Jack" <jgkersemakers(a)noemail.noemail> wrote in message news:eIbgQ0kfKHA.5608(a)TK2MSFTNGP05.phx.gbl... >A customer of ours receives the following message as soon as we try to add a > subscription to a compact framework database. > > The process could not initialize 'Microsoft SQL Server DATETIME (Later Wins) > Conflict Resolver'. Verify that the component is registered correctly > > Is anyone familiar with this problem and does anyone know a possible > solution to solve this? > >
From: Jack on 23 Dec 2009 01:53 Hilary, Of course I can give you the schema of the table, but that doesn't seem to be the problem. --Here is the schema create table SOReceiveTime( SOGuid uniqueidentifier ROWGUIDCOL not null default (newsequentialid()), ReceiveTime datetime not null default getdate(), constraint pk_ReceiveTime primary key (SOGuid)); --Here the way to create the publication use master exec sp_replicationdboption @dbname = N'FADb', @optname = N'merge publish', @value = N'true' GO - Adding the merge publication use [FADb] exec sp_addmergepublication @publication = N'FATest', @description = N'Merge publication of database ''FADb'' from Publisher ''SRV001''.', @sync_mode = N'character', @retention = 0, @allow_push = N'true', @allow_pull = N'true', @allow_anonymous = N'true', @enabled_for_internet = N'false', @snapshot_in_defaultfolder = N'false', @alt_snapshot_folder = N'c:\snapshot', @compress_snapshot = N'false', @ftp_port = 21, @ftp_login = N'anonymous', @allow_subscription_copy = N'false', @add_to_active_directory = N'false', @dynamic_filters = N'false', @conflict_retention = 14, @keep_partition_changes = N'false', @allow_synctoalternate = N'false', @max_concurrent_merge = 0, @max_concurrent_dynamic_snapshots = 0, @use_partition_groups = N'false', @publication_compatibility_level = N'90RTM', @replicate_ddl = 1, @allow_subscriber_initiated_snapshot = N'false', @allow_web_synchronization = N'true', @allow_partition_realignment = N'true', @retention_period_unit = N'days', @conflict_logging = N'both', @automatic_reinitialization_policy = 0 GO exec sp_addpublication_snapshot @publication = N'FATest', @frequency_type = 4, @frequency_interval = 14, @frequency_relative_interval = 1, @frequency_recurrence_factor = 0, @frequency_subday = 1, @frequency_subday_interval = 5, @active_start_time_of_day = 500, @active_end_time_of_day = 235959, @active_start_date = 0, @active_end_date = 0, @job_login = null, @job_password = null, @publisher_security_mode = 1 exec sp_grant_publication_access @publication = N'FATest', @login = N'sa' GO exec sp_grant_publication_access @publication = N'FATest', @login = N'NT AUTHORITY\SYSTEM' GO exec sp_grant_publication_access @publication = N'FATest', @login = N'BUILTIN\Administrators' GO exec sp_grant_publication_access @publication = N'FATest', @login = N'SRV001\SQLServer2005SQLAgentUser$SRV001$MSSQLSERVER' GO exec sp_grant_publication_access @publication = N'FATest', @login = N'SRV001\SQLServer2005MSSQLUser$SRV001$MSSQLSERVER' GO exec sp_grant_publication_access @publication = N'FATest', @login = N'distributor_admin' GO -- Adding the merge articles use [FADb] exec sp_addmergearticle @publication = N'FATest', @article = N'SOReceiveTime', @source_owner = N'dbo', @source_object = N'SOReceiveTime', @type = N'table', @description = N'', @creation_script = N'', @pre_creation_cmd = N'drop', @schema_option = 0x0000000008034FF1, @identityrangemanagementoption = N'none', @destination_owner = N'dbo', @force_reinit_subscription = 1, @column_tracking = N'false', @article_resolver = N'Microsoft SQL Server Subscriber Always Wins Conflict Resolver', @subset_filterclause = N'', @vertical_partition = N'false', @verify_resolver_signature = 0, @allow_interactive_resolver = N'false', @fast_multicol_updateproc = N'true', @check_permissions = 0, @subscriber_upload_options = 0, @delete_tracking = N'true', @compensate_for_errors = N'false', @stream_blob_columns = N'false', @partition_options = 0 GO use [FADb] exec sp_changemergepublication N'FATest', N'status', N'active' GO As you can see it's a fairly simple table. This synchronization works just fine except at one of our customers. At one customer synchronization just fails, because of the article resolver. Whenever we change the article resolver back to the default resolver, synchronization works just fine (We replicate to compact database). Even when pciking another article, whenever not all article resolvers are default the error appears. In the meantime we did some more research and it seems to be an installation problem, maybe the server was installed incorrectly. As we digged deeper we discovered it has to be an IIS problem. Whenever we create a similar publication that replicates to antoher SQL server (synchronization is not done by web synchronization), the error doesn't appear. The problem we have is that we are replicating to mobile devices, so we use IIS for web synchronization. And there seems to be the problem. We are trying to find out, whether an incorrect order of installation could cause the problem (First installing SQL Server and then IIS could be a possible reason), the customer installed the base components themselve. "hilary" <hilary.cotter(a)gmail.com> wrote in message news:782BE20D-55CD-4766-AACF-A80A271FEF71(a)microsoft.com... Can I see the schema of the problem table? "Jack" <jgkersemakers(a)noemail.noemail> wrote in message news:uxmhKGufKHA.2188(a)TK2MSFTNGP04.phx.gbl... Here some more information. Maybe it is usefull. Sql Server is installed on a 64 bit Windows 2008 Server. Active Directory is active We already did some tests which might be helpful. a.. setting all conflict resolvers default of a publication --> Subscription wizard is able to create subscription b.. Changing just one conflict resolver to not default (of course we set correct parameters) --> trying to reinitialize the subscription leads to the error shown before. c.. Changing just one conflict resolver to not default (of course we set correct parameters) --> an error occurs during the subscription wizard (same error) and subscription won't be created. The strange thing is that this is happening only at one 64 bit Windows 2008 Server. All similar servers just work fine. Reinstalling SQL Server isn't an option, because it is a production Server of a customer. Does anyone have an idea what could be the cause of this and how to fix it? We are running out of options and the customer is becoming very impatient at the moment. We tried to search for a similar situation, but didn't find a solution. "Jack" <jgkersemakers(a)noemail.noemail> wrote in message news:eIbgQ0kfKHA.5608(a)TK2MSFTNGP05.phx.gbl... >A customer of ours receives the following message as soon as we try to add a > subscription to a compact framework database. > > The process could not initialize 'Microsoft SQL Server DATETIME (Later Wins) > Conflict Resolver'. Verify that the component is registered correctly > > Is anyone familiar with this problem and does anyone know a possible > solution to solve this? > >
From: Jack on 7 Jan 2010 08:02
We have been doing some more investigation. It seems to be a problem with IIS, but don't know exactly what is going wrong. Windows 2008 (64 bits) Dutch version in installed at the server. When setting up a replication to a SQL Server database that doesn't use IIS, we can use the conflict resolvers without any problem. Only when we replicate to a device (Compact Framework) then the error occurs. Could a IIS lockdown tool be the cause? "Jack" <jgkersemakers(a)noemail.noemail> wrote in message news:eOoUoy5gKHA.1536(a)TK2MSFTNGP06.phx.gbl... Hilary, Of course I can give you the schema of the table, but that doesn't seem to be the problem. --Here is the schema create table SOReceiveTime( SOGuid uniqueidentifier ROWGUIDCOL not null default (newsequentialid()), ReceiveTime datetime not null default getdate(), constraint pk_ReceiveTime primary key (SOGuid)); --Here the way to create the publication use master exec sp_replicationdboption @dbname = N'FADb', @optname = N'merge publish', @value = N'true' GO - Adding the merge publication use [FADb] exec sp_addmergepublication @publication = N'FATest', @description = N'Merge publication of database ''FADb'' from Publisher ''SRV001''.', @sync_mode = N'character', @retention = 0, @allow_push = N'true', @allow_pull = N'true', @allow_anonymous = N'true', @enabled_for_internet = N'false', @snapshot_in_defaultfolder = N'false', @alt_snapshot_folder = N'c:\snapshot', @compress_snapshot = N'false', @ftp_port = 21, @ftp_login = N'anonymous', @allow_subscription_copy = N'false', @add_to_active_directory = N'false', @dynamic_filters = N'false', @conflict_retention = 14, @keep_partition_changes = N'false', @allow_synctoalternate = N'false', @max_concurrent_merge = 0, @max_concurrent_dynamic_snapshots = 0, @use_partition_groups = N'false', @publication_compatibility_level = N'90RTM', @replicate_ddl = 1, @allow_subscriber_initiated_snapshot = N'false', @allow_web_synchronization = N'true', @allow_partition_realignment = N'true', @retention_period_unit = N'days', @conflict_logging = N'both', @automatic_reinitialization_policy = 0 GO exec sp_addpublication_snapshot @publication = N'FATest', @frequency_type = 4, @frequency_interval = 14, @frequency_relative_interval = 1, @frequency_recurrence_factor = 0, @frequency_subday = 1, @frequency_subday_interval = 5, @active_start_time_of_day = 500, @active_end_time_of_day = 235959, @active_start_date = 0, @active_end_date = 0, @job_login = null, @job_password = null, @publisher_security_mode = 1 exec sp_grant_publication_access @publication = N'FATest', @login = N'sa' GO exec sp_grant_publication_access @publication = N'FATest', @login = N'NT AUTHORITY\SYSTEM' GO exec sp_grant_publication_access @publication = N'FATest', @login = N'BUILTIN\Administrators' GO exec sp_grant_publication_access @publication = N'FATest', @login = N'SRV001\SQLServer2005SQLAgentUser$SRV001$MSSQLSERVER' GO exec sp_grant_publication_access @publication = N'FATest', @login = N'SRV001\SQLServer2005MSSQLUser$SRV001$MSSQLSERVER' GO exec sp_grant_publication_access @publication = N'FATest', @login = N'distributor_admin' GO -- Adding the merge articles use [FADb] exec sp_addmergearticle @publication = N'FATest', @article = N'SOReceiveTime', @source_owner = N'dbo', @source_object = N'SOReceiveTime', @type = N'table', @description = N'', @creation_script = N'', @pre_creation_cmd = N'drop', @schema_option = 0x0000000008034FF1, @identityrangemanagementoption = N'none', @destination_owner = N'dbo', @force_reinit_subscription = 1, @column_tracking = N'false', @article_resolver = N'Microsoft SQL Server Subscriber Always Wins Conflict Resolver', @subset_filterclause = N'', @vertical_partition = N'false', @verify_resolver_signature = 0, @allow_interactive_resolver = N'false', @fast_multicol_updateproc = N'true', @check_permissions = 0, @subscriber_upload_options = 0, @delete_tracking = N'true', @compensate_for_errors = N'false', @stream_blob_columns = N'false', @partition_options = 0 GO use [FADb] exec sp_changemergepublication N'FATest', N'status', N'active' GO As you can see it's a fairly simple table. This synchronization works just fine except at one of our customers. At one customer synchronization just fails, because of the article resolver. Whenever we change the article resolver back to the default resolver, synchronization works just fine (We replicate to compact database). Even when pciking another article, whenever not all article resolvers are default the error appears. In the meantime we did some more research and it seems to be an installation problem, maybe the server was installed incorrectly. As we digged deeper we discovered it has to be an IIS problem. Whenever we create a similar publication that replicates to antoher SQL server (synchronization is not done by web synchronization), the error doesn't appear. The problem we have is that we are replicating to mobile devices, so we use IIS for web synchronization. And there seems to be the problem. We are trying to find out, whether an incorrect order of installation could cause the problem (First installing SQL Server and then IIS could be a possible reason), the customer installed the base components themselve. "hilary" <hilary.cotter(a)gmail.com> wrote in message news:782BE20D-55CD-4766-AACF-A80A271FEF71(a)microsoft.com... Can I see the schema of the problem table? "Jack" <jgkersemakers(a)noemail.noemail> wrote in message news:uxmhKGufKHA.2188(a)TK2MSFTNGP04.phx.gbl... Here some more information. Maybe it is usefull. Sql Server is installed on a 64 bit Windows 2008 Server. Active Directory is active We already did some tests which might be helpful. a.. setting all conflict resolvers default of a publication --> Subscription wizard is able to create subscription b.. Changing just one conflict resolver to not default (of course we set correct parameters) --> trying to reinitialize the subscription leads to the error shown before. c.. Changing just one conflict resolver to not default (of course we set correct parameters) --> an error occurs during the subscription wizard (same error) and subscription won't be created. The strange thing is that this is happening only at one 64 bit Windows 2008 Server. All similar servers just work fine. Reinstalling SQL Server isn't an option, because it is a production Server of a customer. Does anyone have an idea what could be the cause of this and how to fix it? We are running out of options and the customer is becoming very impatient at the moment. We tried to search for a similar situation, but didn't find a solution. "Jack" <jgkersemakers(a)noemail.noemail> wrote in message news:eIbgQ0kfKHA.5608(a)TK2MSFTNGP05.phx.gbl... >A customer of ours receives the following message as soon as we try to add a > subscription to a compact framework database. > > The process could not initialize 'Microsoft SQL Server DATETIME (Later Wins) > Conflict Resolver'. Verify that the component is registered correctly > > Is anyone familiar with this problem and does anyone know a possible > solution to solve this? > > |