Odoo Help


How to understand Traceback (most recent call last)?

on 3/7/13, 4:16 PM 18,005 views

Most people who start with OpenERP doesn't make the right set-up of the software. Because of the wrong set-up the systems often reacts with errors and long trace backs.

Those starters are by definition not experienced. So they don't understand what the trace back is trying to tell them.

A lot of more experienced users have also their problems in interpreting the trace backs.

Next step for both categories is to post the trace-backs on the forum with their cry for help. If this happens it pollutes our nice forum.

Is it an idea to make some kind of a guide: "How to read your trace back yourself". If one can read is self one can communicate more effective on this forum. I am not experienced enought to make such a guide. But I hope your answers will be a start.

On 3/11/13, 9:03 AM

We can look at the generic examples in the Python tutorial: http://docs.python.org/2/tutorial/errors.html

But I find this to generic.

I give an example of how it is done for an opensource CMS called plone.


In this case they give examples of trace backs and what is the cause. Is this available for OpenERP?


Hi ,

In order for you to understand the trace back , the best way is to learn python programming.

The trace backs are presented to all of us. Most of us are not programmers. And not Python programmers. There must be some smart things to look for which can be done by an intelligent person without programming knowledge. I am not looking for the "best" way but for the intelligent way.

on 3/11/13, 8:42 AM

About This Community

This platform is for beginners and experts willing to share their Odoo knowledge. It's not a forum to discuss ideas, but a knowledge base of questions and their answers.


Odoo Training Center

Access to our E-learning platform and experience all Odoo Apps through learning videos, exercises and Quizz.

Test it now

Question tools

0 follower(s)


Asked: 3/7/13, 4:16 PM
Seen: 18005 times
Last updated: 3/16/15, 8:10 AM