| Description | This article describes how to fix the issue preventing remote TACACS+ administrators from editing/modifying application control security profile due to 'Error ending transaction'. |
| Scope |
FortiGate v7.4.1, v7.4.2, v7.4.3. |
| Solution |
The error message 'Error ending transaction' appears when attempting to modify the Application Control Security Profile by navigating to Security Profile -> Application Control -> Edit -> Application and Filter Overrides- > Create New -> Select a signature and select 'Ok' -> Ok.
The following error is seen when 'Edit in CLI' is selected from GUI:
config application list Can not config the object since either the object or the referenced objects are being configured by other transactions. Command fail. Return code 14
In the httpsd debugs, the error message 'Error ending transaction' is seen as shown below:
diagnose debug application httpsd -1 2023-11-10 15:21:58 [httpsd 20037 - 1699629718 info] endpoint_process_req_vdom[1070] -- new API request (action='select',path='system',name='debug',vdom='root',user='Trustmarque') 2023-11-10 15:21:58 [httpsd 20037 - 1699629718 warning] JavaScript -- No language entry found for "Error ending transaction." window.FOS_LIB</Lang.prototype.translate@ https://10.6.5.11/9cb69a312b4e367b37b1e85a92ef932e/ng/app.js:25:152040 lang@ https://10.6.5.11/9cb69a312b4e367b37b1e85a92ef932e/ng/app.js:238:369452 notify_failure@ https://10.6.5.11/9cb69a312b4e367b37b1e85a92ef932e/ng/app.js:25:575015 2023-11-10 15:21:58 [httpsd 20037 - 1699629718 warning] JavaScript -- Possibly unhandled rejection: {"user_notified":"error","request":{"data":{"http_method":"POST","revision":"51552d1337 6e88ac91216ef683ffd98b","revision_changed":false,"error":-37,"status":"error","http_status":500,"vdom":"MAIN","action":"transaction-commit","serial":"F2K60FTKXXXXXXX","version":"v7.4 .1","build":2463},"status":500,"config":{"method":"POST","transformRequest":[null],"transformResponse":[null],"jsonpCallbackParam":"callback","url":"/api/v2/cmdb?action=transaction-commit" ,"data":"{\"transaction-id\":38}","headers":{"Accept":"application/json, text/plain, */*","Content-Type":"application/json;charset=utf-8","X-Requested-With":"XMLHttpRequest","X-CSRFTOKEN": "C3DA89392F1A575F5E32F388EB2C"},"params":{"vdom":"MAIN"}},"statusText":"","xhrStatus":"complete"},"message":"Error ending transaction.","cli_error":""} processChecks@ https://10.6.5.11/9cb69a312b4e367b37b1e85a92ef932e/ng/app.js:31:168711 $digest@ https://10.6.5.11/9cb69a312b4e367b37b1e85a92ef932e/ng/app.js:31:179398 26090/bootstrap/</</Rt<@ https://10.6.5.11/9cb69a312b4e367b37b1e85a92ef932e/main.js:1:2545895 2023-11-10 15:21:58 [httpsd 20037 - 1699629718 warning] JavaScript -- CMDBError: (Error ending transaction.) 2023-11-10 15:21:58 [httpsd 20037 - 1699629718 warning] JavaScript -- CMDBError: (Error ending transaction.)
This issue has been resolved in v7.4.4, v7.6.0
Workaround: Local admin can make changes to application control via the GUI without running into this issue. |
