Rest API Crashes when calling UpdateBaq - No specific trigger found

I’m attempting to call a UpdateBaq, it has been working, but it has now started to hang up and is just spinning in circles.

I’m eventually getting a timeout show up in the logs after numerous minutes. But before that its just the same message over and over and over and over…

<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="78"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="80"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="80"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="78"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="78"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="78"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="78"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="80"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="78"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="78"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="78"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="78"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="78"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="78"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="78"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="78"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="78"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="80"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="78"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="80"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="78"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="78"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="78"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="78"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="78"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="78"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="78"/>
<TriggerProvider msg="No specific trigger found for Ice.Triggers.SysActivity.WriteTrigger. Using default trigger implementation" machine="DEV-SERVER" pid="12345" tid="78"/>
<Exception act="unknown" machine="DEV-SERVER" pid="12345" tid="80"><![CDATA[System.Data.Entity.Core.EntityException: The underlying provider failed on Open.

It goes on for quite a while…

The Curl output for the REST call can be found below for reference:

curl -X 'POST' \
  '.../Ice.BO.KineticErpSvc/UpdateBaq' \
  -H 'accept: application/json' \
  -H 'X-API-Key: VALID KEY' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer VALID TOKEN \
  -d '{
  "queryID": "RePrioritiseOps",
  "queryResultDataset": {"Results":[{"JobOper_JobNum":"00001","JobOper_AssemblySeq":0,"JobOper_OprSeq":30,"JobOper_PriorityNo_c":3,"JobOpDtl_ResourceID":"RESOURCE123","JobOper_OpComplete":false,"JobHead_JobNum":"00001","JobOpDtl_AssemblySeq":0,"JobOpDtl_OprSeq":30,"Calculated_NewRowNum":4,"JobHead_JobComplete":false,"JobAsmbl_Company":"PT_Live","JobAsmbl_JobNum":"00001","JobAsmbl_AssemblySeq":0,"RowMod":"U","RowIdent":"06909e33-dddb-41b4-9326-ab86249943bb","SysRowID":"06909e33-dddb-41b4-9326-ab86249943bb"}]}
}'

The Json is valid and works, It has just started to hold up and time out. It was already holding up when called from a function which is why I decided to try it from the REST portal. Initially it didn’t replicate the bug, and went through instantly, and I could view the changes in the analyze sector of the BAQ Editor. But it has now started to replicate the issue and I cannot get it to run in the REST portal either. I did wonder if there’s a memory leak somewhere in the UBAQs?

Anyone seen this before? Any suggestions on what to look for?

Cheers

1 Like

I’d check any BPMs added recently. We had a BPM disabling v2 BAQ rest calls and had no idea why until we went through our BPMs.

Anything on Ice.BO.DynamicQuery ?

1 Like

On purpose, or as a side effect?

1 Like

Maybe it is hanging up because a bad query plan… I’d be wanting to start with the basics and take a look at your event logs an sql logs for any information before restarting both sql and you app, server, then go from there. I noticed that it is pointing to you Dev environment, also check that the shared flag is not turned off on your baq

100% side effect

1 Like