UCC MAPI contacts list get truncated

Unanswered Question
Aug 9th, 2010

I am running into an issue with UCC/SCC that has been lingering around for quite some time. One of my users has a large number of contacts in Outlook and when those contacts are pulled via MAPI from UCC about half of the records are returned with empty data. I am not personally running into this issue so I'm guessing it could be some formatting inconsistency within the contacts database causing this problem.

Has anybody else seen this problem? I have told the user to clean up their contacts but is there something specific I should be pointing out for cleanup.



I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
shtalukd Mon, 08/09/2010 - 11:01

Hi Cole:

The current UCC versions send one MAPI query requesting all the contacts from Exchange. Some Exchange have settings to limit the number of records to be sent in one query to 250. This is the underlying casue of the bank records you are seeing with the customer with a large number of contacts. There are two workarounds to this issue: a) To change the Exchange settings to return greater than 250 records  -- please see the workaround from MIcrosoft at


and 2) we have this resolved in SCC Adv-Client 2.0 by sending multiple queries. This should be released within a couple of weeks.

I will check to see if the change has been applied to UCC path. If available we could provide a early release version for your customer to verify. Please let me know if you would be interested.



greenturtlesteak Mon, 08/09/2010 - 11:31

Hi Shahryar,

That makes perfect sense.  The user reported to me that when they resort the names in reverse order it pulls the other half of their contacts properly.

I have adjusted the objtMessage value in Exchange 2007 from the default of 250 to 2000. I will let you know if that solves the problem.

We would definitely be interested in seeing a prerelease version of SCC 2.0. How can we go about getting access to that?



greenturtlesteak Tue, 08/10/2010 - 08:49

Just heard back from the end user and making the registry change to Exchange did the trick. All records are being returned correctly.

Thanks for the help, Cisco!