- Welcome BMC Customer Support Site Guest User
Knowledge Article
Remedy - Server - Upgrade to 9.1.04 displays warning about a localized Approval view not being imported: "RIKERROR] Exception from RIKJ command Definition import failed, code 2....\templates\fr\AP%Signature_"
Remedy - Server - Upgrade to 9.1.04 displays warning about a localized Approval view not being imported: "RIKERROR] Exception from RIKJ command Definition import failed, code 2....\templates\fr\AP%Signature_"
Remedy AR System Server
AR System
Remedy AR System Server
When upgrading ARS from v.9.1.02 to v.9.1.04 an Approval localized view fails to import and the installer shows warnings. The installation log shows: ............... LOG EVENT {Description=[[resultType=COMPLETED,exitCode=2]],Detail=[RIK command ( returned a RETURN code of 2, which was interpreted as a failure from RIKJ [RIKCOMMAND] LOAD_APPLICATION -C true -f D:....\ARSystem\approval\templates\fr\adf_approval_fr_def.xml -G 14400 -k 0 -l D:....\ARSystem -L true -n Approval-RIK_PostUpgradeInstall -N 7200 -t 3553 -u Action Request Installer Account -x {Server_name} -X 21600 [RIKERROR] Exception from RIKJ command Definition import failed, code 2 , filename - D:....\ARSystem\approval\templates\fr\AP%Signature_view.def]} ............... When trying to import the file: "...fr\AP%Signature_view.def" using DevStudio using “import in place” the following is displayed: ........... Duplicate VUI for the form; AP:Signature : <14816>, 389, ........... The API-SQL log shows: ...................... */ +IMP ARImport -- as user {Username} from Developer Studio (protocol 23) at IP address {IP_Address} using RPC // :q:0.0s */ SELECT e.fieldId, e.vuiId, e.propShort, e.propLong FROM FieldDisppropEntity e WHERE e.schemaId = :schemaId AND e.overlayGroup = :overlayGroup AND e.fieldId > 0, [170, 0] */ SELECT fieldId, vuiId, propShort, propLong FROM field_dispprop WHERE (((schemaId = 170) AND (overlayGroup = '0')) AND (fieldId > 0)) */ OK */ SELECT e.vuiId, e.propShort, e.propLong FROM VuiDisppropEntity e WHERE e.schemaId = :schemaId AND e.overlayGroup = :overlayGroup, [170,0] */ SELECT vuiId, propShort, propLong FROM field_dispprop WHERE (((schemaId = 170) AND (overlayGroup = '0')) AND (fieldId = 0)) */ OK */ SELECT e.fieldId, e.vuiId, e.propShort, e.propLong FROM FieldDisppropEntity e WHERE e.schemaId = :schemaId AND e.overlayGroup = :overlayGroup AND e.fieldId > 0, [170, 1] */ SELECT fieldId, vuiId, propShort, propLong FROM field_dispprop WHERE (((schemaId = 170) AND (overlayGroup = '1')) AND (fieldId > 0)) */ OK */ SELECT e.fieldId, e.vuiId, e.propShort, e.propLong FROM FieldDisppropEntity e WHERE e.schemaId = :schemaId AND e.overlayGroup = :overlayGroup AND e.fieldId > 0, [170, 0] */ SELECT fieldId, vuiId, propShort, propLong FROM field_dispprop WHERE (((schemaId = 170) AND (overlayGroup = '0')) AND (fieldId > 0)) */ OK */ SELECT e.vuiId, e.propShort, e.propLong FROM VuiDisppropEntity e WHERE e.schemaId = :schemaId AND e.overlayGroup = :overlayGroup, [170,1] */ SELECT vuiId, propShort, propLong FROM field_dispprop WHERE (((schemaId = 170) AND (overlayGroup = '1')) AND (fieldId = 0)) */ OK */ SELECT e.vuiId, e.propShort, e.propLong FROM VuiDisppropEntity e WHERE e.schemaId = :schemaId AND e.overlayGroup = :overlayGroup, [170,0] */ SELECT vuiId, propShort, propLong FROM field_dispprop WHERE (((schemaId = 170) AND (overlayGroup = '0')) AND (fieldId = 0)) */ OK */ -IMP FAIL ...................... |
AP:Signature localized view as 'Default Administrator View -[local]' is present as overlaid but is missing in the base form.
This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088 for more information about troubleshooting BMC products in containers. 1- Check in DevStudio as Base mode if the view is present as in base mode (not as ab overlay). 2- If in the base form the view is missing and only exists as an overlay, delete it at database level so it will be changed to an "unmodified" object view. 3- Restart AR System. 4- Import the DEF file again. The issue comes prior the upgrade where the base form for containing the view can be already missing. The above steps will help to overcome this scenario, however in order to be sure nothing else is left behind and to have the installer reporting a clean upgrade the steps will be: 1- Revert the database and file system again prior the upgrade. 2- Perform then the changes mentioned above in the Database for the view. 3- Then start installation again to upgrade.
|
Attachment(s):