The error message 9601000 pops up when Application server is idle. When there are jobs for it to process, it seems to work fine, but if there's nothing to do, the error message pops up, and if a new job pops into the queue, the 'ok' has to be clicked on the error message before it will process it.
I would appreciate any help resolving this.
Actually, the Application Server process itself is called 9601000, so it's likely that this isn't an error code.
I have to ask you a few questions to understand the problem:
The Application Server talks with Outlook to read and send messages. Since the actual jobs seems to work, maybe is the messaging part that's messed up. This may be Outlook itself or a protection software that pops a warning like "This 9601000 fellow is messing up with me, are you ok with that?".
I am experiencing the same problem as Dan.
The process itself 9601000 is stopping and just says 9601000 has stopped working. You have to close the process and reopen the application server process. It will then run and email any requests sitting in the queue but pops up that error once it is idle for a while (nothing in queue).
We are running SL 2015 cu1
Outlook is not popping up the message, we are running office 365
There is nothing in the application server log or the event history.
I do find this error in Windows Log - Application
faulting module path - C:\Windows\Microsoft.net\Framework\V4.0.30319\clr.dll
Did anyone ever come up with a resolution for this? Experiencing the same issue with SL 2015 CU2 on a Win 10 PC, running Outlook 2016.
9601000 - The operation failed.
Still don't have a resolution for this, other than to get by with using PTFB Pro to click the OK button every time this message comes up....
I have a client also experiencing this same issue. Would love a resolution to this.
Business Applications communities