IdB service crashing when running imports from remote FIM server
Carol Wapshere 10 years ago • updated by anonymous 7 years ago • 4
Everything working fine until today. Last major change was on the 25/09/2012 when the WofG->Health connection was introduced.
Today since lunchtime the IdB service keeps crashing.
In the System Event log:
Log Name: System Source: Service Control Manager Date: 3/10/2012 12:17:12 PM Event ID: 7034 Task Category: None Level: Error Keywords: Classic User: N/A Computer: PRDAPP119VS.act.gov.au Description: The UNIFY Identity Broker v3.0.6 service service terminated unexpectedly. It has done this 1 time(s).
In the Application Event log at the same time:
Log Name: Application Source: Microsoft-Windows-MSDTC Client 2 Date: 3/10/2012 12:17:12 PM Event ID: 4879 Task Category: CM Level: Warning Keywords: Classic User: N/A Computer: PRDAPP119VS.act.gov.au Description: MSDTC encountered an error (HR=0x80000171) while attempting to establish a secure connection with system PRDAPP119VS.
The server it is failing to establish a secure connection with is in fact itself.
There have been no further MSDTC errors but IdB no longer works. I can start the service but as soon as I try to run an Import from the WofG FIM server IdB on the Health server crashes immediately with the same error in the System event log.
Restarting the DTC service does not help.
Customer support service by UserEcho
Can you please attach a screenshot for the MSDTC properties security tab?
Also, I found a few things online, http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/eb8835d9-5f5b-4df2-8c68-4a61d5e44d6b, suggests that the permissions might be wrong for the account configured to run MSDTC, as well as the permissions to the log file (further down in the post).
The customer also found that information however it was not the cause - it turns out that warning has been happening every time the DTC service restarts.
The problem was lack of diskspace on the logs drive where IdB is writing it's logs. Is there something better I should be doing to ensure IdB fails more gracefully or writes something into the Event Viewer if it can't write to its log file?
This is all I have as the logging config:
You may consider adding another type of log writer, such as one of the Windows event log writers. Bob is quite fond of using the IDB307:Windows Custom Event Log configuration, as it uses a custom event log name.
v4.0 of Identity Broker has improved logging components that protect the product should logging fail. It will then log to the Windows event log the error that occurred whilst logging (also protecting the product should that also fail).
Reopened to log time.