Post-upgrade fix for MADB service on Onpremise/Hybrid MateAgent

Known Issues
, , ,
1

:lady_beetle: Summary

After upgrading to Autom Mate v4.5.0 or v4.6.0, On Premise or Hybrid environments may encounter issues with the MADB service due to a mismatch in expected folder structure. This prevents the service from running with the latest data.

:package: Affected Versions

  • 4.5.0

  • 4.6.0

:test_tube: Steps to Reproduce

  1. After upgrade, MADB service continues to run but does not reflect updated data.

  2. Inspect the mateagent folder structure — both database and db folders may exist.

:white_check_mark: Expected vs :cross_mark: Actual

  • :white_check_mark: Expected: Upgrade updates the correct folder (db) used by MADB.

  • :cross_mark: Actual: Upgrade updates a different folder, leaving MADB with outdated content.

:wrench: Workarounds

  1. Stop MADB service from Windows Services.

  2. If a db folder already exists → copy all contents from database into db.

    • If no db folder exists → rename database → db.

  3. Restart the MADB service.

:clipboard: Environment

  • Deployment: On-Prem Autom Center / Hybrid MateAgent

  • OS: Windows

3 Likes