Tools
Initialization error during upgrade of Web Help Desk
During the upgrade of Web Help Desk to 2026.2.1.x, an error was encountered that prevented the database upgrade from completing. The upgrade is recovering the Web Help Desk configuration, but is getting and Initialization Eroor.
First published date
Last published date
Overview
The upgrade error means Liquibase thinks there are two baseline changesets in 2026.1-baseline-complete.xml were modified after they already ran (checksum mismatch), so it refuses to continue.
Product section
Cause
The error means Liquibase thinks two baseline changesets in 2026.1-baseline-complete.xml were modified after they already ran (checksum mismatch), so it refuses to continue.
Resolution
Run the script that corresponds to the applicable database. Each script applies the two MD5SUM corrections within a single transaction.
Before running the script:
- Take a full database backup, or at a minimum, back up the DATABASECHANGELOG table.
- Stop the Web Help Desk (WHD) service.
- Run the script using the database user account that owns the WHD schema.
-- Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further
-- disclaims all warranties including, without limitation, any implied warranties
-- of merchantability or of fitness for a particular purpose. The risk arising
-- out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation,
-- production, or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits, business
-- interruption, loss of business information, or other pecuniary loss) arising
-- out of the use of or inability to use the scripts or documentation.
MySQL
-- Apply the corrections in a single transaction.
START TRANSACTION;
SET SQL_SAFE_UPDATES = 0; -- include this only if safe-update mode is on
UPDATE DATABASECHANGELOG
SET MD5SUM = '9:30263ca4482ea84a0de85440e62a5fe1'
WHERE ID = '1771864125027-5'
AND AUTHOR = 'Web Help Desk'
AND FILENAME = 'db/changelog/baseline/2026.1-baseline-complete.xml';
UPDATE DATABASECHANGELOG
SET MD5SUM = '9:f457c0be815073c655b9be7672561750'
WHERE ID = '1771864125027-136'
AND AUTHOR = 'Web Help Desk'
AND FILENAME = 'db/changelog/baseline/2026.1-baseline-complete.xml';
COMMIT;
PostgreSQL
-- Apply the corrections in a single transaction.
BEGIN;
UPDATE databasechangelog
SET md5sum = '9:30263ca4482ea84a0de85440e62a5fe1'
WHERE id = '1771864125027-5'
AND author = 'Web Help Desk'
AND filename = 'db/changelog/baseline/2026.1-baseline-complete.xml';
UPDATE databasechangelog
SET md5sum = '9:f457c0be815073c655b9be7672561750'
WHERE id = '1771864125027-136'
AND author = 'Web Help Desk'
AND filename = 'db/changelog/baseline/2026.1-baseline-complete.xml';
COMMIT;
Microsoft SQL Server
-- Apply the corrections in a single transaction. XACT_ABORT ensures a
-- rollback if anything unexpected happens.
SET XACT_ABORT ON;
BEGIN TRANSACTION;
UPDATE dbo.DATABASECHANGELOG
SET MD5SUM = '9:30263ca4482ea84a0de85440e62a5fe1'
WHERE ID = '1771864125027-5'
AND AUTHOR = 'Web Help Desk'
AND FILENAME = 'db/changelog/baseline/2026.1-baseline-complete.xml';
IF @@ROWCOUNT <> 1
BEGIN
ROLLBACK TRANSACTION;
RAISERROR('Expected 1 row updated for 1771864125027-5. Rolled back.', 16, 1);
RETURN;
END
UPDATE dbo.DATABASECHANGELOG
SET MD5SUM = '9:f457c0be815073c655b9be7672561750'
WHERE ID = '1771864125027-136'
AND AUTHOR = 'Web Help Desk'
AND FILENAME = 'db/changelog/baseline/2026.1-baseline-complete.xml';
IF @@ROWCOUNT <> 1
BEGIN
ROLLBACK TRANSACTION;
RAISERROR('Expected 1 row updated for 1771864125027-136. Rolled back.', 16, 1);
RETURN;
END
COMMIT TRANSACTION;
GO
- Stop the Web Help Desk (WHD) service.
- Click Retry