Scribe IDispatch Error #616
Help! Pierre, our Integration is crashing today. What is going on?
First a bit of irony... Our Area Code is 616.
This looks scary but it's actually easy to fix. These DTS's just need to be restarted. That is it. Scribe has a design behavior where they will fail the DTS if it loses connection to the Databases. Once the DTS fails it stays in that failed state after 3 tries.
But what causes such an error? Most of this time is is a SQL time-out. The SQL box pegs its CPU because of some other issue and Scribe can't connect to either CRM, ScribeInternal, or SL. Or something happens on the network where physical connectivity is lost, or finally a password changes and the DTS's don't get updated with that new info.
Anyway it fails the fix is pretty quick and painless. I just go here and manually run each of the processes. One by one and 99.5% of the time they start right back up.
Pierre is currently rockin' to " Every Time I Think" By: Fred Hammond - on the Free to Worship [Bonus Track] [Bonus DVD] Disc 1 album.
Comments