Workflow Notification Mailer Stuck In Starting Status With Error "INBOUND_SERVER=Protocol Is Not Supported"
(Doc ID 3048009.1)
Last updated on SEPTEMBER 17, 2024
Applies to:
Oracle Workflow - Version 12.2 to 12.2.13 [Release 12.2]Information in this document applies to any platform.
Symptoms
In EBS Oracle workflow,Inbound processing enabled with OAUTH Office 365 mail server using proxy server.After configuration workflow notification mailer failed to start and mailer stuck in starting status.
Below error message captured in mailer log file.
Inbound test connection from configuration page and inbound test connection using AFJVAPRG command worked without any issues.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.Connect to EBS application
2.Configure Inbound processing
3.Start workflow notification mailer.
Changes
EBS upgraded to 12.2.13 and Used OAUTH for Inbound processing
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |