locked
Users missing from OCS Address book... RRS feed

  • Question

  • I've been reading and trying things for days and just can not seem to get this working.  Hopefully someone has seen this and knows the answer.

     

    I have a new OCS installation (standard, single server, no edge...internal only).  The client can find many users, both with and withough OCS access in the address book.  It also can find users across all 5 domain in our forest.  However, there are some users that just do not show up.

     

    I've read that in order to be listed a user needs at least one phone number defined and/or have OCS enabled.  I have triple checked that the users I have found missing indeed have a phone number..usually main, cell, and fax.

     

    In order to debug I have deleted all the lsabs and dabs files, run abserver.exe -regenUR, checked the event log to make sure no errors and all 5 domains processed, run abserver.exe -syncNow, saw the new lsabs and dabs created, checked event viewer and saw no errors, go to a client and exit OC, remove the GalContact.db, start OC, see that GalContact.db is recreated, and search again.....users are still missing.

     

    The only error I've been able to find is when I run abserver.exe -validateDB...

    Exception occured while validating database.

    Object reference not set to and instance of and object.

    Exception type:  NullReferenceException

     

    Thanks for any tips or suggestions...

     

    -Andy

     

    PS.  I just went in and used abserver.exe -dumpFile xxxx.lsabs lsabs.txt and took a look at it.  All the users I am trying to see from OC are in the file.  For whatever reason the OC client is NOT seeing them.

     

    Friday, May 2, 2008 5:17 PM

All replies

  • We are having a similar problem except that we have some users with data displayed and some without.  I've done the dumpcontacts command and comparing contacts shows no difference between them.  In addition, mobile numbers are not coming through at all.  It almost seems like the MOC client is looking invalid data.  Is there a way to troubleshoot where MOC is looking?  we have a share <server>\ABS which hosues the lsabs files, but that certainly isn't what MOC looks at from what I can tell.

     

    Friday, May 2, 2008 9:27 PM
  •  

    I am not seeing this issue.  The users I can see seem to have all the information they are supposed to.  In my case it seems that the OC client is downloading the dabs and lsabs properly but then not building the galcontact.db properly.  This could very well be a client issue and not a server issue....Im not sure.

     

    I did discover one interesting thing....if I open the galcontact.db in wordpad and then search for some of the users names that seem to be missing, it finds them!  Yet I type the last name of the same user in OC and get "No results found."  I think the OC client must be broken....or maybe it's operator error, but this just doesn't seem right.

     

    Any ideas?

     

    -Andy

     

    Update:  Found an article that mentions how to dump the galcontact.db to csv.  (Instruction below for anyone that needs it.)  My galcontacts.db file has 1161 contacts in it.  The vast majority show "No results found" in the OC client.  This is VERY frustrating!

     

     

    For anyone that is interested in seeing the contents of their Office Communicator address book you can create the following registry key, relaunch Communicator, then click Tools, and click View Received Files to dump it from Communicator. The resulting file will be called Contacts.csv in \My Documents\My Received Files.

    HKEY_CURRENT_USER\Software\Microsoft\Communicator

    Dword: DumpContactsToCsvFile

    Value= 1

    Note:  Make sure the "My Received Files" directory exists....if not, manually create it.

    Monday, May 5, 2008 5:11 PM
  • We have everything working now.

     

    1. Make sure your normalization rules are normalizing all numbers (Work, Mobile, Other) to E.164.  That means whatever you do, the number needs to be preceeded by +.

     

    For example, this is our norm rule for internal extensions:

     

    Code Snippet

    # 4 digit extentions
    (\d\d\d\d)
    +$1

     

     

    Once that is done, abserver.exe -regenUR and then abserver -syncnow.  You should not see many numbers in the Invalid_AD_Phone_Numbers.txt file.

     

    When you do the export to contacts.csv file in MOC, the URIs should be in the format tel:+5555 (in the case of a four digit phone extension)

     

    Hope this helps.

     

     

    Monday, May 5, 2008 7:15 PM
  • I have normalization turned off since we are not using OCS with any kind of VoIP functionality.  Right now just using for IM and Live Meeting.

     

    I dont believe this will help, but I can turn normalization back on and see if this helps.

     

    Ill let you know.

     

    -Andy

    Monday, May 5, 2008 7:21 PM
  • Unless your phone numbers are stored in AD in E.164 format (+13535551234 or +5555), they need to be normalized to that format or MOC ignores them...

     

    Monday, May 5, 2008 7:54 PM
  •  

    So you are saying that even though I could care less whether or not the phone numbers are usable by MOC and even though the galcontact.db file contains all the contacts, MOC will ignore the contacts?  That doesn't seem right to me.

     

    As for how the numbers are stored....for most of our US based employees its XXX-XXX-XXXX....for Asia and Europe its all kinds of ways.

     

    I wonder if there is a way to tell MOC to show contacts regardless for the format of the phone number?

     

    -Andy

    Monday, May 5, 2008 8:02 PM
  •  

    As far as I can tell, the E.164 requirement is new for MOC 2007.  We ran LCS/MOC 2005 with Cisco Call Manager 5.1 and we never had issues with the phone numbers in XXX-XXX-XXXX format.  I believe the E.164 format is being imposed for Microsoft Enterprise Voice compatibility.  I'm not sure I understand why you want to bring the phone numbers into MOC if they are not "usable" for click to dial.  Are you just interested from a phone directory/data standpoint?  If that is the case, just add the normalization rules and you'll be good to go.

     

    Here's a snip from my company norm file:

     

    Code Snippet

    # 4 digit extentions
    (\d\d\d\d)
    +$1

     

    # Company Internal
    # 111-111-1111, dddd
    (\+\s*1)?\s*\(?(111)\s*\)?[\s()\-\./]*(111)[\s()\-\./]*(1111)\s*[Xx\s\,]\s*(\d*)
    +$5


    # 1-ddd-ddd-dddd
    (\s*1\-)?\s*\(?(\d\d\d)\s*\)?[\s()\-\./]*(\d\d\d)[\s()\-\./]*(\d\d\d\d)[\s]*
    +1$2$3$4

     

     

    Monday, May 5, 2008 8:35 PM
  • More specifically, OC will not display the PHONE NUMBER, but the Contacts themselves still appear.  I'm seeing a bunch of threads about this lately and there seems to be some confusion.  If the contacts themselves are not appearing them something else is in the mix.

     

    Take a peak here for a little background:

    https://blogs.pointbridge.com/Blogs/schertz_jeff/Pages/Post.aspx?_ID=26

     

    Monday, May 5, 2008 8:36 PM
    Moderator
  • What was throwing me off for the longest time is that I didn't have the + in my normalization rules and some Work numbers actually were making it through and MOC was displaying them.  So, based on that, I thought there was something broken rather than misconfigured.  However, once I added + to all my norm rules, the contact numbers populated just like they did in LCS/MOC 2005.  Now, if only Microsoft would provide a reg hack to disable the E.164 requirement.  Then, maybe we could get RNL working!

    Monday, May 5, 2008 8:41 PM
  • In my case, since I don't have any enhanced voice integration need, I am looking for just the ability to use it as a lookup tool.  Now that I discovered how to view the galcontact.db file I can see that the only entires I am able to see are:

     

    1.  Any account I've enabled for OCS.

    2.  Any account defined in my local contacts.

    3.  Pretty much all groups defined in any domain.

     

    Based on what you are saying, I should be able to see everyone but not their phone numbers.  I am not seeing everyone.

     

    As for the data I can see with the ones that do work...The contacts that came from outlook show everything.  The ones that came in because OCS access is approved do not show phone numbers.  Looking at the galcontact.db, this makes sense.....most of the data is missing from the domain synced contacts.

     

    It for sure does not work as I would expect.

     

    BTW...I thought the "Include in devices" option from ABSConfig would do what I want....I added mail thinking that anyone with the mail field defined would then show up.  Doesn't seem to work.

     

    Thanks for the other article....I'm going to read that one carefully and see if it clears some things up.

     

    -Andy

     

     

    Monday, May 5, 2008 8:57 PM
  • Same issue here. I can see I get a lot of errors based on phone numbers. I don't really care as we don't have the VoIP part implemented. The missing users are both enabled and non-enabled for OCS. Please post here if you have made any progress.

    • Proposed as answer by St0kkies Thursday, January 15, 2009 1:25 PM
    Wednesday, June 18, 2008 1:21 PM
  • I opened a case with Microsoft on this.  Basically you will need a valid SIP address or E.164 phone number for each account you want to show up the the OC address book.

     

    Wednesday, June 18, 2008 1:57 PM
  • we are also facing same issue; Did anyone get any solution on this.

    Monday, August 25, 2008 12:33 PM
  •  Are any of you still experiencing the issue? We had similar issues relating to the E.164 format, address book issues, users not displaying etc which are all resolved now.

    Please let me know if you are still having issues
    Thursday, January 15, 2009 1:25 PM
  • Have u tried the phone normalisation rules?
    Thursday, January 15, 2009 1:26 PM