TMS: Could not sync phonebook source with id 2 and name Provisioning Source

Unanswered Question
Feb 7th, 2012

Hi, I keep on getting below failure messeges. I'm new to TMS. what does below messeges mean and how do I resolve it?

Failure Reason:  

Communication error. Could not sync phonebook source with id 2 and name Provisioning Source. 

Event log

1/28/2010 6:53 AM - Event Created

11/21/2011 2:46 PM - Event executed by MYTMS1

11/21/2011 2:46 PM - Phonebook source Provisioning Source synchronizing

11/21/2011 2:47 PM - Event Postponed to 2009-02-05 17:23:47

11/21/2011 2:47 PM - Communication error. Could not sync phonebook source with id 2 and name Provisioning Source.

11/21/2011 2:47 PM - The event failed to complete. Details: Communication error. Could not sync phonebook source with id 2 and name Provisioning Source.

11/21/2011 5:24 PM - Event executed by MYTMS1

11/21/2011 5:24 PM - Phonebook source Provisioning Source synchronizing

11/21/2011 5:24 PM - Communication error. Could not sync phonebook source with id 2 and name Provisioning Source.

11/21/2011 5:24 PM - The event failed to complete. Details: Communication error. Could not sync phonebook source with id 2 and name Provisioning Source.

11/22/2011 5:24 PM - Event executed by MYTMS1

11/22/2011 5:24 PM - Phonebook source Provisioning Source synchronizing

11/22/2011 5:24 PM - Communication error. Could not sync phonebook source with id 2 and name Provisioning Source.

11/22/2011 5:24 PM - The event failed to complete. Details: Communication error. Could not sync phonebook source with id 2 and name Provisioning Source.

11/23/2011 5:24 PM - Event executed by MYTMS1

11/23/2011 5:24 PM - Phonebook source Provisioning Source synchronizing

11/23/2011 5:24 PM - Communication error. Could not sync phonebook source with id 2 and name Provisioning Source.

11/23/2011 5:24 PM - The event failed to complete. Details: Communication error. Could not sync phonebook source with id 2 and name Provisioning Source.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 0 (0 ratings)
Magnus Ohm Tue, 02/07/2012 - 21:25

Hi it can likely be something wrong with one or more users in the opends datadase.

I have seen a similar issue before but in order to confirm that it's related I would need to see the log-tmsagent after an attempted sync.

I recommend a tac case on this one.

Sent from Cisco Technical Support iPhone App

Magnus Ohm Wed, 02/08/2012 - 22:58

Hi Gavin

Did you raise a case on this? Is it resolved? What is the SR number?

/magnus

Sent from Cisco Technical Support iPhone App

ib67076 Sun, 02/12/2012 - 23:14

im also seeing this error message pop up daily.

when i dig deeper, under

phonebook - manage phonebook sources - configuration - click test connection, the following error message appears:

"Unable to connect to the source: Could not connect to TMS Agent REST Service. => Unable to connect to the remote server"

phonebook - manage phonebook sources - configuration - view contacts, the following message appears:

"Unable to communicate with the TMS agent. See log (log-web.txt) for details."

when i go to log-web.txt it basically repeats the first message above.

ive just started building the tms server so (& also new to tms) i have a feeling it is something i havent enabled somewhere.

any ideas??

Magnus Ohm Sun, 02/12/2012 - 23:46

Hi

Have you enabled TMSAgent under Administrative tools --> General settings?

/Magnus

gavinhan07 Sun, 06/10/2012 - 16:30

I eventually found that the endpoint was down that's why TMS wasn't able sync up the phone book. TMS does phone book sync every 24 hrs.

Sent from Cisco Technical Support iPad App

Actions

Login or Register to take actions

This Discussion

Posted February 7, 2012 at 6:41 PM
Stats:
Replies:5 Avg. Rating:
Views:1409 Votes:0
Shares:0
Tags: No tags.

Discussions Leaderboard