I actually saw one post on the internet that said, the incoming queue for connect was broken.
We have tried numerous things, and we can even seem to get any kind of message to show up in the econnect event log when we drop an xml into the queue
We've used the profile to see what was happening on the database, but don't see any attempted login or processing.
Our settings for the incoming queue are below
the message comes in the queue, and shows up in the Journal but doesn't appear to be processing into GP 2016
We do have integrations running... and those seem to work, but we are told
that integrations don't hit the econnect Queue
Can anyone please help? I'd appreciate any suggestions
<add key="eConnect.BackOffice.ConnectionString" value="data source=GPDBSRV;initial catalog=ABC;integrated security=SSPI;persist security info=False;packet size=4096" />
<add key="eConnect.Incoming_Queue" value="GPSRV\Private$\econnect_incoming16" />
<add key="eConnect.Transactional_deadletter_Queue" value="1" />
<add key="eConnect.Schema.Type" value="" />
<add key="eConnect.Schema" value="" />
<add key="eConnect.LogAll" value="2" />
<add key="eConnect.Threads" value="0" />
