Maintenance Connection Everywhere (MCe) · EAM/CMMS manuals
All values are from Accruent unless otherwise stated. In particular if it says MCC: it means it was not listed by Accruent as working but we have done tests that show it does work. So for example, under Windows 2025 there are some that say "MCC: Yes, but email issues" which means We have tested and come to this conclusion. But others that say "Yes, but email issues"
Missing values are currently unknown
- Please be careful reading this. There are 3 products that use a year as part of the version name: Accruent aka MC 2025 which shipped in 2026
- Windows Server aka 2022
- Windows SQL server aka 2022
This chart is subject to change as we learn more
| MCe older | MCe 11 | MCe 12 | MC 8.8 and older | MC 8.9 | MC 2021 | MC 2022 | MC 2025 | MC 2026 | |
|---|---|---|---|---|---|---|---|---|---|
| Retired | Retired | Active | Retired | Retired | Retired | Retired | Active | Coming?In Development any notes are predictive not authoritative | |
| MCe | |||||||||
| 12.x | N/A | N/A | N/A | No, need MCe 10 or earlier | Yes | Yes | Yes | 12.10 | 12.x |
| MS SQL | Server: | ||||||||
| SQL 2008 R2, 90 | Yes | No | No | No | No | No | No | ||
| SQL 2012,110 | Yes | Yes | No | No | No | No | |||
| SQL 2014,120 | Yes | Yes | Yes | No | No | No | No | ||
| SQL 2016,130 | Unknown | Yes | Yes, minimum | No | No | ||||
| SQL 2017,140 | Unknown | Yes | Yes, minimum | No | No | ||||
| SQL 2019,150 | Unknown | Yes | Yes, maximum | Yes, minimum requirement | |||||
| SQL 2022, 160 | Unknown | Preferred | No | Preferred | Probably | ||||
| SQL 2025, 170 | Not tested | No | Untested | Probably | |||||
| Windows | Server | ||||||||
| 2014 | |||||||||
| 2016 | |||||||||
| 2019 | |||||||||
| 2022 | MCC: Yes, but email issues | MCC: Yes, but email issues | MCC: Yes, but email issues | Yes, but email issues | Probably | ||||
| 2025 | No | Probably | |||||||
| Linux | Server | ||||||||
| All versions | No | No | No | No | No | No | No | No |
Critical notes:
- Upgrading from SQL that is OLDER than 2017 to SQL 2017 or higher will kill MC until you run SQL scripts that re-activate the SQL CLR features and the .DLL
- MCe V12.1 detects 2016+ and uses more efficient queries.
- When upgrading from MC 2022 to MC 2025 you need to be running SQL 2019, the max allowed for MC 2022 and the min allowed for MC 2025.
- MC requires SQL server MUST be running the correct collation sequence, the US standard collation SQL_Latin1_General_CP1_CI_AS. Further discussion on Collation requirements
- SQL table and procedure type scripts target the VERSION of SQL. Select, Update, type scripts target the compatibility mode
eMail issues with Windows Server 2022 and newer
This only affects Accruent MC, this is not an issue for the MCe product family.
The requirement for Accruent supported for email to work has been the same since 2003: the customer (IT department) must provide a non-TLS non-authenticated SMTP gateway on port 25.
This applies to all known versions of MC from version 1.0 to MC2025 including some pre release testing of MC 2026 which is not even in alpha at time of writing.
Up until Windows Server 2022 (so all versions OLDER than Windows Server 2022) this was fairly easily met by most customers using the Windows email Relay server the built in "IIS SMTP Server".
- But this feature was made unsupported and deprecated with Windows Server 2022, and although some report it can be brought back through settings, there are also reports that maintenance upgrades turn in back off again and Microsoft states that some of their security updates may uninstall it making it very unreliable even if you can get it working temporarily. For all intents and purposes, it was removed with Windows Server 2022.
- For Windows Server 2022 and newer (as they become supported) you must provide a non-TLS non-authenticated SMTP gateway on port 25.
For most customers the easiest way is leveraging the MCe reliability email server which can be used as a relay server, allowing MC to call in and then MCe can (and in these cases must) use alternative methods to pass it on. As a bonus, you get the reliability features that MCe provides. This feature is provided at no extra charge for the software, only Professional Services for setting it and MC up to use it if you need that assistance.
Customers on Windows 2022+ who are not using the MCe reliability email server are responsible for finding a non-TLS non-authenticated SMTP gateway on port 25 to use with MC emails or only send emails using MCe.
Questions:
What happens if SQL Server is updated to MS SQL 2022 or higher before upgrading to MC 2025 or MC 2026?
- The 2025 upgrade will FAIL, this is not a possibility that Accruent supports.
- You must UNINSTALL SQL Server 2022 and install SQL Server 2019.
- If the ent or reg databases were upgraded to level 160 you must set them back to level 150 aka MS SQL Server 2019.
What happens if SQL Server is set to 2017 when trying to upgrade to MC 2025?
I'm hearing Cam say: The 2025 upgrade will FAIL, this is not a possibility that Accruent supports.
Your only option is:
1. Upgrade the SQL Server to EXACTLY 2019
2. Run the MC upgrade to MC 2025
3. Optional but recommended, Upgrade the SQL Server to 2022
What happens if SQL server is 2025
Unknown, probably will have 'some' problems.