2026 Top bug, affects all versions of MC back to version 0.9

2026, starting in March, the most common issue reported to our support department is the new Chromium deprecation. It isn't reported to us that way, it is reported as things such as:

I changed a item but the corresponding field didn't change
I've made several changes and found out, possibly days later, that the changes weren't saved
certain buttons or other UI elements aren't showing up that are supposed to be there

This is not a bug(s) in Maintenance Connection, Accruent's MC per se, rather this is a change in how Chromium (the engine behind Chrome, Edge, Brave, Vivaldi, Shift and many others) is starting to remove a feature Maintenance Connection relies on. For more and more people, Chrome page loads are being failed on purpose by Chromium Chromium official statement on this.

Who is affected?

10% (statistical average as of May 5 2026) of Accruent MC users (20% June 2, 40% June 30, 60% July 28, 80% Aug 25, 100% Sept 22, 2026)

Who is not affected?

MCe users
LoginHub (until you get to MC)
Service requesters in MCe
Service requesters in MC (these pages are built very different from the rest of MC)

What's the solution?

There is a set of temporary hack fixes that work, see the Chromium official statement above. It will work until the feature is removed entirely.

We have a permanent solution which solves this issue and gives you many other benefits, our "Desktop App for MC" which runs MC in a dedicated environment. This solution fixes this issue for all version of MC. The current version is in beta, but you can start with that and upgrade later. There is NO cost for this for all customers with their MC SMA through Asset Pro Solutions Inc. DB Maintenance Connection Canada or ITIQPro Inc.

Go straight to install it

Accruent will have a solution. We are waiting to hear back from them what their plans are and timing is.

That's not my issue:

If you have support with us (Asset Pro Solutions Inc. DB Maintenance Connection Canada or ITIQPro Inc.) reach out to us at support@MaintenanceConnection.ca, send us as much detailed info as you can - screen shots almost always help, and we'll point you to the best info we have on it and if not, will work with you to find the cause of the issue. Depending on the type of issue, if you are an on-prem customer (you decided you want to run your own servers) we may need early contact with your IT department.

Think about things like: - is this a new issue?

- did this 'just' start happening or has this been happening for a long time?

- is it only happening to some people?

- is it only happening on some devices?

Identify the problem accurately by gathering comprehensive details such as symptoms, frequency, severity, impact, and context. Use tools like screenshots, screen recordings, error messages, logs, or diagnostic tests to capture evidence, and document the software environment including the operating system, hardware, network, software version, and configuration. Again, providing screen shots where possible.

Whenever possible, Provide precise reproduction steps in a clear, numbered list so developers can recreate the issue. Include actual versus expected results to clarify if the behavior is a bug or a misunderstanding.

If you are going through one of our problems shooting guides, collect screen shots of your work step by step so we can confirm what you tried.

With MC, a common fix to 'new' issues is to clear the cache. This is easy off the 3 dot menu in the 'Desktop App for MC' and various in how it is done from browser to browser.