The culprit here is location Object Id in the Global Location table.
To resolve this issue,
Step 1: Open Enterprise manager-- > SQL server Group-- >Local-- > Databases-- >UnityDb-- >Tables
Step 2: Look for the Global Location Table-- >Return all rows-- > Copy the location Object Id in a notepad file.
Step 3: Look for the Location Table-- >Return all rows-- >Copy the location object Id in a notepad file
Step 4: Compare the Location Object Id from the Global Location and location table
Step 5: In a working scenario the location object Id of the Global location and location table should be similar
Step 6: Copy the location object Id from the location table to the global location table.
Step 7: Restart AvCsMgr
If there is more than 1 entry in the Global Location Table then we have to determine the correct location object Id to be used
Open Cisco Unity Tools Depot-- >Diagnostics Tool-- >Data Link Explorer
Look for the table Cisco Unity parameters-- > Look for the row @system Id
Each Unity Server has it's own unique system ID.
A corresponding Location object Id is also created in Active Directory
Start-- > Run -- >dsa.msc
View-- >Advanced Features
Look for Unity-- >Locations, which contains all the systems Id's prepended with the word "default".
The defaultXXXXXXX (where XXXXXXX-->represents the system ID) represents all the Unity servers that are present in the domain, it even includes the ids of the Unity server that once existed in the domain. The screen below shows a total of 2 Unity servers in the environment.
The highlighted value is the corerct location matching with the system ID.
In the above example there is a just a single Unity server in the domian and still we have two location entries. One of the entry is due to a past Unity install in the domain. The incorrect value needs to be deleted from AD as well as SQL.
Compare the System Id value and the entry in the Active Directory and delete the unknown defualtXXXXXXX from AD.
In the above scenario, default24136896 matches with the system ID of the Unity server and so we need to delete the default293e7cb3 from AD.
An automatic sync should update the database, but incase if the entry doesnot get update follow the steps from 1 to 7 to correct the location object id value
Happy to help
Vidit