cancel
Showing results for 
Search instead for 
Did you mean: 

idm dispatcher service failing

Former Member
0 Kudos

Hello all,

We have a service failing on our idm server. This is an application server running idm 7.2 sp8 on Windows 2008 R2. The service failure looks like this.

System Log - Event 7031 - Error - The MxDispatcher_idmap1 service terminated unexpectedly. 

In the logs, at the same time, I see the following:

[17.12.2015 23:17:07-100] - 1 - Could not carry out normal MCSystem log operation: The connection is closed.

[17.12.2015 23:17:07-100] - 1 - Original line:Key:GET_DISPATCHER - SQL Exception: Software caused connection abort: recv failed

[17.12.2015 23:17:07-100] - 1 - Could not carry out normal MCSystem log operation: The connection is closed.

[17.12.2015 23:17:07-100] - 1 - Original line:Raising DIRTY flag due to:Software caused connection abort: recv failed

[17.12.2015 23:17:07-100] - 1 - Could not carry out normal MCSystem log operation: The connection is closed.

[17.12.2015 23:17:07-100] - 1 - Original line:Key:MC_LIST_RUNNING_ENGINES - SQL Exception: Socket closed

[17.12.2015 23:17:07-100] - 1 - Could not carry out normal MCSystem log operation: The connection is closed.

[17.12.2015 23:17:07-100] - 1 - Original line:Exception on thread:IDS_DispThread_JOBEXECUTE _b1-pidmap01:Socket closed

I have looked at the server and see no issues. The OS is good. The SQL server also has no issues. It isn't even busy. Ping times to the SQL server are in the single millisecond range.

Any ideas on why the dispatcher may be failing? It does this once or twice a day.

Thanks,

Paul

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member2987
Active Contributor
0 Kudos

Hey Paul, good to see you here!

Couple of things come to mind...

Check the SQL system. Are there any access issues from the mxmc_rt account? Or any other issues showing on that end? Maybe a big SQL report that bogs down the system?

Have there been any system reboots or service changes?  It's looking like there's a communication failure occurring and I would guess that it's either account or service based.

The other possibility would be to run the dispatcher in test mode? You can find information on that in this blog: . You might get some extra info.

Good luck!

Matt