Error-Exception from HRESULT: 0xFFFFFC17

[beehoiphoebe_yeo]

Here’s the summary of the issue:

• SAP Business One 9.1 (9.10.180) PL: 08 (32-bit)
• The customer had been using this add-on for many years, suddenly they encounter the error when update the ‘Approval Configuration’ and ‘Approval Exemption’, the error message is as the following:
• oError when update the ‘Approval Configuration’: [SaveData] : Exception from HRESULT: 0xFFFFFC17, I have attached the print screen of the error for your reference

  

• oError when update ‘Approval Exemption’: [UpdateExemption] : Exception from HRESULT: 0xFFFFFC17, I have attached the print screen of the error for your reference

  

• The issue happens to all PC, all database and all users
• We tried to duplicate the live DB to test DB also encounter the same error
• The issue happen randomly at all DB, sometime can update and sometime cannot update, even we tried when no users are accessing SAP, it also the same.
• We have checked the transactions, add-on source code and stored procedure, all looks fine
• We have checked the HANA resources, hard disk, CPU and memory, it looks fine.
• We have restarted the NDB and server tools, but it still the same
• I found similar error in the forum https://archive.sap.com/discussions/thread/3348286 , we checked the customer database, there is no UDO, UDT or UDF created recently. So, the cause is no applicable to the customer environment
• I also found this in the forum https://archive.sap.com/discussions/thread/9421 , it says the UDF value more than the characters allowed, we have checked the customer data, there are no transactions with UDF value more than the characters allowed.
• We search SAP note ‘Exception from HRESULT’ or ‘0xFFFFFC17’, can't find much information, except these two SAP note 2329423 and 2472534, but not related to the customer environment.
• We found SAP note 1988581 - Unable to update UDT, however the note mentioned is relevant to SAP Business One 9.0, the customer is in 9.1

Any idea what could be the cause of the issue?

[beehoiphoebe_yeo]

The issue resolved after restarted Linux server.

Don't understand the logic though.