Forum Discussion
Resolver IIGateway connection is failing with Oracle Error Code ORA-50122
Resolver II"ORA-50122" is typically an Oracle client/connection parsing issue rather than a Power BI Gateway issue itself. Since one gateway server works with the exact same gateway version and configuration, I'd focus on identifying what is different in the Oracle client stack.
A few things I'd check:
- Verify that both servers are using the same Oracle provider (ODP.NET Managed vs. Unmanaged) and that the gateway is loading the expected Oracle client. Multiple Oracle Homes on the server can sometimes cause the gateway to load a different client than expected.
- Compare the PATH, TNS_ADMIN, and ORACLE_HOME environment variables between the working and non-working servers to ensure they're resolving to the same Oracle installation.
- Confirm that the tnsnames.ora, sqlnet.ora, and any wallet/network configuration files are truly identical and that the gateway service account has access to them.
- Restart the On-premises Data Gateway service after making any Oracle client or configuration changes so the provider is reloaded.
- If the error specifically mentions the "Community" tag in the connection description, inspect the Oracle connect descriptor (or any generated connection string) for unsupported attributes. It's possible the non-working server is picking up a different client version or parsing the descriptor differently.
- Enable gateway diagnostic logs and compare them with the working server to see the exact connection string or provider being used. That often reveals whether the gateway is loading a different Oracle client or configuration.
Since the other gateway works with the same Power BI Gateway version, I'd lean toward an Oracle client/configuration mismatch on the affected server rather than a bug in the June 2026 gateway release.
If you can share:
- The full "ORA-50122" error text,
- Your Oracle client version (e.g., 19c, 21c, 23ai),
- Whether you're using ODP.NET Managed or Unmanaged, and
- Whether the gateway is running in standard or personal mode,
it will be easier to narrow down the root cause.
Resolver IIHi Sannavajjala,
Here is the info you requested.
Ora-50122 Full text error: Received error payload from gateway service with ID 318007: Oracle: <ccon>ORA-50122: The following configuration parameters are not allowed to be set: community.</ccon>.
Both servers are using 19c
This is the entry in both server's machine.config file.
<DbProviderFactories>
<add name="ODP.NET, Unmanaged Driver" invariant="Oracle.DataAccess.Client" description="Oracle Data Provider for .NET, Unmanaged Driver" type="Oracle.DataAccess.Client.OracleClientFactory, Oracle.DataAccess, Version=4.122.19.1, Culture=neutral, PublicKeyToken=89b483f429c47342" />
<add name="ODP.NET, Managed Driver" invariant="Oracle.ManagedDataAccess.Client" description="Oracle Data Provider for .NET, Managed Driver" type="Oracle.ManagedDataAccess.Client.OracleClientFactory, Oracle.ManagedDataAccess, Version=4.122.19.1, Culture=neutral, PublicKeyToken=89b483f429c47342" />
</DbProviderFactories>
Neither Microsoft.PowerBI.EnterpriseGateway.exe.config files mention anything about ODP.NET
The gateways are running in Standard mode.
I hope this helps.
Thanks,
DKHughes
- sannavajjala
Hi DKHughes,
Thanks for providing the additional details. The fact that both gateway servers are using Oracle Client 19c, the same ODP.NET versions, and the same gateway mode makes this even more interesting.
The key clue appears to be the error itself:
ORA-50122: The following configuration parameters are not allowed to be set: community.
At this point, I'd focus less on Power BI Gateway and more on what Oracle Net configuration is actually being loaded on the affected server. ORA-50122 is generally raised by the Oracle client when it encounters a parameter in the connect descriptor or network configuration that it does not allow.
A few additional things I'd check:
- Compare the effective sqlnet.ora, tnsnames.ora, and any included network configuration files that are being used at runtime. Even if the files appear identical, the affected server may be resolving TNS_ADMIN differently and loading a different set of configuration files.
- Verify that there is only one active Oracle Home being used by the gateway service. Multiple Oracle installations can cause the gateway to load a different Oracle client or network configuration than expected.
- Use Oracle tools such as tnsping and sqlplus while running under the same service account context as the gateway to confirm which network configuration is actually being used.
- Enable Oracle Net client tracing on both the working and failing servers and compare the generated traces. This may reveal where the community parameter is being introduced.
- Check whether the Oracle listener or connect descriptor contains a COMMUNITY attribute that one client is interpreting differently than another.
- Review the Windows registry entries for Oracle Home configuration on both servers. I've seen cases where two servers appear identical but are referencing different Oracle network admin locations.
Since the same gateway version and ODP.NET version work successfully on another server, I still suspect an Oracle client configuration difference rather than a Power BI Gateway defect. The fact that the error explicitly references the community parameter suggests that the failing server is parsing a different connect descriptor or Oracle Net configuration than the working server.
One additional test would be to create a simple standalone ODP.NET or SQL*Plus connection from the affected server using the exact same TNS alias. If that reproduces ORA-50122 outside of the gateway, it would confirm the issue is entirely within the Oracle client/network layer rather than Power BI Gateway.
Let us know whether the Oracle connection succeeds outside the gateway and whether Oracle Net tracing reveals the source of the community parameter. That should help narrow this down considerably.
Thanks,
Manoj Annavajjala
- DKHUghes55
Hi Manoj,
I did find a couple of differences in the Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config file. The one that worked was set this way.
<setting name="MashupFlight_EnableOracleBundledOdacProviderV2"
serializeAs="String">
<value>False</value>
</setting>The one that doesn't was set this way
<setting name="MashupFlight_DisableOracleBundledOdacProviderV2"
serializeAs="String">
<value>False</value>
</setting>I changed the one that didn't work to be like the one that did.
The other differences was the ADServices entries in the one that did work had no values.
The one that did not work had entries.
"ADServerPath"
"ADUserNameReplacementProperty"
"ADUserNameLookupProperty"
DKHughes55