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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

CallManger upgrading issue--DC Directory health check failed

Hi everyone,

Now I am upgrading CCM3.3(5) to CCM4.1(3).

I run Upgrade Assisstant4.3(1) on CCMSUB, got the following message:

DC Directory Health Check: Validation failed.

( Please refer to the following message and log file. And CCMPUB validation successfully)

Could anybody see if the upgrading should proceed or not?

Thank you very much. ( please be patient to read the following log file)

got the following message in 'DC Directory Health Check_LOCAL.log' file:

04-13-2007 18:07:18.485:DCDHealthC:INFO:Calling checkDirHealth

04-13-2007 18:07:18.985:DCDHealthC:INFO:checkDirHealth returnes with -2024

04-13-2007 18:07:18.985:DCDHealthC:INFO:checkDirHealth returnes with -2024

04-13-2007 18:07:18.985:DCDHealthC:INFO:Detailed log location C:\dcdsrvr\log\DirUpgradeAsst.log

checked DirUpgradeAsst.log, found the following message:

'" Error occured on reg.exe

Either the PUB is down or unreachable "

..............

04/13/2007 20:19:51.174 DCDChecker.cpp CheckDirHealth Machine is a SUB. Check for existence of passwords in PUB registry.

04/13/2007 20:19:51.236 DCDChecker.cpp checkSpecialUserPassword Starting Password check for CCMAdministrator Users

04/13/2007 20:19:51.236 DCDChecker.cpp checkSpecialUserPassword Querying the PUB registry for CCMAdministrator password C:\utils\SecurityTemplates\reg query "\\CCMPUB\HKLM\Software\Cisco Systems, Inc.\Directory Configuration\AppUsers\CCMAdministrator" /v Password > C:\dcdsrvr\log\UpgradeAssistant.txt

04/13/2007 20:19:51.377 DCDChecker.cpp checkSpecialUserPassword Reg Query for CCMAdministrator done

04/13/2007 20:19:51.393 DCDChecker.cpp checkSpecialUserPassword Searching in the temp file for the CCMAdministrator password

04/13/2007 20:19:51.393 DCDChecker.cpp checkSpecialUserPassword CCMAdministrator password found in temp file

04/13/2007 20:19:51.393 DCDChecker.cpp checkSpecialUserPassword Starting Password check for IPMASysUser Users

04/13/2007 20:19:51.393 DCDChecker.cpp checkSpecialUserPassword Querying the PUB registry for IPMASysUser password C:\utils\SecurityTemplates\reg query "\\CCMPUB\HKLM\Software\Cisco Systems, Inc.\Directory Configuration\AppUsers\IPMASysUser" /v Password > C:\dcdsrvr\log\UpgradeAssistant.txt

04/13/2007 20:19:51.424 DCDChecker.cpp checkSpecialUserPassword Reg Query for IPMASysUser done

04/13/2007 20:19:51.439 DCDChecker.cpp checkSpecialUserPassword Temp file empty. Error occured on reg.exe

04/13/2007 20:19:51.439 DCDChecker.cpp checkSpecialUserPassword Either the PUB is down or unreachable

04/13/2007 20:19:51.455 DCDChecker.cpp checkSpecialUserPassword Exiting...

04/13/2007 20:19:51.455 DCDChecker.cpp checkSpecialUserPassword Starting Password check for CCMSysUser Users

04/13/2007 20:19:51.455 DCDChecker.cpp checkSpecialUserPassword Querying the PUB registry for CCMSysUser password C:\utils\SecurityTemplates\reg query "\\CCMPUB\HKLM\Software\Cisco Systems, Inc.\Directory Configuration\AppUsers\CCMSysUser" /v Password > C:\dcdsrvr\log\UpgradeAssistant.txt

04/13/2007 20:19:51.486 DCDChecker.cpp checkSpecialUserPassword Reg Query for CCMSysUser done

04/13/2007 20:19:51.486 DCDChecker.cpp checkSpecialUserPassword Searching in the temp file for the CCMSysUser password

04/13/2007 20:19:51.486 DCDChecker.cpp checkSpecialUserPassword CCMSysUser password found in temp file

04/13/2007 20:19:51.502 DirLDAPHelper.cpp ~DirLDAPHelper Destructing DirLDAPHelper object..

04/13/2007 20:19:51.502 DirUpgConfig.cpp ~DirUpgConfig Destroying DirUpgConfig

04/13/2007 20:19:51.502 DirUpgConfig.cpp ~DirUpgConfig Unbinding LDAP

04/13/2007 20:19:51.518 DCDChecker.cpp ~DCDChecker DCDChecker Destroyed

04/13/2007 20:19:51.518 DirUpgradeAsst.cpp DllMain DLL_PROCESS_DETACH_____________________________________________________________________________

5 REPLIES
New Member

Re: CallManger upgrading issue--DC Directory health check failed

Does anybody have similar experience?

Thank you for your comment and I would like to share the experience.

Howard

Hall of Fame Super Red

Re: CallManger upgrading issue--DC Directory health check failed

Hi Howard,

You probably fix this error before you continue :) Make sure that the Subscriber servers can see the Publisher before you run the Upgrade Assistant.

This utility identifies problems that could cause the Cisco CallManager upgrade to fail. This utility does not correct the problem(s); you must perform the corrective action for the problem that the utility identifies.

Cisco strongly recommends that all servers in the cluster pass the validation before you upgrade any servers.

DC Directory HealthCheck Validation

This check occurs on the publisher database and subscriber servers.

The utility validates whether Cisco CallManager is integrated with DC Directory. This utility validates the DC Directory connection and the DC Directory configuration containers.

Interpreting the Results

The validation results display in the Upgrade Assistant Summary window. At the top of the window, a report summarizes the results for all modules and displays which modules failed, which modules produced warnings, and which modules passed. A link to the folder that contains all log files, including the Upgrade Assistant Summary report, displays also.

To identify a problem with the failed validation module, review the following information that displays in the Summary window:

The first link points to the log file that specifies the error or warning.

Click the first link and search for the error or warning; for example, ERR: or WARN: .

The second link points to the corrective action file that describes the log file error message and recommends the corrective action.

Click the second link to open the corrective action file. Search the corrective action file for the error message that is noted in the log file. Review the description and corrective action.

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

Caution After you correct all problems that the utility identifies, Cisco strongly recommends that you run the utility again on every server in the cluster before you begin the upgrade.

From this good doc;

http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_installation_guide09186a00803f5c59.html

Hope this helps!

Rob

New Member

Re: CallManger upgrading issue--DC Directory health check failed

I saw a similar issue where cluster was AD integrated and the DCD services were not running on the pub.

New Member

Re: CallManger upgrading issue--DC Directory health check failed

Hello,

Sorry for the delay. I just need to follow up the post-upgrade task.

Please check the updates as follows:

I ignored the error message and continue upgrading.

After CCM-PUB/CCM-SUB finished, CCM work properly and Database replication is fine.

then I rerun the upgrade assistant again,

CCM-PUB no any errors,

CCM-SUB shows

"Database Location Setting Validation: Validation failed."

14/04/2007 23:13:58:dBConn0Chk:INFO: Accessing CCM glassHouse database

14/04/2007 23:13:58:dBConn0Chk:ERR : Database Access Failure

14/04/2007 23:13:59:dBConn0Chk:ERR : CCM Database Settings Conflict

14/04/2007 23:13:59:dBConn0Chk:ERR : Highest CCM Database=ERROR

14/04/2007 23:13:59:dBConn0Chk:ERR : DBConnection0=DSN=CiscoCallManager;

SERVER=CCMPUB;DATABASE=CCM0302;Trusted_Connection=yes

04-14-2007 23:13:59.330:dBConnChck:INFO:dBConn0Chk.exe process completed

04-14-2007 23:13:59.330:dBConnChck: ERR:Cisco Unified CallManager Database Location Setting test failed!

Today I run the upgrade assistant on CCM-SUB again,

" Validation successful !"

I would like to share this experience with you.

Has anybody some comments or similiar experience?

Thanks.

Howard

Hall of Fame Super Red

Re: CallManger upgrading issue--DC Directory health check failed

Hi Howard,

Its good to see that you are moving forward here, great job! My guess is that you were doing these checks with the Sub isolated from the Pub, so this would be expected. Once the 2 boxes could see each other and sync'd up again the Validation was successful.

Rob

159
Views
3
Helpful
5
Replies