Working tryton suddenly started giving error on Reporting

[Dr. Praveen Bhatia]

Hi,

  I was successfully running some proteus scripts and seeing the financial reports. 

  For testing, I shut down the server, rebuilt the database and ran the same proteus script. 

  On clicking Financials->Reporting-> Any of the submenus

I get errors like this: 

Traceback (most recent call last):

  File "/trytond/wsgi.py", line 47, in dispatch_request

    return endpoint(request, **request.view_args)

  File "/trytond/protocols/dispatcher.py", line 59, in rpc

    request, database_name, *request.params)

  File "/trytond/wsgi.py", line 39, in auth_required

    return wrapped(*args, **kwargs)

  File "/trytond/protocols/dispatcher.py", line 40, in wrapper

    return func(request, pool, *args, **kwargs)

  File "/trytond/protocols/dispatcher.py", line 177, in _dispatch

    obj, method = get_object_method(request, pool)

  File "/trytond/protocols/dispatcher.py", line 162, in get_object_method

    return pool.get(name, type=type), method

  File "/trytond/pool.py", line 172, in get

    return self._pool[self.database_name][type][name]

KeyError: u'account.general_ledger.account.context'

===========================

I dont think I changed anything from the working program, So why this sudden change in behavior? Does some old data get stored somewhere and gets corrupted? Do I need to re-clear some area, OR re install some modules?

[Cédric Krier]

You probably did not activate the account module on this new database.

--
Cédric Krier - B2CK SPRL
Email/Jabber: cedric...@b2ck.com
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/

[Dr. Praveen Bhatia]

> I dont think I changed anything from the working program, So why this
> sudden change in behavior? Does some old data get stored somewhere and gets
> corrupted? Do I need to re-clear some area, OR re install some modules?

You probably did not activate the account module on this new database.

--

I think proteus script activates (installs the account module). 

However, this problem luckily got solved this way  :

Tried

trytond -d newdb --dev

This gave an error and exited (On my workstation the error is always there - None type doesnt have getstart() or something like that)

However, after that returning to trytond -d newdb, the same program runs correctly. 

Perhaps luckily, tyring the --dev option did something right, but I don't know what.