Power BI on-premises Gateway - Error When Gateway Members On Two Separate Versions

[Sad_Gateway]

Hi all, I'm hoping someone has come across the following issue:

We have an on-premises Power BI gateway with 2 members within the Gateway clusters, with each being a different Virtual Machine.

The version of the primary member is 3000.210.14, which is from Jan 2024. This is noticeably out of date but we had kept it on this version as we've had negative issues updating gateways in the past, and this version was stable for us.

We decided to bite the bullet and update the gateway to the latest version, starting with the secondary gateway member.

However, as soon as we did this, reporting visuals started displaying errors: Feature is not supported. Please make sure you have installed the latest version of the gateway.

We tried disabling the out-dated primary member, leaving the updated member running on its own but the issues persist even after waiting 30 minutes. This makes us hesitant to proceed with updating the primary member since we would have expected the secondary member to be work when it alone was enabled and we wouldn't have an easy rollback option.

The Gateway logs contain multiple instances of the following error:

InnerType=ArgumentOutOfRangeException

InnerMessage=Specified argument was out of the range of valid values.

Parameter name: OleDbCreateRowsetRequest

If anyone has come across this before or has any assistance to offer, it would be much appreciated!

[v-bmanikante]

Hi @Sad_Gateway 

May I check if this issue has been resolved? If not, Please feel free to contact us if you have any further questions.

Thank you

[v-bmanikante]

Thankyou, @MohdZaid_ for your responses.

Hi @Sad_Gateway 

We appreciate your inquiry through the Microsoft Fabric Community Forum.

We would like to inquire whether have you got the chance to check the solution provided by @MohdZaid_  to resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.

Thank you.

[MohdZaid_ · Accepted solution]

Hey @Sad_Gateway , 

What you’re seeing is happening because a gateway cluster in Microsoft Power BI is expected to have all members on the same version. When you upgraded only the secondary VM and left the primary on the January 2024 build (3000.210.14), the cluster became version-mismatched. Power BI treats the cluster as a single logical gateway, so when different members advertise different capabilities, the service can throw errors like “Feature is not supported” and the OleDbCreateRowsetRequest argument out of range exception. That error usually indicates a capability or provider mismatch triggered by the mixed versions.

Even though you disabled the older primary member, Power BI does not instantly re-evaluate the cluster metadata. The service may still cache capability information, and existing connections might still reference the older configuration. That’s why the issue persisted even after waiting.

The stable and supported approach is to ensure both gateway members run the exact same version. The recommended next step is to plan a short maintenance window and upgrade the primary member to match the updated secondary node. Before doing that, take a VM snapshot or backup and make sure you have the recovery key so you have a rollback option. Once both nodes are on the same version, restart the gateway services on both machines and allow a few minutes for synchronization. In most cases, this resolves the feature support and OLE DB errors.

Running mixed gateway versions in a cluster is not a supported long-term state, and issues like the one you’re seeing are a common symptom of that mismatch. Aligning the versions should stabilize the environment.

If this explanation helped, please mark it as the solution so others can find it easily.

If it helped, a quick Kudos is always appreciated it highlights useful answers for the community.

Thanks for being part of the discussion!