The Address Book Request web service can not be started?

Locked The Address Book Request web service can not be started?

  • Friday, September 11, 2009 9:30 AM
     
     

    Hello,

    We have an installation of OCS 2007 R2 on Windows 2008 Sp1.

    The addressbook never worked since the initial installation, and we always see the following error message in the event log after the server is rebooted.

    ---
    Log Name:      Office Communications Server
    Source:        OCS Address Book and Distribution List Expansion Web Service
    Event ID:      62009
    Task Category: (1024)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Description:
    Address Book Request web service could not be started.

    Exception information : The type initializer for 'System.Management.MTAHelper' threw an exception..
    Cause: Startup errors.
    Resolution:
    Check the events prior to this to resolve the service startup issue.
    ---
    Then we get the following events repeating every five minutes as the Web service tries to restart,
    in order 62014, 62017, 62018, 62019, 62020.

    Event ID:      62014
    Description:
    Failed to initialize Address Book web service setting
    Initialization will be retried in 5 minutes

    Event ID:      62017
    Description:
    Address Book web service settings
    AbWebSvcDbServer: (local)\rtc
    AbWebSvcDbName: rtcab
    AbWebSvcDbEnlist: False
    AbWebSvcDbPooling: True
    AbWebSvcDbMinPoolSize: 0
    AbWebSvcDbMaxPoolSize: 0
    AbWebSvcDbConnectionReset: False
    AbWebSvcDbMaxReturnContacts: 100
    AbWebSvcDbQueryRetryCount: 2
    AbWebSvcDbConnectTimeout: 0
    AbWebSvcDbStatementTimeout: 0
    AbWebSvcQueryAttributeListDelimiters: 0x20 0x2C 0x3B 0x7C 0x9 0xA 0xD
    AbWebSvcHeartbeatTimer: 5
    AbWebSvcQueryByOu: False
    AbWebSvcUserOuPathIdExpirationInMin: 600
    AbWebSvcDbLikeQueryEscapeChar: `

    Event ID:      62018
    Description:
    Address Book web service Active Directory search base GC://<our domain name>.local

    Event ID:      62019
    Description:
    Address Book web service backend connection string Data Source=(local)\rtc;Initial Catalog=rtcab;Integrated Security=True;Enlist=False;Connection Reset=False

    Event ID:      62020
    Description:
    Address Book web service backend data partition = -1


    We have checked permissions of the RTCComponentService account.
    The .NET framework version is 3.5 sp1.
    We have compared WMI settings with a working installation and it all seems to be correct.
    We can download the ABS files manually via a webbrowser, and that works fine.

     

All Replies

  • Friday, September 11, 2009 12:15 PM
    Moderator
     
     
    Take a look at the latter half of this article to validate that your RTCCompnonetService account is correctly configured on the LsGroupExpAppPool in IIS:
    http://blogs.pointbridge.com/Blogs/schertz_jeff/Pages/Post.aspx?_ID=66

    You also may want to verify that the Scalable Network Pack is disabled on your servers: http://support.microsoft.com/kb/948496
    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
  • Friday, September 11, 2009 12:45 PM
     
     
    Hi Jeff,

    Thanks for your quick reply.
    The RTCCompnonetService account is correctly configured in the LsGroupExpAppPool, and we are not getting any messages around "access denied" or "account lockout" etc.

    About the Scalable Network Pack, we are running windows 2008 and as far as we know the default settings have not been changed. However, this SNP is somewhat confusing so here is the printout from netsh int tcp show global:

    TCP Global Parameters

    ----------------------------------------------

    Receive-Side Scaling State          : enabled

    Chimney Offload State               : disabled

    Receive Window Auto-Tuning Level    : normal

    Add-On Congestion Control Provider  : ctcp

    ECN Capability                      : disabled

    RFC 1323 Timestamps                 : disabled

    Should we change any setting?

  • Friday, September 11, 2009 3:28 PM
     
     

    Hi again,

    On this installation, when running abserver.exe -validatedb we are getting the messages below:

    Exception occurred while validating database.
    Object reference not set to an instance of an object.
    Exception type: NullReferenceException

    So it seems the rtc database has some junk in it or is corrupt in some way.
    How can we continue troubleshooting it? (dbanalyze does not seem to do to much)
    Is there a way of deleting / recreating / reloading the rtc database?

    Another thing that concerns me in this installation is the occurence of non-english
    characters such as norwegian Æ, Ø, and Å...

  • Monday, October 12, 2009 6:27 PM
     
     
    Did you get an answer to this?
  • Monday, October 12, 2009 8:03 PM
     
     Proposed Answer

    My team had the same problem, and we updated a SQL Database content, to remove this error. W ehave notified the OCS Product Group on this.

    I guess you need to wait untill the next set of updates come

    • Proposed As Answer by Sri Todi Monday, October 12, 2009 8:03 PM
    •  
  • Monday, October 19, 2009 9:33 AM
     
     

    Hello Rocky,

    No, we still see the same problem (or atleast the same messages in the event viewer), and we have also escalated the issue to Microsoft.

    /mk

  • Tuesday, October 20, 2009 3:19 PM
     
     
    I was able to get past the exception error below when I ran abserver -validatedb:

    Exception occurred while validating database.
    Object reference not set to an instance of an object.
    Exception type: NullReferenceException

    I installed both of these hotfixes below from July 09.

    http://support.microsoft.com/kb/969834/

    and

    http://support.microsoft.com/kb/969821/

    Hope that works for you.

    -Dave

  • Friday, October 23, 2009 12:07 AM
     
     
    Please note if you have the following in your event logs

    Event ID:      62020
    Description:
    Address Book web service backend data partition = -1

    Then the next set of updates by Microsoft  (Nov'09) should solve the problem.