Warning 661 (Authentication Failed) When Processing Messages For Channels w/ "Process immediately" Enabled

[mikeperley]

I upgraded FMS to version 20.2.1.19 running on Windows Server 2016 yesterday. Since then, I'm receiving status 2 (Failed Permanently) for every message in sent to a channel that has "Process immediately" enabled. The messages can be processed successfully via the Retry button. The FMS event log reports the following:

2023-10-09 11:52:27.983 -0600 Warning 661 FMS 19 SECURITY: Client "process message immediately ( messageID ) - developer 172 (WIN-5UHJC0NQJIV) [127.0.0.1]" authentication failed on database "Order_Management.fmp12" using "developer [fmrest]".

I do not receive any errors if I uncheck the "Process immediately" option and let the messages process according to the server script schedule. This is my current solution to the issue.

I'm using the current version of SimpleQ (1.3.2) along w/ Otto version 3.6.3.

[toddgeist]

Hi Mike,

Process Immediately means that it is the same client that sends the message is going to process the message. If it is queued for later, it will use the Server Side Client, authenticated with the user name and account in the server-side script schedule.

The most likely answer is that Order_Management.fmp12 can't be accessed with the credentials backing the API KEY.

Are you sure that SImpleQ and Order_Management.fmp12 have the exact same credentials used by the API key? If they do then I am afraid I don't have an easy answer and I would suggest going back to 20.1 or dropping process immediately for now.

We will look to see if something changed on 20.2, but I don't know how long that will take.

Todd

[mikeperley]

Hey Todd, We don’t need these to be processed immediately so I’ve dropped that for now — we’re good there. I just wanted to log the report in case it was unexpected behavior. As a quick test, I reset all API keys using the “developer” account seen in the attached screen shot and that appeared in the log entry I sent earlier. This is also the same account used for the scheduled server script and that was logged in during my tests. Is the "process immediately" option compatible with messages sent via insert from URL or from other external systems via Otto? In this circumstance, the Order_Management file is accessed via a local FM client. It performs an update via PSOS in another file because that’s the only way to import data from an ODBC data source. In order to avoid having SimpleQ open on the client machine and running into missing file (100) errors, we’ve been sending those messages via insert from URL in the PSOS session. I’m not sure if that makes sense, and if it doesn’t, no worries because the workaround to not process messages immediately is sufficient for us.

[toddgeist]

are using insert from url using "fmp://" or are you sending it through Otto? — Todd

--- original message --- On October 9, 2023 at 2:07 PM PDT ***@***.*** wrote: Hey Todd, We don’t need these to be processed immediately so I’ve dropped that for now — we’re good there. I just wanted to log the report in case it was unexpected behavior. As a quick test, I reset all API keys using the “developer” account seen in the attached screen shot and that appeared in the log entry I sent earlier. This is also the same account used for the scheduled server script and that was logged in during my tests. Is the "process immediately" option compatible with messages sent via insert from URL or from other external systems via Otto? In this circumstance, the Order_Management file is accessed via a local FM client. It performs an update via PSOS in another file because that’s the only way to import data from an ODBC data source. In order to avoid having SimpleQ open on the client machine and running into missing file (100) errors, we’ve been sending those messages via insert from URL in the PSOS session. I’m not sure if that makes sense, and if it doesn’t, no worries because the workaround to not process messages immediately is sufficient for us. Thanks! <https://prodigypromos.com/> Mike Perley O: +1 (801) 705-5069 M: +1 (801) 362-5384 122 S 1380 W • Lindon, Utah 84042 • USA

On Oct 9, 2023, at 14:34, Todd Geist ***@***.***> wrote: Hi Mike, Process Immediately means that it is the same client that sends the message is going to process the message. If it is queued for later, it will use the Server Side Client, authenticated with the user name and account in the server-side script schedule. The most likely answer is that Order_Management.fmp12 can't be accessed with the credentials backing the API KEY. Are you sure that SImpleQ and Order_Management.fmp12 have the exact same credentials used by the API key? If they do then I am afraid I don't have an easy answer and I would suggest going back to 20.1 or dropping process immediately for now. We will look to see if something changed on 20.2, but I don't know how long that will take. Todd — Reply to this email directly, view it on GitHub <#26 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A54BHNRA2VUQ7BVH4PVUF3TX6RNULAVCNFSM6AAAAAA5ZFQYECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJTG43DCOJSG4>. You are receiving this because you authored the thread.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***> --- end of original message ---

[mikeperley]

We are sending through Otto.

…

On Oct 9, 2023, at 15:58, Todd Geist ***@***.***> wrote: are using insert from url using "fmp://" or are you sending it through Otto? — Todd --- original message --- On October 9, 2023 at 2:07 PM PDT ***@***.*** wrote: Hey Todd, We don’t need these to be processed immediately so I’ve dropped that for now — we’re good there. I just wanted to log the report in case it was unexpected behavior. As a quick test, I reset all API keys using the “developer” account seen in the attached screen shot and that appeared in the log entry I sent earlier. This is also the same account used for the scheduled server script and that was logged in during my tests. Is the "process immediately" option compatible with messages sent via insert from URL or from other external systems via Otto? In this circumstance, the Order_Management file is accessed via a local FM client. It performs an update via PSOS in another file because that’s the only way to import data from an ODBC data source. In order to avoid having SimpleQ open on the client machine and running into missing file (100) errors, we’ve been sending those messages via insert from URL in the PSOS session. I’m not sure if that makes sense, and if it doesn’t, no worries because the workaround to not process messages immediately is sufficient for us. Thanks! <https://prodigypromos.com/> Mike Perley O: +1 (801) 705-5069 M: +1 (801) 362-5384 122 S 1380 W • Lindon, Utah 84042 • USA > On Oct 9, 2023, at 14:34, Todd Geist ***@***.***> wrote: > > > Hi Mike, > > Process Immediately means that it is the same client that sends the message is going to process the message. If it is queued for later, it will use the Server Side Client, authenticated with the user name and account in the server-side script schedule. > > The most likely answer is that Order_Management.fmp12 can't be accessed with the credentials backing the API KEY. > > Are you sure that SImpleQ and Order_Management.fmp12 have the exact same credentials used by the API key? If they do then I am afraid I don't have an easy answer and I would suggest going back to 20.1 or dropping process immediately for now. > > We will look to see if something changed on 20.2, but I don't know how long that will take. > > Todd > > — > Reply to this email directly, view it on GitHub <#26 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A54BHNRA2VUQ7BVH4PVUF3TX6RNULAVCNFSM6AAAAAA5ZFQYECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJTG43DCOJSG4>. > You are receiving this because you authored the thread. > — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***> --- end of original message --- — Reply to this email directly, view it on GitHub <#26 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A54BHNWMATOEO2MBCBZ5G53X6RXRLAVCNFSM6AAAAAA5ZFQYECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJTHE2DCMBUGQ>. You are receiving this because you authored the thread.