locked
Address Book Server problem RRS feed

  • Question

  • Hello all,

    please does anyone has idea why this kind of error occures:

    OCSAddressBookServer ID:21045 Description:Address Book Server was unable to perform its heartbeat function against the back-end database after 3 attempts.SQL Connection String: Data Source

     

    We have OCS 2007 environment with 2 consolidated front end server and clustered sql back en servers.

     

    BR,

    Heikki Pesonen

    Monday, June 30, 2008 12:18 PM

All replies

  • Is the SQL backend cluster responding to the OCS Servers?

    Tuesday, July 1, 2008 11:30 AM
  • I too have same problem.
    My backend server is responding to OCS front end server
    Tuesday, June 16, 2009 1:43 PM
  • We had the exact same problem (our back end was clustered and we have four front end servers) in our R1 environment with most of the same error messages - it took me a while, but here's what I figured out:

    As we have worked on the issue, we have determined that when the back end resources fail over, and the resources are not available when the front end responsible for the address book has a heartbeat, then there are problems that the system does not appear to be able to overcome.  We have found that timing is critical.  If an error is thrown by the front end, then the following ordered steps must be accomplished to get the system back:
    1. On a front end server, run the "dbanalyze.exe /report:diag" command from a command prompt - it is an OCS resource kit utility.  The output of the command will identify the front end responsible for the address book server.
    2. Shut down the front end service for the front end identified in step #1.
    3. Give the system several minutes - usually around 5 minutes - to allow it to select another front end server to be responsible for the address book.  Running the "dbanalyze.exe /report:diag" again will confirm that the role has changed.
    4. Once the role has changed, the address book can be regenerated manually or wait until the automatic cycle starts at 1:30am.
      Start the front end service for the front end identified in step #1.

    Note: Just "restarting" the front end service isn't enough - we've never been successful doing this.

    Tuesday, June 16, 2009 3:34 PM
  • Hi,
    this was in our case caused by some load balancing or router misconfig, nobody tell me the exact reason.
    Thanks Sick Freak for your solution, I have recorded it in my notes.

    Cheers,
    Heikki
    "Certified" OCS specialist
    Tuesday, August 25, 2009 11:10 AM