Environment throwing strange errors

[KoenJanssensPD]

Dear,

I have some development sandbox Dataverse environments, with a security group configured, that behaves strangely.

9 out of 10 times, some of the default tables do not show in the list of tables, together with an error:

My account is part of the security group and I have the "basic user", "system administrator" and "system customizer" security roles assigned...

In the browsers' network trace I don't see anything pointing me to the cause...

Is there any way I can get more info on why this happens?

Thanks,

Koen

[cchannon]

If that's the case, you might be able to fix it yourself with solution xml, right?

I mean, both of those attribs carry in solution xml, so if you still have that broken copy you made, you might try putting these entities into a (managed) solution, exporting it, then cracking it open to put those labels in by hand and re-importing it. I mean, probably won't work but couldn't hurt.

[KoenJanssensPD · Accepted solution]

So, the holidays are a few days behind me, time for an update:

I had a call with a MS support engineer and he explained me a bit, though he was also a bit fuzzy about everything:

- How did it happen? They think it went wrong after the Environment received an automatic release wave update

- How did they found out was wrong? They used internal tools to check; they are considering if these tools might be set publicly available so end-users can find out and resolve problems themselves. That will probably take quite some time before it really happens...

- How did they resolve it? They made a rebuild of the environment, also with those internal tools...

Let's hope that it doesn't happen anymore, since we lost quite some time investigating the problem...

[AlexD1]

Strange situation with quite strange "solution" (Let's hope that it doesn't happen anymore...)
More than 5 months passed since your initial post. And we have the same issue now (18th of Jan 2022) with "The tables could not be fetched: ..."  

So it seems we need to use only custom tables within a solution in order to avoid this strange errors. Are there any other ideas to assure solution stable work?

[KoenJanssensPD]

Hi @AlexD1 , from my ongoing experience, it seems that it is related with missing translations (for tables and/or fields) if multiple languages are used in the same environment. I haven't had the same issue since my initial case, but since you now have the same, I am also starting to worry again...

[AlexD1]

Heyo @KoenJanssensPD,
nice to have your fast reply. 
I really sorry that my message caused some kind of your worries. But my case is not concerned with any other languages except initial English. 
The Solution that we provided for Customer include only Contact table from Standart list. Now we have the situation that on MakerPortal we have the same strange error message and our Customer see "Unknown" field instead of "Contacts" within the App. 

[KoenJanssensPD]

Hi @AlexD1 , your response got me thinking, and I was wrong about stating that is has to do with multiple languages, but more with missing names for entities. Below what I got from MS Support:

I have not found (I have not been searching a lot 😉 ) any way to find this information myself. Maybe somebody knows a way to get these "MSCRM:ASSERTEX" logs somehow...?

[AlexD1]

Hello KoenJanssensPD, 
here I have some answers (after a month of communication with Support).

1) They think that the reason in LabelCache feature (that is switched on by default in every environment). and probably it somehow depends on Languages settings (no matter if only default English was turned on).
2) Also, unfortunately, they have no any roadmaps or public docs on the issue. 

Really at the moment the issue can appears in any new environment (even within one tenant). 
That's strange 

[JenniferK]

This same error just started happening to me on a dev environment that I had reset

Will resetting the environment again get rid of the problem?

[AlexD1]

Hello @JenniferK , 

it seems the issue can appears in every instance that have LabelCache feature turned on. So if it was not turned off then you can face it again. 

But that doesn't mean, that you will face it anyway. The issue description was very unclear (like "when the initial org used to create the Label Cache has invalid Label layers then the Label Cache created will be corrupted and can cause issues for the orgs sharing the Label Cache") 

Generating a ticket to Support seems the only way to have the issue eliminated (if it will appears again).