installing ciscocm.4-1-3-sr2 error message .

Unanswered Question
Mar 20th, 2007
User Badges:

dear sir,

Current environment have 1 publisher ccm 4.1(3)sr2 and 1 subscriber ccm 4.1(3)sr2. We try to install sr2 in new scrubscirber ccm 4.1(3) but got the error messsage "DBAccess Failure" , "Attempt to access database has failed. Collect c:\install\dbinstall\dbinstall00x.txt for diagnosis. picture as attached.

The new ccm have attached to the selected group in ccm group yet.

please advise.


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Rob Huffman Tue, 03/20/2007 - 09:51
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Charles,

If I understand you correctly this new Subscriber build is not yet connected to the Publisher. This is where the problem lies (not being able to see the Pub database);

The publisher database server functions as the master database for all servers in the cluster. All servers except the publishing database server maintain subscriber databases, which are copies of the publisher database server. If you are configuring a subscriber database server, make sure that the server that you are installing can connect to the publishing database server, so the installation can continue. The installation process necessitates this connection, so the publisher database server can be copied to the local drive on the subscriber server. To make sure a good connection exists between the servers, issue a ping command from the subscriber server to the publisher database server before you try to authenticate to it. In the status of the ping command, verify that the IP address displayed is the IP address of the publisher database server. If the ping command is not successful, you can also try to access the publisher database server from all subscriber servers by choosing Start > Run, entering \\\C$, and then by clicking OK. You do not need to enter a user name and password. Mapping to the drive without entering a user name and password ensures that the passwords on the publisher and subscriber servers match. If the subscriber database server cannot access the publisher server, you must exit the installation program, fix the problem, and begin the installation process again on the subscriber server.

From this good doc;

Also, have a look at this recent thread that details this Subscriber addition (Great answers from Gonz,Shanky, Mike,Johnny and Eric);

Hope this helps!


p-kitaka Wed, 03/21/2007 - 04:52
User Badges:

i had a similar issue.. activate services on the new subscriber then apply sr2


This Discussion