Skip to content

Connect Server fails to start with a repeating UnauthorizedAccessException ('POST error #401: Unauthorized access') after changing the ifsconnect user's password through the installer (both the Oracle user password and instance configuration were updated) — reinstalling the instance and services entirely doesn't fix it.

Answer

Check whether the IFSCONNECT application user's own status is Active — in a confirmed case, this exact 401 error had nothing to do with the password change itself; the actual cause was that the IFSCONNECT user had an Inactive status in the application. Setting the IFSCONNECT user's status to Active resolved the UnauthorizedAccessException completely, even though the password, instance, and service-level troubleshooting had all been correct and thorough. This is worth checking early, since it's easy to overlook while focused on password/credentials troubleshooting.

← Browse Integrations and APIs questions