Small and medium business | Business Central, N...

NavNotSupportedException error in BC14 when there is QueryCategory property in Pages

(0) Share

Report

Posted on by Ghetz

3,013

We have an installation that has been running without any problem for about 2 years after upgrade from NAV 2009. They have BC14.0.45810.0

Yesterday, after server restart and Windows Update, users started reporting this error when opening main pages in BC, like customer list, item list, sales orders, etc.

Microsoft.Dynamics.Nav.Types.Exceptions.NavNotSupportedException

Also this is logged in the server's event viewer, for example whe opening Customer's List:

Server instance: ******
Category: Extensions
ClientSessionId: b7a2353c-7fb7-468c-bf04-33776b1c60e3
ClientActivityId: 22c421aa-eb1f-49ce-b5fa-9b960a0a4e93
ServerSessionUniqueId: f53d7320-d205-4b82-8191-48d68ecb6f94
ServerActivityId: 2d2383f8-ac71-4dea-84b5-f8f7c138e7d9
EventTime: 11/05/2019 09:49:59
Message Fatal error during metadata load -- Type:Query; Id:50; MetadataGroup:0; MetadataLoaded:False; CLRLoaded:False; ThreadGroup:0
ProcessId: 14224
Tag: 00007YQ
ThreadId: 22
CounterInformation:

Query 50 is "Power BI Customer List". Maybe a missing extension?

Doing a google search, we find this issue linked to the QueryCategory property of Pages: https://github.com/microsoft/AL/issues/5416

So just making this property blank, indeed solved the issue. But no official explanation of this issue was ever notified that I know of. We even upgraded to the latest Cumulative Update of BC 14 June 2022. The issue is still there.

Compiling the full application also didn't work.

Anyone know about the root reason of this error, and why it can suddenly appear after a server restart? Any fix that doesn't imply modifying all pages?

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Inge M. Bruvik 1,111 Moderator on at

Like (0)

Report

I have never seen this issue with BC14. I would suggest you open a support request with Microsoft around this.

BC14 is also going to end of life in 2023, so you should start planning an upgrade to the latest version.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 95,729 Super User 2025 Season 2 on at

Like (0)

Report

Hi, I've never had this problem either, soagree with Inge, suggest you install BC14 on another host or virtual machine and try again, see if there is still this problem? If you still have problems, it is recommended to contact Microsoft.

In addition, BC14, as the last version to retain the Windows Client, can be supported until Oct 14, 2025.

More details: https://docs.microsoft.com/en-us/lifecycle/products/dynamics-365-business-central-onpremises-fixed-policy

Hope this helps as well.

Thanks.
ZHU

Was this reply helpful? Yes No
Ghetz 3,013 on at

Like (1)

Report

Thanks for your comments. We are indeed aware of end of support dates, and we will upgrade our customers acordingly. However, this issue is know to have been there, but has not been correctly addressed. It's already been reported in github, as you can see in my original post, and also in this same forum:

Anyway, it's nothing major, as just removing the Querycategorý property from all pages solved the issue, but would be nice to have some official explanation on why this is happening. So far, we've only encountered this in one of our many customers.

Was this reply helpful? Yes No
GM-03061541-0 2 on at

Like (0)

Report

Even though this issue is a bit old and I'm doing thread necromancy I wanted to add what caused this error for us:

I was having a Query that used a Flow Field in it. That worked fine. Due to some new requirements we extended the Flow Field to also filter for another Flow Field.

This broke the metadata of our Query. If you ran page 9174 (All Objects with Captions) it wouldn't let you display the faulty Query with the NavNotSupportedException error.

In my case I was able to create a new FlowField on a FlowField that isn't used in a Query. Seems like this was one recursion/select statement depth too much to handle for BC.

Maybe this helps someone else to find the reason.

Was this reply helpful? Yes No