well, don't know what to say without seeing your app's code. The thing is, that kind of error is pretty "down the line" and usually is given by a wrong table structure or a completely locked down database. if you use another DAL connection (e.g., just to try, sqlite) does it raise the same exception ?
On Wednesday, January 20, 2016 at 9:48:05 PM UTC+1, Marcelo Huerta wrote: > > Niphlod decía, en el mensaje "[web2py] Re: Scheduler Tasks show TICKER: > error > assigningt task (0) and task never start" del 20/1/2016 17:42:40: > > all of the sudden or you just started it ? > > No, I just incorporated the Scheduler to my application. Previously I > wasn't > using it. It never worked from the moment I created the Scheduler object > and I > didn't know why until I started running manually the "web2py.py -K app" > (previously I was using the "-K app -X" parameters in my service so I > wasn't > seeing the errors). > > I've tried removing the *.table files for all the schedule* tables and > removed > them manually from the server using the backend console, and then > restarted > the admin app and ran the scheduler manually again, to no avail. > > -- > o-=< Marcelo >=-o > > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
