Managing Scribe Timeouts
Scribe Insight DTS packages, which are the integration mappings and instructions component of a Scribe integration, may be scheduled and managed through a tool called the Scribe Console.
The tool presents categories of information in a tree on the left side and list views on the right. The list views within the Collaborations - Integrations area of that tool provides an overview and general status of the scheduled integrations. Occassionally, the status might give you something other than the designed Paused or Active status. When the status is Failed, the desciption column will give you some information on the reason.
I recently encoutered an error I hadn't seen before that I couldn't readily find the answer for:
"The Job was terminated because the message processor is unresponsive."
After some research it was discovered that there is a 60 second timeout built into Scribe that is applied to the time the source query is initially executed and the time that the first row is processed into the target. There are a variety of reasons for why this might happen (server latency, network latency, etc...). While you are trying to determine the cause for the latency, there is a registry entry you can create that will allow for a manual override of the standard timeout.
The key named ProcHangTimeOut needs to be created in the HKEY_LOCAL_MACHINE\SOFTWARE\Scribe\EventManager\Settings key. This represents the timeout in seconds. Set this to what makes sense for you.
Remember that messing around in the registry is inherently dangerous if you don't know what you are doing, so be careful not to disturb anything else when working in the registry.