Spawn BPM: Security Error: 1

[JJack]

Hi,
Any suggestions on why a 'Spawn BPM: Security Error: 1' might have suddenly appeared?
We have a csv file of 'ticket details' which we process via a scheduled run of goHornbillRequestImport.exe, controlled by a json file (Hornbill Service Manager Request Import Utility V1.12.0); neither of these files have changed since October but last night's run failed for one out of 32 tickets, where there were no failures on the previous night's run. A ticket was raised, but not associated with the process.
The csv file includes service id and catalog item id, and is the same for all the records. The catalog item specifies a process.

2023/11/09 07:55:43 Records Found: 32
2023/11/09 07:55:43 Requests Logged: 32
2023/11/09 07:55:43 Requests Skipped: 0
2023/11/09 07:55:43 Requests with available BPM Workflows: 32
2023/11/09 07:55:43 BPM Workflows Spawned: 31
2023/11/09 07:55:43 BPM Workflows Associated to Requests: 31
previous night:
2023/11/08 07:55:44 Records Found: 32
2023/11/08 07:55:44 Requests Logged: 32
2023/11/08 07:55:44 Requests Skipped: 0
2023/11/08 07:55:44 Requests with available BPM Workflows: 32
2023/11/08 07:55:44 BPM Workflows Spawned: 32
2023/11/08 07:55:44 BPM Workflows Associated to Requests: 32
The error was:
2023/11/09 07:55:31 [DEBUG] Spawning BPM [is---scheduled---automatic-tickets] for [SRnnnnn390]
2023/11/09 07:55:31 [ERROR] MethodResult not OK: Spawn BPM: Security Error: 1

A successful association shows as:
2023/11/09 07:55:32 [DEBUG] Spawning BPM [is---scheduled---automatic-tickets] for [SRnnnnn391]
2023/11/09 07:55:32 [DEBUG] BPM Spawned: BPM20231109000024
2023/11/09 07:55:32 [DEBUG] BPM [BPM20231109000024] Associated to Request [SRnnnnn391]
Thanks,
Jill.

 

[Berto2002]

@JJack see if the one that failed meets the conditions we describe in this thread. You may be experiencing another facet of a potential defect introduced earlier this week with the release ("A ticket was raised, but not associated with the process").

 

[JJack]

Thanks @Berto2002, I don't think for us it's the details of the particular item that are the problem. The entry in our csv file that failed yesterday has been set up fine today, with the call associated to its process, but a different entry has failed with the security error.
I've looked back through the logs and in total we seem to have had three failures, today 11th, yesterday 10th, and an earlier one from the morning of the 3rd (and a different set of call details on that date). 

The process is mentioned in the log file:
2023/11/03 07:55:14 [DEBUG] Using Catalog ID 553 [Automatic tickets]
2023/11/03 07:55:14 [DEBUG] Using BPM is---scheduled---automatic-tickets
2023/11/03 07:55:14 [DEBUG] New Service Manager Request: SR00017386
2023/11/03 07:55:14 [DEBUG] Request Social Object Ref Update Successful
but then fails to get initiated:
2023/11/03 07:55:30 [DEBUG] Spawning BPM [is---scheduled---automatic-tickets] for [SR00017386]
2023/11/03 07:55:30 [ERROR] MethodResult not OK: Spawn BPM: Security Error: 1

As the calls are raised by the RequestImport program, I don't have access to any process logs. 
Might there be somewhere else I can look for more information?

I haven't found anything on what 'security error: 1' might mean.

[Steve Giller]

If these are scheduled Requests (based on the Workflow name) would the recently released Scheduled Request functionality be something that would replace and improve on using the Request Importer?

[JJack]

Thanks for the suggestion @Steve Giller. We currently have well over 50 calls specified, so not immediately keen on re-entering all the details.
We also currently populate extra fields that do not seem obviously catered for in the Scheduled Request functionality, such as customer ids (not necessarily important), various analyst ids for the tickets to be assigned to, and several different due by times to set up within the activities that the process raises.

We have not had any more errors since the 10th ('11th' above was my mistake), so it just seems to have occurred on three days.

However, there were failures and 'security error: 1' must be set deliberately somewhere, so I would be interested to know what it means.