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

SQL replication, CM Subscriber fails to install, DBL hangs on startup

Cant get CM subscriber to be installated properly, database layer monitoring service hangs on startup so cant activate other services, this is CM 3.3 2. I noticed on publisher that under enterprise manager, the name of the server is not there, it just says local system and that might be the problem, any thoughts?

6 REPLIES
Cisco Employee

Re: SQL replication, CM Subscriber fails to install, DBL hangs o

By any chance, in the publisher has the passwords been changed; esp. for user name SQLSvc?

- Muhilan

New Member

Re: SQL replication, CM Subscriber fails to install, DBL hangs o

Yes, I was asked by TAC to change that password when the issue first started, so they gave me an autogenerated password based on the server name and I changed it on all the services, and also under DBL on COM+ apps.

Re: SQL replication, CM Subscriber fails to install, DBL hangs o

When you built the subscriber are you sure you built the LMhosts file (and hosts for good measure) correctly and could ping the publisher by name.

Also did you try and do the install over a routed connection, I've seen this cause problems.

Paul

rjs
New Member

Re: SQL replication, CM Subscriber fails to install, DBL hangs o

Starting with CCM 3.3.2 you should NOT manually change service account passwords. See cut below from Readme of Cisco CallManager 3.3(2) Admin Password Utility. FYI I did not find the app on the CCM I was having issues installing rather I found on a CCM running 3.3.2spC. Only on Pub. Look on your PUB, TAC probably can send or allow special download access if needed.

I have posted parts of the readme, serious caveats to acknowledge and follow:

Important NOTES:

The Cisco CallManager 3.3(2) has been modified to increase the security for the NT Services that comprise the system. Many of the services that were running as Local System in prior releases have been changed to run as Local NT User accounts/services. These accounts are: CCMServiceRW, CCMService, CCMEML, CCMCDR, CCMUser, SQLSVC, and BackAdmin. During installation, by default, an account is created (without “Log on locally” access) and the local NT password is set using a 128-bit encryption algorithm that creates a unique 15-character password for each account within the Cisco CallManager cluster. The passwords generated meet all four classes of the Microsoft complex password rules which state that passwords must contain characters from at least three of the following four classes: at least 6-characters in length that contains English lower-case letters, English upper-case letters, Westernized Arabic Numerals, and Non-alphanumeric ("special characters").

Due to the complexity of the interoperability relationships of the Cisco CallManager, we strongly recommend Administrators/Installers NOT change any CallManager passwords/services manually. If you decide to change these passwords, the Cisco-provided AdminUtility.exe should be used with the following caveats:

o After using the AdminUtility.exe to change passwords from defaults if for any reason you need to ADD or REPLACE a Subscriber system you MUST reset the passwords for all accounts/services back to default system generated ones before attempting the install otherwise the Subscriber installation will fail.

o The local Administrator account passwords must be identical for every Cisco CallManager system within the cluster. Always log on with the local Administrator account to run the AdminUtility.exe utility.

o The AdminUtility.exe is located in the C:\Program Files\Cisco\Bin directory and must be run using the local Administrator account on the Publisher server. It cannot be successfully executed on Subscriber servers.

o The Publisher must be configured using the default DNS name for the system within the Cisco CallManager Administration Server Configuration web page. If the system is configured to use the IP address you will receive the following error message: “You can only execute this utility on the Publisher!” To correct this go to the Cisco CallManager Administration web page, from the menu go to System/Server. Click on the Publisher within the list on the left-hand list. Change the Publisher DNS/IP Address setting from IP Address to DNS name. Click Update. Re-run the AdminUtility.exe utility.

o All systems that constitute the Cisco CallManager cluster should be in a single identical Workgroup, not a Windows NT or Active Directory Domain. AdminUtility.exe is unable to successfully synchronize CallManager passwords/services in a mixed workgroup/domain environment. If this occurs, configure the Subscriber into the same Workgroup as the Publisher and re-run the utility.

o Local Security Account Policies for these accounts cannot not Enforce Password History, Maximum Password Age, Minimum Password Age, and Account Lockout.

rjs
New Member

Re: SQL replication, CM Subscriber fails to install, DBL hangs o

Is that a bad thing? What affect does this have on a Subscriber as long as the password is consistent when building the Subscriber.

Also, what is the default password for sqlSVC account?

-Randall

Cisco Employee

Re: SQL replication, CM Subscriber fails to install, DBL hangs o

Hi

There is no default pass for sqlsvc. It's a password that is being created based on a the computer name.

Ullie

329
Views
0
Helpful
6
Replies
CreatePlease to create content