Forum Discussion
This semantic model uses a deprecated gateway version. Upgrade required.
I started getting the following message on nearly every report on my tenant suddenly. The gateway has been updated the same way with the same cadence for years without have this message appear.
The gateway is one update behind the newest. Was able to get the message to go away for most users by restarting the gateway but the message still persists for some. Everything is working fine but as you can imagine, it's causing lots of panic. Any input would be greatly appreciated.
6 Replies
Murtaza_GhafoorSuper User
DClark21044
This is more likely the gateway deprecated warning rather than Power BI refresh failure.
Suggested pathway:- Restart the gateway service, as you already did.
- Upgrade the gateway to the latest available version instead staying one version behind.
- Check that all gateway cluster nodes are running the same version.
- If the warning persists for some users after the upgrade/restart, allow some time for the Power BI Service to refresh its gateway status, hope these steps will eradicate your problem.
Please accept this answer yes and give kudos if this is helpful
Thanks for the suggestions. As a general rule for my organization, we are not allowed to be on the newest update for anything. That being said, we have been one behind the newest update for years and have never encounter this issue. I believe Microsoft supports up to the last 6 updates.
We have a 3-node cluster. All were reinstalled and restarted them all. Most of the warnings are gone but some users still get them. Refreshes are not failing but some semantic model owners are getting notified via email with the warning message after every refresh.
We also started seeing those messages on reports connected to several of our gateway clusters this past week.
Similar to what was stated in DClark21044's post, we have also generally stayed one version behind without users receiving messages like this in the past.
We will be doing some restarting and maintenance on those impacted gateway clusters tomorrow, but just wanted to let DClark21044 know, you are not alone with your scenario.- Jai-Rathinavel
DClark21044 If it's critical, reach out to your Fabric Admin and raise a support ticket. So that issue will be sorted ASAP
v-kathullacCommunity Support
Hi DClark21044 ,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
Regards,
ChaithanyaHello v-kathullac,
I have tried everything except for updating to the newest gateway update. As I mentioned, my company does not allow the newest updates for security and stability reasons. The only thing that seemed to help was restarting the cluster. Started with support nodes and ending with the primary.
The issue still exists it reduced the frequency.
