Sean Reifschneider wrote: > It sounds like the database wasn't updated correctly. Try manually running > the "vpm-dbupgrade" script. That fixed it, thanks. w