Skip to Content
Menu
This question has been flagged
3 Replies
6003 Views

Please help - I cant find any resolve for this ... 
Any-one else seen this ? 

I can't get into SETTINGS - it gives this error.


UncaughtPromiseError > OwlError

Uncaught Promise > An error occured in the owl lifecycle (see this Error's "cause" property)

OwlError: An error occured in the owl lifecycle (see this Error's "cause" property)

    at handleError (http://localhost:8069/web/assets/b145335/web.assets_web.min.js:916:101)

    at App.handleError (http://localhost:8069/web/assets/b145335/web.assets_web.min.js:1542:29)

    at ComponentNode.initiateRender (http://localhost:8069/web/assets/b145335/web.assets_web.min.js:1006:19)


Caused by: Error: "res.config.settings"."anglo_saxon_accounting" field is undefined.

    at Field.parseFieldNode (http://localhost:8069/web/assets/b145335/web.assets_web.min.js:7661:231)

    at http://localhost:8069/web/assets/b145335/web.assets_web.min.js:8539:865

    at visit (http://localhost:8069/web/assets/b145335/web.assets_web.min.js:4223:51)

    at visitChildren (http://localhost:8069/web/assets/b145335/web.assets_web.min.js:4222:171)

    at visit (http://localhost:8069/web/assets/b145335/web.assets_web.min.js:4223:129)

    at visitChildren (http://localhost:8069/web/assets/b145335/web.assets_web.min.js:4222:171)

    at visit (http://localhost:8069/web/assets/b145335/web.assets_web.min.js:4223:129)

    at visitChildren (http://localhost:8069/web/assets/b145335/web.assets_web.min.js:4222:171)

    at visit (http://localhost:8069/web/assets/b145335/web.assets_web.min.js:4223:129)

    at visitChildren (http://localhost:8069/web/assets/b145335/web.assets_web.min.js:4222:171)

Avatar
Discard
Best Answer

The error you're encountering seems to be related to an issue in the Odoo settings, particularly with the anglo_saxon_accounting field in the res.config.settings model. This could happen due to a variety of reasons, such as missing or incorrectly configured modules, issues with custom code, or data inconsistencies.

Here’s how you can troubleshoot and potentially resolve this issue:

1. Check Installed Modules

  • Issue: The anglo_saxon_accounting field is related to the Anglo-Saxon accounting method, which is part of the Odoo accounting module.
  • Solution: Ensure that the accounting module is correctly installed. If you have uninstalled or updated any modules recently, try reinstalling or upgrading them to see if it resolves the issue.

Steps:

  • Go to Apps and search for account_accountant.
  • Ensure it is installed and up to date.

2. Disable Custom Modules

  • Issue: If you have custom modules or code that extends or modifies the res.config.settings model, it might be causing the issue.
  • Solution: Temporarily disable custom modules to see if the issue persists. If the issue is resolved after disabling a module, you'll need to inspect the custom code for any problems.

Steps:

  • Go to Apps.
  • Filter by Installed Modules.
  • Uninstall or disable custom modules one by one to identify the problematic one.

3. Check for Data Inconsistencies

  • Issue: There might be data inconsistencies or corruption in the database, particularly in the ir.model.fields table where field definitions are stored.
  • Solution: Check the ir.model.fields table for the anglo_saxon_accounting field and ensure it exists and is correctly defined.

Steps:

  • Access the Odoo database using a database manager like pgAdmin.
  • Run a query on the ir.model.fields table:
    sqlCopy codeSELECT * FROM ir_model_fields WHERE name = 'anglo_saxon_accounting' AND model = 'res.config.settings';
    
  • Verify if the field is present and correctly configured.

4. Clear Cache and Rebuild Assets

  • Issue: Cached assets or outdated files might be causing the issue.
  • Solution: Clear the cache and rebuild the web assets to ensure you're working with the latest version of the code.

Steps:

  • Go to Settings > Technical > Actions > Reload.
  • Alternatively, you can run the following command from your terminal:
    bashCopy code./odoo-bin -c /etc/odoo/odoo.conf -d your_database_name -u all --stop-after-init
    
  • This will update all modules and rebuild the assets.

5. Inspect the Odoo Logs

  • Issue: Detailed error logs might provide more insight into what's going wrong.
  • Solution: Check the Odoo server logs to see if there are any additional error messages or stack traces that can help identify the issue.

Steps:

  • Access the logs typically found in /var/log/odoo/ or wherever your Odoo instance is configured to store logs.
  • Look for errors around the time you try to access the Settings module.

6. Update Odoo

  • Issue: There might be a bug in your current version of Odoo.
  • Solution: Ensure that you are running the latest stable version of Odoo.

Steps:

  • Run the following command to update your Odoo instance:
    bashCopy codegit pull origin 
    ./odoo-bin -c /etc/odoo/odoo.conf -d your_database_name -u all --stop-after-init
    

7. Restore from Backup

  • Issue: If none of the above solutions work, the issue might be too complex to resolve directly.
  • Solution: Consider restoring the database from a backup taken before the issue occurred.

Steps:

  • Access your backups and restore the database to a point where the issue wasn’t present.
  • Test to ensure the issue is resolved.

8. Seek Professional Support

  • Issue: If you're unable to resolve the problem on your own, it may be necessary to consult with a professional.
  • Solution: Contact Odoo support or a certified Odoo partner to help diagnose and fix the issue.

By following these steps, you should be able to identify and resolve the error preventing you from accessing the Settings module in Odoo.

Avatar
Discard
Author Best Answer

Thank you so much ! 
I can confirm this worked ! 

SOLUTION FOR this error: 
connect to odoo database using terminal and run this sql:

DELETE FROM ir_ui_view WHERE arch_db::text LIKE '%anglo_saxon_accounting%';

Avatar
Discard