Queue Based Integrations Stop Processing

[Steve Platz]

Hi everyone,

I'm running Scribe Insight 7.9.3.58357 and have an issue with queue-based integrations. In a nutshell, for most of the week, the integrations will work fine. A message will hit the queue, the message processor will see it, pick it up, and then process it. However, occassionally, the message processor will quit processing messages. This happens at least once per week and usually over the weekend (although it happened yesterday - a Thursday). To fix the issue, all I need to do is to log into the box interactively as myself (not the service account that the message processor is operating under) and the messages start processing. Then, for the next few days, everything works as expected until the process repeats itself. Additionally, during the time that messages aren't processing, I don't receive any error notifications or other indication that things aren't working.

Has anyone else run into a similar situation and can offer suggestions on how to fix this or what to look for

Additional Information

 

OS: Windows Server 2016

Dynamics Adapter: 5.6.0.58564

 

Thanks,

Steve

[Audrey Buettner]

Have you been able to figure this out I'd be interested since I have seen on very rare occasions where one or two scribe services stop for some unknown reason but then start up once I LOG INTO the server. Have you tried assigning your user as the services account to see if that reveals anything Guessing you already scanned your server Event Logs.

[Audrey Buettner]

They just posted this which might be helpful to at least make sure the services are running:

 

https://support.tibco.com/s/article/Programmatically-Start-Scribe-Insight-Services

[Steve Platz]

I haven't figured this out yet. I'll be opening a case to see if support can lend any assistance to figuring out the root cause. No services are stopping that I can tell - they all report as started if you view the services list.

 

I have not tried assigning my user as the services user, but everything works great with the service account I'm using until it doesn't. The only thing my event logs show are occassional BridgeServer errors where it's unable to access the internal database due to a communication link failure. These are usually temporary and are resolved after a second.