Ccm0301 Call manager Database does not exist on Subscriber Servers

Unanswered Question
Mar 26th, 2009

Tried to reinitialize a pull from the Call Manager 4.2.3SR2 subscriber servers from the Publisher servers in SQL Server Enterprise Manager (the status is Deactivated). But I get an error message. SQL Server replication does not support nicknames, such are "." or "[local]" as server names. The names of the servers have not been changes since inception. All servers are running the same SQL Server ver 2000 SP4 and OS ver 2000.2.7. All servers have valid host and lmhost files. Admin tool password synchronizes but database does not, says database does not exist on both subscriber servers.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Jaime Valencia Thu, 03/26/2009 - 11:10

so, you do have an entry named local or servername in SQL but under that there is no CCM0301 DB?? or you don't have entries in SQL for any server??

if you add an entry for the SUB in the PUB SQL do you see it??



if this helps, please rate

e.giron Thu, 03/26/2009 - 11:15

Yes, there is an entry on all three servers named (local)(Windows NT). But the ccm0301 DB only resides on the Publisher Server but not on the Subscriber servers at all, when I try to add them, it says "connction could not be established to AJC-FCP-CCMSUB, and I don't even see the 2nd Subscriber in the list of SQL server available at all, although it is up and fully functional on the server itself?

Jaime Valencia Thu, 03/26/2009 - 11:19

you don't need to see a server the list in order to add it. you can type the hostname, have you tried it that way?



if this helps, please rate

e.giron Thu, 03/26/2009 - 11:24

Tried adding both subscribers and they both get the same error message - I cannot add it using the SA account username only Windows authentication, but when it does add the Server Group I get the error message: (connection failed, check SQL Server Registration Properties - conncetion timed out).


This Discussion