Jun.10

Scribe Insights Error – Message Processor is unresponsive

I’ve been working on a project where I’ve been using the Scribe Insights tool to move data from a SQL Server database to a Dynamics CRM Online instance. I needed to run this integration each week day so I configured the Scribe Console/Server to manage the integration. I have over 20 different “jobs” (*.dts files) so the process takes well over an hour to run. At first the integration ran well with no major errors.

However, the integration began to fail and when I checked, I found that the error was “The job was terminated because the Message Processor is unresponsive.” As is typical with me, I try to find a solution on my own. So I took to the interwebs and found two primary solutions.

The first solution was to adjust a timeout limit stored in Windows registry. The second solution was to adjust a timeout limit in the Scribe Internal database. I tried both of these but it didn’t help.

I finally contacted Scribe directly (you can’t post on their forum unless they grant you an account) and received a better answer. It turns out that the approach outlined above was on the right track but was not complete. So as of June 2016, you’ll need to follow the below instructions.


If you are using Scribe Insights (this doesn’t pertain to Scribe Online), version 7.6.2 or later, you’ll need to adjust or add two settings to the Scribe Internal database.

--Timeout Registry Settings
If exists (Select Top 1 * From [SCRIBEINTERNAL].[SCRIBE].[KSYNC] Where Section = 'EVENTMANAGER' And KeyName = 'SETTINGS.PROCHANGTIMEOUT') 
 Update [SCRIBEINTERNAL].[SCRIBE].[KSYNC] Set KeyValue = '180' Where Section = 'EVENTMANAGER' And KeyName = 'SETTINGS.PROCHANGTIMEOUT'
Else
 Insert Into [SCRIBEINTERNAL].[SCRIBE].[KSYNC] Values('EVENTMANAGER','SETTINGS.PROCHANGTIMEOUT','180');

--Memory Registry Settings
-- MAXMEMORYUSAGEMS 
-- For Queue Integration Memory Issues

If exists (Select Top 1 * From [SCRIBEINTERNAL].[SCRIBE].[KSYNC] Where Section = 'MESSAGEPROCESSOR' And KeyName = 'SETTINGS.MAXMEMORYUSAGEMS') 
 Update [SCRIBEINTERNAL].[SCRIBE].[KSYNC] Set KeyValue = '600' Where Section = 'MESSAGEPROCESSOR' And KeyName = 'SETTINGS.MAXMEMORYUSAGEMS'
Else
 Insert Into [SCRIBEINTERNAL].[SCRIBE].[KSYNC] Values('MESSAGEPROCESSOR','SETTINGS.MAXMEMORYUSAGEMS','600');


-- MAXMEMORYUSAGEEM --
-- For File, Timed & Query Integration Memory Issues

If exists (Select Top 1 * From [SCRIBEINTERNAL].[SCRIBE].[KSYNC] Where Section = 'MESSAGEPROCESSOR' And KeyName = 'SETTINGS.MAXMEMORYUSAGEEM') 
 Update [SCRIBEINTERNAL].[SCRIBE].[KSYNC] Set KeyValue = '600' Where Section = 'MESSAGEPROCESSOR' And KeyName = 'SETTINGS.MAXMEMORYUSAGEEM'
Else
 Insert Into [SCRIBEINTERNAL].[SCRIBE].[KSYNC] Values('MESSAGEPROCESSOR','SETTINGS.MAXMEMORYUSAGEEM','600'); 


If you’re using a version of Scribe Insights older than version 7.6.2, you’ll need to edit the Windows registry on the host server.

Registry Locations: 
32-bit     
HKEY_LOCAL_MACHINE\SOFTWARE\Scribe\EventManager\Settings 

64-bit     
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Scribe\EventManager\Settings

 

Creating the registry entries (the value below is just a starting point and may need to be increased):

  • Right-click on the Settings folder, on the shortcut menu, point to New and then click DWORD Value.
  • Name the new value ProcHangTimeout. Right-click on the new value, on the shortcut menu, click Modify.
  • In the Edit DWORD Value dialog box, in the Value data box, type 180. This is the amount of time, in seconds, to wait before terminating the process.
  • In the Base box, choose the Decimal.

Restart the Scribe services for this setting to take effect. This value may need to be increased depending on your environment.

 

Update: June 2016

I can confirm that after running the Scribe Integration for several days with the settings above, I’ve not had a problem with the Message Processor becoming unresponsive.

Dynamics CRM,Scribe Insights