We’ve had some longstanding issues with the multi-company process silently ceasing processing and we typically don’t find out until a user goes to update something and we have to restart it. Something that we’ve never been able to pin down a cause and have lived with for the past two years just restarting it once a week or two.
Recently we’ve upgraded to 10.2.300. The release notes say they’ve fixed a bug where it stops processing. What’s happening now is that it’s showing up as failed in the system monitor after running for exactly 9 hours, the same as the timeout in our web.config, with a timeout exceeded message. Even more strange is that even though it’s not showing as active anymore it’s still processing records. Best guess is that it’s still running on the AppPool but now we’ve lost visibility to the running process.
Has anyone run into this before or any ideas what could be causing this strange behavior?