Scribe Error – Error initializing the Message Processor – Initialize failed (MsgProcDoc is null)

Our Scribe Insight 7 server abruptly stopped running integration tasks, a few days back. We decided to restart the services, however, the Scribe Monitor Service wouldn’t restart. We checked all configuration, and verified that no changes had been made. The services were running under a domain account, and that account was added to the Scribe Console Users local group as well as to the local Administrators group.

We were getting multiple errors in the event log –

1. An Alert has been added to the alert log:
   System Critical Error
   Error initializing the Message Processor – Initialize failed (MsgProcDoc is null)
2. An Alert has been added to the alert log:
   System Critical Error
   Error creating the Message Processor – Server execution failed
   (Error code=80080005)
3. Faulting application MessageProcessor.exe, version 7.0.0.15071, time stamp 0x4c219e78, faulting module MSVCR90.dll, version 9.0.30729.1, time stamp 0x488ef6c5, exception code 0x40000015, fault offset 0x0005bb47, process id 0x1bd4, application start time 0x01cb2ec483cc60e0.

Fortunately, we came across this post in the Scribe OpenMind forums – Error(s) trying to run DTS in Scribe Console – Error initializing the Message Processor.

For some reason, the Scribe Monitor Service tries to connect to the Internet on startup, and since we were running behind a proxy, and the service account did not have permissions to use the proxy, the service was refusing to start. Once, we turned off the setting (IE => Tools => Internet Options => Advanced tab => Security => Check for publisher’s certificate revocation) for the service account (by logging into the server using the service account), everything started working as expected.

Why does Scribe need to connect to Internet? This remains a mystery as of now…