locked
WMI error RRS feed

  • Question

  • Colleagues I have collided with a following situation at adjustment Phone normalization Rule

    I do all as it is written here

    <http://www.microsoft.com/technet/prodtechnol/office/livecomm/library/abs/lcsabs_7.mspx>

    And at input of parameter MSFT_SIPAddressBookSettings

     

    The mistake gets out

    Number: 0x80041002
    Facility: WMI
    Description: Not found

     

    OS - w2k3 sp2

    sql 2005 sp2

    OCS 2007 RC

    Saturday, June 9, 2007 10:54 AM

Answers

  • Hello,

     

    To begin addrerssing your issue I wanted to confirm that I am heading in the right direction for your issue. Here is an excerpt from the link that you have posted and I feel this is the topic that you are referring to:

     

    Address Book Service Phone Normalization

    Phone numbers that are stored in disparate directories are essentially unstructured strings that lack a strict model for consistency. Communicator requires standardized E.164 phone numbers. This number translation is performed by the Address Book Service in conjunction with mapping rules. These rules are stored in the Generic_Phone_Number_Normalization_Rules.txt text file that is stored in the same directory as the ABServer.exe executable (by default <drive>:\Program Files\Microsoft LC 2005\Address Book Service). If the UseNormalizationRules WMI flag is set to TRUE, the rules are applied to those Active Directory attributes with 0x2000 bit set in the Flags column value. If the 0x1000 bit is set in the Flags column value, then the associated Active Directory attribute value is always normalized.

    Two files are used by Address Book Service to normalize phone numbers:

    Generic_Phone_Number_Normalization_Rules.txt is a read-only file and should not be changed.

    Sample_Company_Phone_Number_Normalization_Rules.txt is the sample file in which you configure rules specific to your company requirements. To use this file, copy it to Company_Phone_Number_Normalization_Rules.txt; otherwise, Address Book Service will use only the generic rules configured in Generic_Phone_Number_Rules_Normalization.txt.

     

     

    To update / access the UseNormalizationRules attribute for OCS 2007 Addressbook Service use the following steps

     

    1. From the desktop on the OCS 2007 server got to Start / Run and enter wbemtest and click on OK

     

    2. Choose the connect button and enter root\cimv2 in the namespace box. Choose connect again

     

    3. Click on Enum Classes, choose recusuive and click on OK

     

    4. Scroll down the list and locate MSFT_SIPAddressbookSetting / double click on this selection

     

    5. Now scroll the list of Properties for MSFT_SIPAddressbookSetting  and find UseNormalizationRules and select it. Make the edit that you want and chosse Save Property / Close / Close /Exit

     

    Thanks

     

     

    Monday, June 25, 2007 8:23 PM

All replies

  • Hello,

     

    To begin addrerssing your issue I wanted to confirm that I am heading in the right direction for your issue. Here is an excerpt from the link that you have posted and I feel this is the topic that you are referring to:

     

    Address Book Service Phone Normalization

    Phone numbers that are stored in disparate directories are essentially unstructured strings that lack a strict model for consistency. Communicator requires standardized E.164 phone numbers. This number translation is performed by the Address Book Service in conjunction with mapping rules. These rules are stored in the Generic_Phone_Number_Normalization_Rules.txt text file that is stored in the same directory as the ABServer.exe executable (by default <drive>:\Program Files\Microsoft LC 2005\Address Book Service). If the UseNormalizationRules WMI flag is set to TRUE, the rules are applied to those Active Directory attributes with 0x2000 bit set in the Flags column value. If the 0x1000 bit is set in the Flags column value, then the associated Active Directory attribute value is always normalized.

    Two files are used by Address Book Service to normalize phone numbers:

    Generic_Phone_Number_Normalization_Rules.txt is a read-only file and should not be changed.

    Sample_Company_Phone_Number_Normalization_Rules.txt is the sample file in which you configure rules specific to your company requirements. To use this file, copy it to Company_Phone_Number_Normalization_Rules.txt; otherwise, Address Book Service will use only the generic rules configured in Generic_Phone_Number_Rules_Normalization.txt.

     

     

    To update / access the UseNormalizationRules attribute for OCS 2007 Addressbook Service use the following steps

     

    1. From the desktop on the OCS 2007 server got to Start / Run and enter wbemtest and click on OK

     

    2. Choose the connect button and enter root\cimv2 in the namespace box. Choose connect again

     

    3. Click on Enum Classes, choose recusuive and click on OK

     

    4. Scroll down the list and locate MSFT_SIPAddressbookSetting / double click on this selection

     

    5. Now scroll the list of Properties for MSFT_SIPAddressbookSetting  and find UseNormalizationRules and select it. Make the edit that you want and chosse Save Property / Close / Close /Exit

     

    Thanks

     

     

    Monday, June 25, 2007 8:23 PM
  • Hi Lawash,

    Can you let us know the status of your issue? Was Mike's suggestion able to help?

    Wednesday, June 27, 2007 8:24 PM
  • Many thanks for the help. With mistake WMI I have understood.

    In parameter MSFT_SIPAddressbookSet.... ---> UseNonrmalizationRules

    Has exposed value 0x2000

    Now after I have changed parameter according to the documentation at start of a command

    abserver/syncnow there are following mistakes. The truth these mistakes were and earlier at start of this command.

     

     

    Event Type: Warning
    Event Source: OCS Address Book Server
    Event Category: (1008)
    Event ID: 21012
    Date: 04.07.2007
    Time: 11:51:28
    User: N/A
    Computer: SERVER-OCS
    Description:
    A delta file would be too large in relation to the full file it is based on.  The delta file will not be generated.

    Path: \\server-ocs\adrbook\D-092a-0947.lsabs
    Full File Records:  4
    Delta File Records: 3
    Cause: A delta file is generated in memory.  If the number of new/updated contacts plus the number of deleted contacts is greater than a configured percentage of the number of contacts in the base file, the delta file is not generated because it would be quicker for the client to just download the full file.
    Resolution:
    None needed.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


    Event Type: Warning
    Event Source: OCS Address Book Server
    Event Category: (1008)
    Event ID: 21012
    Date: 04.07.2007
    Time: 11:51:28
    User: N/A
    Computer: SERVER-OCS
    Description:
    A delta file would be too large in relation to the full file it is based on.  The delta file will not be generated.

    Path: \\server-ocs\adrbook\D-092b-0947.lsabs
    Full File Records:  4
    Delta File Records: 3
    Cause: A delta file is generated in memory.  If the number of new/updated contacts plus the number of deleted contacts is greater than a configured percentage of the number of contacts in the base file, the delta file is not generated because it would be quicker for the client to just download the full file.
    Resolution:
    None needed.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Warning
    Event Source: OCS Address Book Server
    Event Category: (1008)
    Event ID: 21012
    Date: 04.07.2007
    Time: 11:51:28
    User: N/A
    Computer: SERVER-OCS
    Description:
    A delta file would be too large in relation to the full file it is based on.  The delta file will not be generated.

    Path: \\server-ocs\adrbook\D-092d-0947.lsabs
    Full File Records:  4
    Delta File Records: 3
    Cause: A delta file is generated in memory.  If the number of new/updated contacts plus the number of deleted contacts is greater than a configured percentage of the number of contacts in the base file, the delta file is not generated because it would be quicker for the client to just download the full file.
    Resolution:
    None needed.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


    Event Type: Warning
    Event Source: OCS Address Book Server
    Event Category: (1008)
    Event ID: 21034
    Date: 04.07.2007
    Time: 11:51:28
    User: N/A
    Computer: SERVER-OCS
    Description:
    One or more phone numbers failed to normalize.

    3 total numbers failed to normalize.  They are listed in the text file: '\\server-ocs\adrbook\\Invalid_AD_Phone_Numbers.txt'
    Cause: One or more phone number attributes in Active Directory contained text that could not be normalized.  Normalization rules are contained in the optional Company_Phone_Number_Normalization_Rules.txt file located in the output location or in the generic rules built into Address Book Server.  Refer to the documentation for a description of the built-in generic normalization rules.  Use the ABServer -dumpRules command to see all the rules that Address Book Server is currently configured with.
    Resolution:
    Either create a Company_Phone_Number_Normalization_Rules.txt file in the output location and make sure it covers all cases found in your Active Directory deployment or fix the invalid phone number(s) in the Active Directory record(s).

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


    Invalid_AD_Phone_Numbers.txt

    Unmatched number: User: 'eec1d0a7-f465-43a2-9477-59024ac2decf'  AD Attribute: 'homePhone'  Number: '2002'
    Unmatched number: User: '290f66f4-1da6-449c-9c45-6681fc914f79'  AD Attribute: 'homePhone'  Number: '2000'
    Unmatched number: User: 'f16a534d-c9fc-47b2-a8a8-85a1fce20626'  AD Attribute: 'homePhone'  Number: '2001'

     

    Thursday, July 5, 2007 10:16 AM