JDBC Import fails in Initiating the connectionDescription<!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms JDBC Import fails with below Error: MID Server reported error: Failed to init the JDBC connection. Check configuration Release All versions Environment Set up a JDBC Data Source via MID Server with or without specific Application scope which has Application Administration as Active. Cause Configuration issue of scope where it has Application Administration set to true on the sys_scope record and the ACL issue sys_data_source table. Resolution 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_<scope_name>.user' i.e. whatever is configured on the Application details so that the mid server user can access the sys_data_source table. Additional Information Ref Doc: Access control rules in application administration apps Check system property: glide.security.scoped_administration.honor_global_acl If no scoped ACL rules are defined, application administration apps can inherit global ACL rules. By default, this property is enabled for new and upgraded instances.