CCX 5 Cluster error Datastore: Repository

carlosg · ‎03-22-2010

Hi

I have "CCX 5.0(2)_Build064 Premium" on a cluster CCXPRI and CCXSEC.

On System->Datastore Control Center->Repository it shows only CCXPRI registered. And get the following failure:

"failure ocurred while performing the operation. The cluster information and subscriber configuration does not match. The subscriber might be dropped (Please check SQL server log for more details).

How can I fix this failure?

David Hailey · ‎03-22-2010

If you grab the SQL log as the error indicates and post the info, that would be greatly appreciated. Could be a few different things.

Hailey

Please rate helpful posts!

Aaron Harrison · ‎03-23-2010

Hi

A quick way to fix this (if it is the Subscriber that has the problem obviously... probably not wise on a Publisher) is to go into Component Activation, and deactivate the Repository data store.

Once done, reactivate it. This rebuilds the SQL replication.

If it fails for whatever reason, report back the exact error as you must have something fundamental wrong that is preventing replication from setting up (e.g. name resolution - have you added the servers to each servers' host file?)

Regards

Aaron

Please rate helpful posts...

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!

carlosg · ‎03-29-2010

Hi.

I just restored the CRS SQL Server–Repository from System->Control Center->CCXSEC.

But the error "failure ocurred while performing the operation. The cluster information and subscriber configuration does not match. The subscriber might be dropped (Please check SQL server log for more details)” Still Continue appearing in the Datastore Control Center->Repository.

The tracing and file generated is:

[3/25/2010 7:46:18 PM]MXMXC-CCE-PRI\CRSSQL.db_cra: {call sp_MSgetversion }

Connecting to Subscriber 'MXMXC-CCE-SEC\CRSSQL.db_cra'

Server: MXMXC-CCE-SEC\CRSSQL

DBMS: Microsoft SQL Server

Version: 08.00.2156

user name: dbo

API conformance: 2

SQL conformance: 1

transaction capable: 2

read only: N

identifier quote char: "

non_nullable_columns: 1

owner usage: 31

max table name len: 128

max column name len: 128

need long data len: Y

max columns in table: 1024

max columns in index: 16

max char literal len: 524288

max statement len: 524288

max row size: 524288

[3/25/2010 7:46:18 PM]MXMXC-CCE-SEC\CRSSQL.db_cra: {call sp_MSgetversion }

Connecting to Publisher 'MXMXC-CCE-PRI\CRSSQL.db_cra'

Server: MXMXC-CCE-PRI\CRSSQL

DBMS: Microsoft SQL Server

Version: 08.00.2156

user name: dbo

API conformance: 2

SQL conformance: 1

transaction capable: 2

read only: N

identifier quote char: "

non_nullable_columns: 1

owner usage: 31

max table name len: 128

max column name len: 128

need long data len: Y

max columns in table: 1024

max columns in index: 16

max char literal len: 524288

max statement len: 524288

max row size: 524288

[3/25/2010 7:46:18 PM]MXMXC-CCE-PRI\CRSSQL.db_cra: {call sp_MSgetversion }

Connecting to Subscriber 'MXMXC-CCE-SEC\CRSSQL.db_cra'

Server: MXMXC-CCE-SEC\CRSSQL

DBMS: Microsoft SQL Server

Version: 08.00.2156

user name: dbo

API conformance: 2

SQL conformance: 1

transaction capable: 2

read only: N

identifier quote char: "

non_nullable_columns: 1

owner usage: 31

max table name len: 128

max column name len: 128

need long data len: Y

max columns in table: 1024

max columns in index: 16

max char literal len: 524288

max statement len: 524288

max row size: 524288

[3/25/2010 7:46:18 PM]MXMXC-CCE-SEC\CRSSQL.db_cra: {call sp_MSgetversion }

Connecting to Publisher 'MXMXC-CCE-PRI\CRSSQL.db_cra'

Server: MXMXC-CCE-PRI\CRSSQL

DBMS: Microsoft SQL Server

Version: 08.00.2156

user name: dbo

API conformance: 2

SQL conformance: 1

transaction capable: 2

read only: N

identifier quote char: "

non_nullable_columns: 1

owner usage: 31

max table name len: 128

max column name len: 128

need long data len: Y

max columns in table: 1024

max columns in index: 16

max char literal len: 524288

max statement len: 524288

max row size: 524288

[3/25/2010 7:46:18 PM]MXMXC-CCE-PRI\CRSSQL.db_cra: {call sp_MSgetversion }

Connecting to Subscriber 'MXMXC-CCE-SEC\CRSSQL.db_cra'

Server: MXMXC-CCE-SEC\CRSSQL

DBMS: Microsoft SQL Server

Version: 08.00.2156

user name: dbo

API conformance: 2

SQL conformance: 1

transaction capable: 2

read only: N

identifier quote char: "

non_nullable_columns: 1

owner usage: 31

max table name len: 128

max column name len: 128

need long data len: Y

max columns in table: 1024

max columns in index: 16

max char literal len: 524288

max statement len: 524288

max row size: 524288

[3/25/2010 7:46:18 PM]MXMXC-CCE-SEC\CRSSQL.db_cra: {call sp_MSgetversion }

Connecting to Publisher 'MXMXC-CCE-PRI\CRSSQL.db_cra'

Server: MXMXC-CCE-PRI\CRSSQL

DBMS: Microsoft SQL Server

Version: 08.00.2156

user name: dbo

API conformance: 2

SQL conformance: 1

transaction capable: 2

read only: N

identifier quote char: "

non_nullable_columns: 1

owner usage: 31

max table name len: 128

max column name len: 128

need long data len: Y

max columns in table: 1024

max columns in index: 16

max char literal len: 524288

max statement len: 524288

max row size: 524288

[3/25/2010 7:46:18 PM]MXMXC-CCE-PRI\CRSSQL.db_cra: {call sp_MSgetversion }

Connecting to Subscriber 'MXMXC-CCE-SEC\CRSSQL.db_cra'

Server: MXMXC-CCE-SEC\CRSSQL

DBMS: Microsoft SQL Server

Version: 08.00.2156

user name: dbo

API conformance: 2

SQL conformance: 1

transaction capable: 2

read only: N

identifier quote char: "

non_nullable_columns: 1

owner usage: 31

max table name len: 128

max column name len: 128

need long data len: Y

max columns in table: 1024

max columns in index: 16

max char literal len: 524288

max statement len: 524288

max row size: 524288

[3/25/2010 7:46:18 PM]MXMXC-CCE-SEC\CRSSQL.db_cra: {call sp_MSgetversion }

Percent Complete: 4

Downloaded 12 data changes (11 inserts, 0 updates, 1 deletes, 0 conflicts).

Percent Complete: 4

Uploading data changes to the Publisher

Percent Complete: 4

No data needed to be merged.

Percent Complete: 4

Downloading data changes to the Subscriber

Percent Complete: 4

No data needed to be merged.

Percent Complete: 4

Uploading data changes to the Publisher

Percent Complete: 4

No data needed to be merged.

Percent Complete: 4

Downloading data changes to the Subscriber

Percent Complete: 4

No data needed to be merged.

Percent Complete: 4

Uploading data changes to the Publisher

Percent Complete: 4

No data needed to be merged.

Percent Complete: 4

Downloading data changes to the Subscriber

Percent Complete: 4

Downloaded 1 data changes (1 inserts, 0 updates, 0 deletes, 0 conflicts).

Percent Complete: 4

Uploading data changes to the Publisher

Percent Complete: 4

No data needed to be merged.

Percent Complete: 4

Downloading data changes to the Subscriber

Percent Complete: 4

Downloaded 1 data changes (1 inserts, 0 updates, 0 deletes, 0 conflicts).

Percent Complete: 4

Uploading data changes to the Publisher

Percent Complete: 4

No data needed to be merged.

Percent Complete: 4

Downloading data changes to the Subscriber

Percent Complete: 4

Downloaded 1 data changes (1 inserts, 0 updates, 0 deletes, 0 conflicts).

Percent Complete: 4

Uploading data changes to the Publisher

Percent Complete: 4

No data needed to be merged.

Percent Complete: 4

Downloading data changes to the Subscriber

Percent Complete: 4

No data needed to be merged.

Percent Complete: 4

Uploading data changes to the Publisher

Aaron Harrison · ‎03-30-2010

Hi

What exactly do you mean by ' I just restored the CRS SQL Server–Repository from System->Control Center->CCXSEC.'?

Aaron

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!