Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

Patch in Subscriber 4.2 Failed

Hello,

I'm trying to patch a cluster callmanager 4.2(3)SR1 to 4.2(3)SR2, the patch is instaled well in the publisher but fail in the subscriber with the message error "Error Fatal : Replication initialisation failed, please make sure that all nodes in the cluster are online, ane the same version before upgrading the patch"

please to help me to resolve this problem.

Regards,

Mohamed

6 REPLIES
Community Member

Re: Patch in Subscriber 4.2 Failed

Following the logs of MS SQL Server and SGL Agent

MS SQO LOG :

----------------------

2010-06-24 12:25:55.29 server    Microsoft SQL Server  2000 - 8.00.2039 (Intel X86)
May  3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)

2010-06-24 12:25:55.31 server    Copyright (C) 1988-2002 Microsoft Corporation.
2010-06-24 12:25:55.31 server    All rights reserved.
2010-06-24 12:25:55.31 server    Server Process ID is 4880.
2010-06-24 12:25:55.31 server    Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2010-06-24 12:25:55.31 server    SQL Server is starting at priority class 'normal'(1 CPU detected).
2010-06-24 12:25:55.39 server    SQL Server configured for thread mode processing.
2010-06-24 12:25:55.39 server    Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2010-06-24 12:25:55.40 server    Attempting to initialize Distributed Transaction Coordinator.
2010-06-24 12:25:56.44 spid3     Starting up database 'master'.
2010-06-24 12:25:56.51 server    Using 'SSNETLIB.DLL' version '8.0.2039'.
2010-06-24 12:25:56.62 server    SQL server listening on 10.180.0.2: 1433.
2010-06-24 12:25:56.62 server    SQL server listening on 127.0.0.1: 1433.
2010-06-24 12:25:56.62 spid5     Starting up database 'model'.
2010-06-24 12:25:56.64 spid3     Server name is 'MARS'.
2010-06-24 12:25:56.64 spid8     Starting up database 'msdb'.
2010-06-24 12:25:56.64 spid9     Starting up database 'CCM0300'.
2010-06-24 12:25:56.64 spid9     udopen: Operating system error 2(The system cannot find the file specified.) during the creation/opening of physical device C:\Program Files\Microsoft SQL Server\MSSQL\data\CCM0300.mdf.
2010-06-24 12:25:56.64 spid9     FCB::Open failed: Could not open device C:\Program Files\Microsoft SQL Server\MSSQL\data\CCM0300.mdf for virtual device number (VDN) 1.
2010-06-24 12:25:56.64 spid9     Device activation error. The physical file name 'C:\Program Files\Microsoft SQL Server\MSSQL\data\CCM0300.mdf' may be incorrect.
2010-06-24 12:25:56.64 spid9     Device activation error. The physical file name 'C:\Program Files\Microsoft SQL Server\MSSQL\data\CCM0300_log.LDF' may be incorrect.
2010-06-24 12:25:56.65 spid5     Clearing tempdb database.
2010-06-24 12:25:56.69 spid8     Bypassing recovery for database 'msdb' because it is marked SUSPECT.
2010-06-24 12:25:56.76 spid5     Starting up database 'tempdb'.
2010-06-24 12:25:56.78 spid3     Recovery complete.
2010-06-24 12:25:56.78 spid3     SQL global counter collection task is created.
2010-06-24 12:25:58.98 server    SQL server listening on TCP, Shared Memory.
2010-06-24 12:25:58.98 server    SQL Server is ready for client connections
2010-06-24 12:26:29.75 spid51    Starting up database 'CCM0300'.
2010-06-24 12:26:29.98 spid51    Using 'xpstar.dll' version '2000.80.2039' to execute extended stored procedure 'xp_regenumvalues'.

SQL AGENT LOG :

---------------------------

2010-07-01 12:12:45 - ! [298] SQLServer Error: 4060, Cannot open database requested in login 'msdb'. Login fails. [SQLSTATE 42000]
2010-07-01 12:12:45 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start
2010-07-01 12:12:45 - ? [098] SQLServerAgent terminated (normally)

Cisco Employee

Re: Patch in Subscriber 4.2 Failed

You should try running DBLhelper to see the replication status.

HTH

java

If this helps, please rate

www.cisco.com/go/pdihelpdesk

HTH

java

if this helps, please rate

www.cisco.com/go/pdi
Community Member

Re: Patch in Subscriber 4.2 Failed

Hi Java,

Thanks for you answer.

in the DBLHelper status for the subscriber is : SQLSERVERAgent service is not running.

the logs of Sql Agent and Sql server are below.

Regards,

Mohamed

Community Member

Re: Patch in Subscriber 4.2 Failed

The logs for the installation Patch 4.2(3)SR2 :

10:40:32: ********************************************************************************************************
10:40:32: ***********************************                               **************************************
10:40:32: ***********************************         Start of Log          **************************************
10:40:32: ***********************************                               **************************************
10:40:32: ********************************************************************************************************
10:40:32: [Install of Cisco Unified CallManager 4.2(3)sr2]
10:40:32: Installer Version: 3.60.06
10:40:32: Build ID: 0020110
10:40:32: Install Date: 2010-07-02
10:40:32: Install Time: 10:40:32
10:40:32: File Backup Location: C:\esbackout
10:40:32: Patch Backout Command: Add/Remove Programs: Cisco Unified CallManager - 4.2(3)sr2 Uninstall
10:40:32: ********************************************************************************************************
10:40:32: ********************************************************************************************************
10:40:32:

10:40:32: Pre-Install Database Check Started *********************
10:40:33: Subscriber Replication Initialization Begun ****************
10:45:34: Replication Status is All agent-implementing jobs are waiting to start
10:45:34: Subscriber Replication remains in a failed state.  Attempt 0 of 3 Failed.  Will attempt again. ****************
10:45:34: Subscriber Replication Initialization Begun ****************
10:50:36: Replication Status is All agent-implementing jobs are waiting to start
10:50:36: Subscriber Replication remains in a failed state.  Attempt 1 of 3 Failed.  Will attempt again. ****************
10:50:36: Subscriber Replication Initialization Begun ****************
10:55:37: Replication Status is All agent-implementing jobs are waiting to start
10:55:37: Subscriber Replication remains in a failed state.  Attempt 2 of 3 Failed.  Will attempt again. ****************
10:55:37: Subscriber Replication Initialization Begun ****************
11:00:39: Replication Status is All agent-implementing jobs are waiting to start
11:00:39: Subscriber Replication remains in a failed state.  Attempt 3 of 3 Failed.  Will attempt again. ****************
11:00:39: ****************************************************
11:00:39: ****************************************************
11:00:39: Replication Status is All agent-implementing jobs are waiting to start
11:00:39: Replication Initialization Begun ****************
11:00:39: ***********Replication Initialization failed****************

Hall of Fame Super Red

Re: Patch in Subscriber 4.2 Failed

Hi Mohamed,

Using DBLHelper to Reestablish a Broken Cisco CallManager Cluster SQL Subscription

http://www.cisco.com/en/US/customer/products/sw/voicesw/ps556/products_tech_note09186a00801e7ddf.shtml


The file is attached in this thread

https://supportforums.cisco.com/message/1110345#1110345

Cheers!
Rob

Please support CSC Helps Haiti

https://supportforums.cisco.com/docs/DOC-8895

https://supportforums.cisco.com/docs/DOC-8727

Community Member

Re: Patch in Subscriber 4.2 Failed

Hi Rob,

Thanks for your replay.

In the DBLHelper Republish is deactivated, and when i reinitiatiaze there is never things.

In the Subscriber, the sgq agent service can't run.

Regards,

Mohamed

326
Views
0
Helpful
6
Replies
CreatePlease to create content