New errors after update

Hi Pkjack

You should contact M-Files support directly and immediately to get help in situations like this. This forum is for voluntary support by whoever finds time and cares enough to offer their assistance.

That said, issue 1) seems to be related to your configuration of the Compliance Kit, User Synchronization module. Have you checked that the required properties are in place and have the required Aliases? Have you tried to disable the module?

I have no good suggestions regarding the other issues other than it might help to restart the server after checking your configurations.
I have just updated my own server and have not seen any problems like the above.

Hello bright-ideas.dk,

Thank you for the quick reply. I just found in one of the Vaults (where I can't save the metadata configuration) these errors:

The upgrade log seem to indicate that something in your configuration does not point to a valid reference. That could happen if you have changed the Alias of a property, class or object type, or if a referenced property has been deleted.

Hello brigh-ideas,

Thank you so much for tip.

After the update apparently some rules were broken. It was necessary to remove them, and then it was ok.

I had to delete the rule one by one to find out which one is working wrong. 

I also found that some fields did not contain the dollar (for example - auto fill "CurrentUser" looks like update deleted dollar symbol.

It's hard to say why this state occurred after the update.

We have hundreds of rules and sub-rules set up. Maybe some rule was set wrong when it was working before the update. And the new update is json more sensitive.

Hello brigh-ideas,

Thank you so much for tip.

After the update apparently some rules were broken. It was necessary to remove them, and then it was ok.

I had to delete the rule one by one to find out which one is working wrong. 

I also found that some fields did not contain the dollar (for example - auto fill "CurrentUser" looks like update deleted dollar symbol.

It's hard to say why this state occurred after the update.

We have hundreds of rules and sub-rules set up. Maybe some rule was set wrong when it was working before the update. And the new update is json more sensitive.

There are new server-side validations for metadata card configuration rules in the August '23 Update, you can read more in this support article: New in M-Files August'23: Metadata Card Configuration Background Processing Change

The error message has a GUID for the broken rule. It is not easy to find directly in Admin. A quick procedure is to copy/past the entire set of rules in JSON from the Advanced tab to Notepad++ or a similar tool and then search for the GUID with that tool. At least that will point out the defect rule. After that it may still be somewhat difficult to figure out what "Object reference not set to an instance of an object" really means....