FortiManager
FortiManager supports network operations use cases for centralized management, best practices compliance, and workflow automation to provide better protection against breaches.
jasonhong
Staff & Editor
Staff & Editor
Article Id 404756
Description

This article describes how to troubleshoot issues related to replacemsg in System Templates when trying to upgrade ADOM in FortiManager.

Scope FortiManager.
Solution

The user may encounter the following error message when attempting to upgrade the FortiManager ADOM.

 

Fail (errno=139):cannot be edited. object: object_name. detail: system replacemsg system_template. solution: static object can not create non-reserved record(s)

 

The error usually correlates with the 'replacemsg' object in the FortiManager System Templates. To resolve this, manually delete the 'replacemsg'object that is causing the ADOM upgrade error.

 

As per the screenshot below, it shows the object 'ztna-block' within the 'webproxy' replacemsg parameter in the system template is causing the ADOM upgrade issue.

 

upgradeadomfail.png

 

To resolve this, delete the 'ztna-block' object via Device Manager -> Provisioning Templates -> System Templates -> Edit 'system_template' -> CLI Configurations -> System -> replacemsg -> Webproxy -> Select 'ztna-block' -> Delete -> Save.

 

adomupgrade.gif

 

Related article:
Troubleshooting Tip: Check FortiManager system template errors