Top Menu

Jump to content
Home
    Modules
      • Projects
      • Activity
      • Work packages
      • Gantt charts
      • Calendars
      • Team planners
      • Boards
      • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.
    • Help and support
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Enterprise support
    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
    Activity
  • Roadmap
  • Work packages
    Work packages
  • Gantt charts
    Gantt charts
  • Calendars
    Calendars
  • Team planners
    Team planners
  • Boards
    Boards
  • News
  • Forums

Content

You are here:
  1. Messages
Support Installation & Updates
  1. OpenProject
  2. Forums
  3. Support Installation & Updates
  4. Your query is erroneous and could not be processed.

Your query is erroneous and could not be processed.

Added by MIke Methe about 8 years ago

Hello,

I originally worked with a bitnami ova install of OpenProject. That server became unusabe and since it was dev, I built a new one and installed openproject using the package installer from the site. Centos 7, mysql (mariadb).

I restored the SQL dump to the new server after installing openproject.

I can see all projects and authentication works. What I cant see are work packages. When I try to either view some that I know existed OR try to create new ones, I see this:

Work packages could not be loaded. Your query is erroneous and could not be processed.

Anyone have any idea how I can fix this short of dumping the DB and starting over?

Thanks!


Loading...