We faced a similar issue at a client site when trying to update an existing Task for a Change record.

Such an error also comes when you assigning value (manually or via workflow) to a currency field using a currency which is no available to that field (e.g. setting AUD value to a field which has USD and does not have AUD as a allowable/functional currency)

It turned out that the Set-field destination fields "Actual Cost" and "Budget Cost" field on the Task form did not have AUD as a currency in our case, but the source fields on the CHG form had AUD as default.

So if the system was fine without any currency conversion ration records, and now you are getting the ARERR 360, it would be worth while looking at the workflow log to find out currency mismatches.

Another note to add to this - after adding entries to the Currency Ratio form within a Server Group environment, you must allow a few hours to allow the Server Group members to synchronise and cache this new data.

To resolve an issue on a recent customer site, I did a distinct scan of the CHG:Infrastructure Change form on currency fields to find all currency values that had been used, then added the respective currency ratios to the form.

I had forgotten about this issue we have, thanks Sumeet and Ash for keeping the thread alive, your comments made me receive notifications about the thread and I begun the troubleshooting again I've now found and fixed this in our environment.

During install of the ITSM 7.6 environment the currency was set to EUR (I've checked logs and install documentation). For some reason some currency fields was not set to the EUR format but was still with the USD format.

During the upgrade to ITSM 8 the currency was set to EUR and this time the currency field(s) received the correct format/currency.