MxManagement Center Issues

ManagementCenter MxMC- Discussion
,
1

Hello,

We have a project file with around 650 cameras. Recently we’ve run into a several issues:

  1. When we upgrade to the latest version of MxManagement a good amount of our cameras aren’t viewable. It would just so a blank grey screen but doesn’t state it isn’t connected. If i roll back to and older version like 2.7 the cameras work again.

  2. We tried to create a new project file from scratch to reduce the size of older one as with the amount of thumbnails, it was a GB in size. After creating the new project file, we set two user environments (user and superadmin). It can open in user but if you switch to superadmin, MxManagement just crashes. I’ve had to delete the project.data and user file in %appdata% to get it to open properly again.

Then with the new project file, it will open fine on one computer but then on another computer crash. The only way to open is to run MxManagement as an admin.

Any insight would be appreciated

2

Thanks for the detailed description.

Based on the information provided, I would not immediately assume that the number of cameras is the root cause. MxManagementCenter is regularly used in significantly larger installations. We have deployments with well over 4,000 cameras managed through MxMC, so a general limitation of MxMC 2.8/2.9 with ~650 cameras can largely be ruled out.

From my experience, complexity increases much more with:

  • Multiple MxMC workstations

  • Many users with different permissions

  • Individual workstation configurations

  • Long project histories that have been migrated across multiple MxMC versions

A few observations:

1. Different behavior on different PCs

The fact that the newly created project works correctly on one PC but crashes on another strongly suggests a workstation-specific issue rather than a project file issue.

Typical hardware-dependent areas in MxMC are:

OpenGL

  • MxMC relies heavily on graphics acceleration.

  • Graphics driver differences can lead to grey camera tiles, rendering issues, or application crashes.

  • As a test, try disabling OpenGL acceleration in MxMC and verify whether the behavior changes.

Audio subsystem

  • Audio handling depends on both Windows audio services and the installed audio hardware/drivers.

  • In some environments, changing the audio backend or temporarily disabling audio support in MxMC can help identify whether audio initialization is contributing to the crash.

It would therefore be useful to compare:

  • GPU model

  • Graphics driver version

  • Audio hardware and drivers

  • Windows version/build

between a working and a non-working workstation.

2. User roles vs. Environments

The description is slightly unclear regarding the terms used.

In MxMC there are:

  • Environments (for example Office, Home Office, Remote Site, etc.)

  • User categories such as User, Supervisor and Administrator

There is no standard “SuperAdmin” role in MxMC, and “User Environments” are typically unrelated to user permissions.

Could you clarify whether:

  • You are switching between different Environments?

  • Or between different MxMC user accounts/permission levels?

This distinction is important because it changes where we would look for the root cause.

3. Local profile and configuration files

The fact that deleting the local project and user configuration files restores functionality is a strong indication that the issue may be related to local profile data rather than camera connectivity.

Particularly relevant is that:

  • The project opens successfully after resetting local configuration files.

  • The issue reappears after switching configurations.

  • Running MxMC as Administrator changes the behavior.

This points toward:

  • Corrupted local configuration data

  • Windows permission issues

  • Driver-related initialization problems

  • Environment-specific configuration conflicts

4. Grey camera tiles after upgrading

Since the affected cameras become visible again after rolling back to MxMC 2.7, it initially appears more likely that something in the existing configuration was not migrated correctly when moving to the newer MxMC version.

One area worth considering is the Environment configuration. In MxMC, a camera can be reached through different addresses depending on the selected Environment. For example:

  • Environment “Home” may use a local 192.168.x.x address

  • Environment “Office” may use a DynDNS or public address

If Environment assignments, address mappings, or related configuration data were affected during the upgrade, this could potentially explain why some cameras appear unavailable in newer versions.

However, since you mentioned that a newly created project/configuration works, I would currently treat this as a secondary hypothesis and focus first on workstation-specific configuration, local profile data, and hardware/driver-related differences between the affected PCs. If the issue can be reproduced consistently with the same project file and Environment settings, further investigation of the Environment configuration would be worthwhile.

Additional information that would help

  • Exact MxMC version where the issue first appeared

  • Windows version/build

  • GPU model and graphics driver version

  • Whether OpenGL acceleration is enabled

  • Whether the same cameras are always affected

  • Crash information from Windows Event Viewer

  • Clarification regarding “SuperAdmin” and the environment setup

At the moment, the symptoms point more towards workstation-specific configuration, graphics/audio driver interaction, or local profile handling than towards the project size itself.

3

The symptoms are a better indicator of a workstation-specific MxMC issue than the number of cameras. Since the project runs on one PC but not the other, I would compare GPU drivers, OpenGL settings, Windows builds and local MxMC profiles.

If you are able to delete the local configuration files and restore the game, it’s a good indication that you either have corrupted MxMC profile data, or a driver conflict.