Skip to main content

Before You Upgrade MagicINFO Server: Pre-Check

When you run a newer MagicINFO Server installer over an existing installation, it first checks whether the computer is ready for the new version. If the check fails, the upgrade does not start. This page lists what to prepare so the check passes, what to back up, and what to do if the installer stops. The upgrade itself is walked through in Updating MagicINFO Server.

What the installer checks​

Recent MagicINFO Server 9 installers run a status-check step that inspects the server PC before anything is changed. According to Samsung's release notes:

  • the check itself needs .NET Framework 4.0 or later on the server;
  • MagicINFO Server must be installed from a Windows administrator account, which applies to upgrades as well.

After the system checks, the installer connects to the existing database with the database credentials it has stored. If that connection fails, it stops; see When the installer stops at the database step.

Pre-upgrade checklist​

  • Read the release notes of the target build. They list the supported databases and any extra conditions for that build.
  • Check the database version. For the recent builds 21.1090.1, 21.1091.1 and 21.1092.3, Samsung's release notes require PostgreSQL 15.x when you upgrade a PostgreSQL-based server. On an older PostgreSQL, back up the MagicINFO database, install PostgreSQL 15.x, restore the backup, and only then run the MagicINFO installer. (Build 21.1092.3 also adds support for PostgreSQL 18 and Microsoft SQL Server 2022 and 2025.)
  • Update display firmware first, where the notes ask for it. The notes for 21.1090.1 say all players should run their latest firmware before the server moves to that build.
  • Check your maintenance license. On MagicINFO Server 9, when a paid Unified Player license is registered, a major version released after the maintenance license expired runs with feature restrictions. See Manage Licenses.
  • Know your database credentials. Have the MagicINFO database user ID and password, and the PostgreSQL administrator password, from the original installation at hand.
  • Back up. Take a backup of the magicinfo database and copies of the conf, runtime and tomcat folders under C:\MagicInfo Premium, or a snapshot of the whole server. The steps are in Updating MagicINFO Server.
  • List your local changes. An upgrade can replace files in the installation folder. Note anything you edited by hand, such as the HTTPS connector in server.xml or values in config.properties, so you can check them afterwards.
  • Plan a maintenance window. The service is stopped during the upgrade, and the web console needs several minutes (allow about ten) after the installer finishes before it answers again. Displays reconnect on their own once it is back.

When the installer stops at the database step​

A failure we have seen in practice: the installer stops the service, passes the system checks, then fails when it connects to the database. The installer's log files in the installation folder (for example MyInstallLog_<version>.txt) show lines such as:

28P01: password authentication failed for user "postgre"
[FAIL] DB Connect Check

28P01 is PostgreSQL's code for a rejected user name or password. In the case we saw, the installer was using the user name postgre while the database user was postgres.

What it means for you:

  • Nothing was changed. The installer stops before writing the new version, so the old build is still in place. If the MagicINFO service is not running afterwards, start it again from Services.
  • Fix the credentials, then rerun. Make sure the database user name and password the installer uses match the real database account, then run the installer again.

After the upgrade​

  1. Sign in and read the version shown at the bottom of the sign-in page or in the dashboard footer. Other ways to read it: Finding the MagicINFO Version.
  2. You can also open http://<server>:7001/MagicInfo/openapi/auth?cmd=isMagicInfo (or the https / 7002 form). It returns the build as a short number, for example 211070.0 for build 21.1070. If it still shows the old number, the upgrade did not complete.
  3. Check that settings, content, schedules and devices look as they did before.
  4. Re-check the local changes on your list, starting with the HTTPS connector; see Change the MagicINFO HTTPS (TLS) Certificate.
  5. Watch the device list for a few minutes: displays should show as connected again. A display that took a firmware update before the upgrade may need a full power cycle before it reconnects.

Checked against Samsung's release notes for builds 21.1090.1 to 21.1092.3, October 2026.

Last updated on