none
Fatal error 823 occurred URGENT

    Question

  • Today we had a power outage when every thing backed none of host instances in our test environmrnt started and we noticed that MsgBoxDB is not accessible(database not showing (+) sign in object exploer in SQL server studio. We deatched and attched the databse and all hosts started running but the vent log statred logging this error

    nable to log message "A message was received of type http..." to the event log due to exception:

    Event Type: Error
    Event Source: BizTalk Accelerator for HL7
    Event Category: None
    Event ID: 8706
    Date:  12/22/2011
    Time:  3:25:16 PM
    User:  N/A
    Computer: BHSETBTSTST.MHBHSET.LOCAL
    Description:
    Unable to log message "A message was received of type http..." to the event log due to exception:
    "Warning: Fatal error 823 occurred at Dec 22 2011  3:25PM. Note the error and time, and contact your system administrator.".

    Username: MHBHSET\BTServiceHostTest
    Time: 12/22/2011 3:25:16 PM


    Why thi si happening any idea?

     


    Mavelikara
    Thursday, December 22, 2011 9:39 PM

Answers

  • Hi Mavelikara,

    The most possible reason for your error might be 

     

    1. The linked server database is stopped.

    2. The linked server database is occupied with other stuff (reindexing, backup).

    3. The linked server is down (power off).

    4. The linked server is busy with other stuff (defragmenting).

    5. A cable to the linked server is dropped (replug all cables).

    6. A router/switch/hub is faulty or not working.

    7. Too much data is passed on the network.

    Also Check this some tips for a Biztalk catastrophic event

     


    Don't forget to mark the post as answer or vote as helpful if it does, Regards - Rajasekhar.R
    Friday, December 23, 2011 5:03 AM
  • There is one more type of an error.

    If for some reason your registry was restored, this error could be shown up.

    When BizTalk service creates  a first event it should create an Event source. But the permission shouldn't be enough.
    The top-level key you want is
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog

    Only Administrators and LocalSystem have write access there by default.

    You could give write permission to that key for a BizTalk Service account.

     


    Leonid Ganeline [BizTalk MVP] BizTalk: Sample: Context Routing and Throttling with orchestration
    Friday, December 23, 2011 6:08 PM
    Moderator

All replies

  • Hi Mavelikara,

    The most possible reason for your error might be 

     

    1. The linked server database is stopped.

    2. The linked server database is occupied with other stuff (reindexing, backup).

    3. The linked server is down (power off).

    4. The linked server is busy with other stuff (defragmenting).

    5. A cable to the linked server is dropped (replug all cables).

    6. A router/switch/hub is faulty or not working.

    7. Too much data is passed on the network.

    Also Check this some tips for a Biztalk catastrophic event

     


    Don't forget to mark the post as answer or vote as helpful if it does, Regards - Rajasekhar.R
    Friday, December 23, 2011 5:03 AM
  • There is one more type of an error.

    If for some reason your registry was restored, this error could be shown up.

    When BizTalk service creates  a first event it should create an Event source. But the permission shouldn't be enough.
    The top-level key you want is
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog

    Only Administrators and LocalSystem have write access there by default.

    You could give write permission to that key for a BizTalk Service account.

     


    Leonid Ganeline [BizTalk MVP] BizTalk: Sample: Context Routing and Throttling with orchestration
    Friday, December 23, 2011 6:08 PM
    Moderator