[RESOLVED] CiviVolunteer install fails with DB Error: No Such Field

[narayanis]

I've attempted to install the extension on 4.4.0, and it fails when inserting a report instance record. The SQL fails when inserting into civicrm_report_instance.args. That field doesn't exist in the table, so it would definitely fail. I searched through all the Civi upgrade scripts to see when the table was altered to add this field, but it doesn't appear to be in there anywhere. Is it safe to just alter the table and add the field? If so, what's the data type?

As a side note, could this be the same reason one of my dashboards is now blank after the upgrade from 4.3 to 4.4?

[Coleman Watts]

Looking at our schema, that field should exist - looks like it's been there since version 3.2:

Code: [Select]

      <name>args</name>
      <title>Report Instance Arguments</title>
      <type>varchar</type>
      <length>255</length>
      <comment>arguments that are passed in the url when invoking the instance</comment>
      <add>3.2</add>

[narayanis]

We've been using Civi since prior to 3.2, so perhaps that change didn't make it into one of the upgrade scripts? I'll alter the table to add the field. Thanks!

[narayanis]

It was actually missing the 'name' field as well. After altering the table to add these fields, CiviVolunteer installed without issue. Thanks!

[FrTommy]

narayanis,

I had a similar issue where i kept getting field not exits errors after an upgrade. After much headache and searching I figured out that over the years an upgrade here or there had failed to properly upgrade the db which was causing all kinds of errors.

It's IMHO a good idea to start with a fresh db every few upgrades. These are the steps I took to ensure my db schema was correct. ( My issue was upgrading from 4.3.3 to 4.3.5)

Here's what I did. I took the 4.3.3 db and exported the STRUCTURE only then grabbed the civicrm.mysql file from the 4.3.3 release and imported that into a clean db and then exported the STRUCTURE only of that. I then used a diff tool and looked at them. there were several inconsistencies that were probably the issues. I then took and did a DATA only dump of the 4.3.3 db minus the custom tables. Then took and did a structure dump of the custom tables and then a data dump of the custom tables.

That gave me 3 files: DATA of custom and other tables and STRUCTURE of custom tables.

I imported the structure of the custom tables into the clean 4.3.3 db then the DATA of the custom tables and then the DATA of the rest of the db.

Then I downloaded 4.3.5 and held my breath and ran the upgrader. It upgraded perfectly with no errors.

I found these steps at:  http://wiki.civicrm.org/confluence/display/CRMDOC/Ensuring+Schema+Integrity+on+Upgrades

[narayanis]

Thanks for the advice. There were a few small schema changes here and there for features we don't use, but everything is merged in, and it's good to know our database is now in a happy place!