Error: (27001) ErrorCode=,Connector Exception: Configuration file conf/ModelBridgeList.xml is invalid

Question

Error: (27001) ErrorCode=,Connector Exception: Configuration file conf/ModelBridgeList.xml is invalid

Carson Souza 5

We are encountering the following error when attempting to create a new Oracle scan in Microsoft Purview:

Error: (27001) Connector Exception: Configuration file conf/ModelBridgeList.xml is invalid

Context:

We already have an existing Oracle connection that is working correctly and currently running scans without issues.
We recently updated the Integration Runtime to a newer version, but it became unstable.
We rolled back to the last stable version: 5.49.9210.1.
A new Oracle connection was created successfully, with no errors during setup.
However, when attempting to create a new scan using this new connection, the error above is returned.

Additional Details:

Authentication is set to Basic, with credentials stored in Azure Key Vault.
The ModelBridgeList.xml file has not been manually modified.
The Oracle database connection was tested successfully outside of Purview (via SQL Developer).
The Integration Runtime is installed locally and running the version mentioned above.
The issue occurs only with the new connection — the existing one continues to work as expected.

Questions:

What could be causing this error specifically with the new connection?
Is there any cache or metadata in Purview that could be interfering?
Are there any recommendations for validating or regenerating the ModelBridgeList.xml file?
Does version 5.49.9210.1 of the Integration Runtime have any known limitations with multiple Oracle connections?

Smaran Thoomu 29,335 Reputation points Microsoft External Staff Moderator

2025-07-23T16:48:11.12+00:00
Hi Carson Souza
Thank you for sharing the detailed context - that’s very helpful for understanding the situation.

The error message you’re encountering:

“Error: (27001) Connector Exception: Configuration file conf/ModelBridgeList.xml is invalid”

typically points to an issue with how the ModelBridgeList.xml file is interpreted by the Microsoft Purview scanning framework - often due to mismatches in integration runtime (IR) versions, scan configuration metadata, or connector registration inconsistencies.

Based on your observations, here are some potential causes and next steps:

Integration Runtime Compatibility

You mentioned rolling back to v5.49.9210.1. While this is a previously stable version, Purview continues to evolve, and compatibility for newer features or connector changes may not be guaranteed in older IR builds.

Recommended Action: If possible, try upgrading to the latest supported IR version, even if temporarily, and then re-attempt scan creation. This often resolves unexpected XML or bridge mapping issues introduced in more recent connector updates.

Connector Registration Corruption or Incomplete Metadata

Even if the Oracle connection tested successfully, the bridge registration metadata might be stale or partially initialized for the new connection.

Recommended Action:

Stop the IR service temporarily.

Navigate to the IR install directory and clear the temp and cache folders, if present (ensure logs are backed up first).

Restart the IR and reattempt the scan creation.

ModelBridgeList.xml Validation

While the file wasn’t manually modified, it’s possible the rollback didn’t fully align the ModelBridgeList.xml schema with the Oracle connector version expected by Purview.

Unfortunately, this file isn’t user-editable, but reinstalling the IR or applying a connector patch will refresh it.

Known IR Limitations

There are no known published limitations for version 5.49.9210.1 specific to multiple Oracle connections, but Microsoft documentation typically assumes you're using the latest IR version with new connector definitions.

Further steps:

Temporarily upgrade to the latest Integration Runtime version.

Clear cached config from the IR host machine (or reinstall IR cleanly).

Retry scan creation with the same Oracle credentials.

If it still fails, please share the full IR logs (found in the installation path under \logs) for deeper analysis, or provide the support request ID if one is already opened.

I hope this information helps. Please do let us know if you have any further queries.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
Smaran Thoomu 29,335 Reputation points Microsoft External Staff Moderator

2025-07-24T18:43:28.3533333+00:00

Carson Souza We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Carson Souza 5 Reputation points

2025-07-24T18:53:18.2066667+00:00
We've tested and re-updated the Runtime to the current version, but it hasn't resolved the issue. The runtime is no longer coming online, and its status is now "running (unhealthy)."

We performed a connection test through the runtime, which is on a VM, and received the following error:

Failed to connect to the database. Error message: ERROR [08001] [Microsoft][ODBC Oracle Wire Protocol driver][Oracle]TNS-12505: TNS:listener could not resolve SID given in connect descriptor ERROR [08001] [Microsoft][ODBC Oracle Wire Protocol driver][Oracle]TNS-12505: TNS:listener could not resolve SID given in connect descriptor

However, we've already contacted the VBA team to adjust some HOST parameters, and the error still persists.

On the Purview side, it continues to report:

Error: (27001) Connector Exception: Configuration file conf/ModelBridgeList.xml is invalid"
Smaran Thoomu 29,335 Reputation points Microsoft External Staff Moderator

2025-07-25T18:17:06.7866667+00:00
Carson Souza Thank you for the update and for confirming that you've upgraded the Integration Runtime (IR) to the current version. Given that the IR status is now showing as “running (unhealthy)” and the connection test returns a TNS-12505 error, the issue seems to have two separate but related parts:

TNS-12505 Error (Oracle Listener Issue)

This error indicates that the Oracle Listener cannot resolve the SID specified in the connection descriptor. Even though the HOST parameters were adjusted by the VBA team, this suggests one of the following:

The SID provided might not be registered with the listener.

The connect descriptor might be pointing to the wrong service name or port.

There's a firewall or routing issue between the IR VM and the Oracle host.

Recommended steps:

Validate the Oracle connection descriptor (SID vs SERVICE_NAME) – if possible, switch to using SERVICE_NAME in the connection string instead of SID.

Confirm with your DBA team that the SID exists and is correctly registered with the Oracle listener (use lsnrctl status).

Try connecting to Oracle from the IR VM using SQL Developer or sqlplus with the same connection string.

Purview Error - ModelBridgeList.xml Invalid

This error usually stems from:

A corrupted IR installation or partial rollback.

Metadata sync failure between IR and the Purview scanner framework.

Failure of the IR to load bridge definitions (due to Oracle connectivity failure as seen above).

Next actions:

Once the Oracle connectivity issue is resolved (above), reinstall the IR cleanly on the VM to regenerate the necessary config files including ModelBridgeList.xml.

Before reinstall:

Uninstall the IR.

Manually delete leftover folders at C:\Program Files\Microsoft Integration Runtime and %ProgramData%\Microsoft Integration Runtime.

Reinstall the latest IR version and re-register it to your Purview account.

Let us know once you’ve tested with a working Oracle connection from the IR VM, and we can help validate if the Purview error persists.

I hope this information helps. Please do let us know if you have any further queries.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
Smaran Thoomu 29,335 Reputation points Microsoft External Staff Moderator

2025-07-28T11:03:02.3766667+00:00

Carson Souza We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Carson Souza 5 Reputation points

2025-07-28T12:14:24.23+00:00

Hello, good morning. We will try today the guidance you gave us about the xml issue.
Carson Souza 5 Reputation points

2025-07-28T14:01:41.9166667+00:00
We did the reinstallation and cleanup on the runtime again. After that, when we tried to connect another Oracle database again, the error message is now this:

Error: (27001) ErrorCode=, Receiving connector dependency update, downloading in progress, please try again later
Carson Souza 5 Reputation points

2025-07-29T11:16:15.3666667+00:00

Right now, the scans that used to work are no longer functioning. All the oracle scans that we tried to perform show the same message.

Error: (27001) ErrorCode=,Receiving connector dependency update, downloading in progress, please try again later

We are trying to understand if it is something that we need to update or if it is something that you are updating in the Oracle connector that caused the scans to be suspended.

Finally, it is highlighted that even after uninstalling and reinstalling from scratch, the self-hosted Runtime continues to show the same status:

Running (not intact)
Smaran Thoomu 29,335 Reputation points Microsoft External Staff Moderator

2025-07-30T12:20:22.5733333+00:00
Carson Souza Thanks for the detailed follow-up and for performing the full IR reinstallation. The current message you're seeing:

Error: (27001) ErrorCode=, Receiving connector dependency update, downloading in progress, please try again later

indicates that the Microsoft Purview scanner is in the middle of fetching or syncing updated connector definitions-this typically happens after a fresh install or when new connector updates are being rolled out on the backend.

Here's what we recommend:

Wait Period & Retest

This "downloading in progress" state is usually temporary and resolves automatically once the required Oracle connector dependencies are fully downloaded by the IR.

Action: Please wait ~30–60 minutes and then retry the Oracle scan.

Confirm IR Status Is Intact

The "Running (not intact)" status confirms that the IR has not yet completed loading all required connectors.

This can happen when:

There’s a network interruption between IR and the Microsoft download endpoints

The IR host has firewall restrictions

A service update is rolling out (which may be the case now)

Action: Ensure the IR host can reach the below endpoints over HTTPS (port 443):
*.purview.azure.com *.azureedge.net *.blob.core.windows.net

Optional Actions if It Doesn’t Resolve

If the issue persists even after waiting:

Restart the Integration Runtime service.

Reboot the VM where IR is installed.

If still unresolved, capture and share the IR logs from:
C:\Program Files\Microsoft Integration Runtime\5.0\Shared\Logs

We understand this has blocked both your new and existing Oracle scans and truly appreciate your patience. Based on current indicators, this appears to be either a connector update sync delay or a network/config sync issue on the IR side, not an issue with your Oracle source itself.

Please let us know how it looks in the next hour or so - and we’ll continue to assist accordingly.

I hope this information helps. Please do let us know if you have any further queries.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
Smaran Thoomu 29,335 Reputation points Microsoft External Staff Moderator

2025-08-01T17:18:05.8766667+00:00

Carson Souza We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
EL Jawad, Mohammad 30 Reputation points

2025-08-15T14:37:21.3733333+00:00

Hello , @Carson Souza I am having the same error as you, and i just wanted to clarify about your 4th statement in Additional Details: The Integration Runtime is installed locally and running the version mentioned above.

By locally i am assuming that you mean on the IR VM? is that a fair understanding?

1 answer

Your answer

Smaran Thoomu 29,335 Reputation points Microsoft External Staff Moderator

2025-07-24T18:43:28.3533333+00:00

Carson Souza We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Carson Souza 5 Reputation points

2025-07-24T18:53:18.2066667+00:00

We've tested and re-updated the Runtime to the current version, but it hasn't resolved the issue. The runtime is no longer coming online, and its status is now "running (unhealthy)."

We performed a connection test through the runtime, which is on a VM, and received the following error:

Failed to connect to the database. Error message: ERROR [08001] [Microsoft][ODBC Oracle Wire Protocol driver][Oracle]TNS-12505: TNS:listener could not resolve SID given in connect descriptor ERROR [08001] [Microsoft][ODBC Oracle Wire Protocol driver][Oracle]TNS-12505: TNS:listener could not resolve SID given in connect descriptor

However, we've already contacted the VBA team to adjust some HOST parameters, and the error still persists.

On the Purview side, it continues to report:

Error: (27001) Connector Exception: Configuration file conf/ModelBridgeList.xml is invalid"
Smaran Thoomu 29,335 Reputation points Microsoft External Staff Moderator

2025-07-28T11:03:02.3766667+00:00

Carson Souza We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Carson Souza 5 Reputation points

2025-07-28T12:14:24.23+00:00

Hello, good morning. We will try today the guidance you gave us about the xml issue.
Carson Souza 5 Reputation points

2025-07-28T14:01:41.9166667+00:00

We did the reinstallation and cleanup on the runtime again. After that, when we tried to connect another Oracle database again, the error message is now this:

Error: (27001) ErrorCode=, Receiving connector dependency update, downloading in progress, please try again later
Carson Souza 5 Reputation points

2025-07-29T11:16:15.3666667+00:00

Right now, the scans that used to work are no longer functioning. All the oracle scans that we tried to perform show the same message.

Error: (27001) ErrorCode=,Receiving connector dependency update, downloading in progress, please try again later

We are trying to understand if it is something that we need to update or if it is something that you are updating in the Oracle connector that caused the scans to be suspended.

Finally, it is highlighted that even after uninstalling and reinstalling from scratch, the self-hosted Runtime continues to show the same status:

Running (not intact)
Smaran Thoomu 29,335 Reputation points Microsoft External Staff Moderator

2025-08-01T17:18:05.8766667+00:00

Carson Souza We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
EL Jawad, Mohammad 30 Reputation points

2025-08-15T14:37:21.3733333+00:00

Hello , @Carson Souza I am having the same error as you, and i just wanted to clarify about your 4th statement in Additional Details: The Integration Runtime is installed locally and running the version mentioned above.

By locally i am assuming that you mean on the IR VM? is that a fair understanding?

Answer 1

Americo Santos 0

Hi.

Today I run into the same error message:
Error: (27001) ErrorCode=,Receiving connector dependency update, downloading in progress, please try again later

The configuration of the scan was not changed and the scan did work previously without issues.

Americo Santos 0 Reputation points

2025-08-28T18:53:20.25+00:00

In addition, when going to the scan history of Oracle scans, it shows none.

I'm absolutely sure that I did some scans because and it's proved by having assets in the collections to where scanned assets goes in this scanning definitions.

If I go to scan history of Fabric scans, it is showing previous scan history, even from scans run on March this year.

Share via

Error: (27001) ErrorCode=,Connector Exception: Configuration file conf/ModelBridgeList.xml is invalid

1 answer

Your answer