MID Server reported error: Failed to init the JDBC connection. Check configuration - Scoped App ACL Access Issue
Hey all I'm just adding some additional information to an existing KB for the error.
I have been facing a issue where I get the MID Server reported error: Failed to init the JDBC connection. Check configuration error when running a JDBC connection from a data source. The error only occurs in scoped applications.
The issue occurred in dev and the support team fixed the problem but didn't realise it. Their accidental fix was to provide the mid server admin access to the instance and then restart the mid server.
The issue was that the mid server did not have access to read the sys_data_source table and a none * (so change the mode to table) ACL was required in the scoped app, on the sys_data_source table. Reboot the MID server after the change.

This is the same result as described in the KB from SN except it has more detail to the second option. The first option is not available external or purchased scoped apps like Human Resources Core. https://hi.service-now.com/kb%5Fview.do?sysparm%5Farticle=KB0744351
"Deactivate 'Application administration' on the sys_scope record.
OR
If 'Application administration' is required to be Active. We will need to ensure that the READ ACLs against the 'sys_data_source' table has the role defined - 'x_.user' i.e. whatever is configured on the Application details so that the mid server user can access the sys_data_source table."
https://www.servicenow.com/community/developer-articles/mid-server-reported-error-failed-to-init-the-jdbc-connection/ta-p/2301651
