Error when doing update.php

I have not been able to reproduce that. Where you updating from backup and migrate v.1.x or from a different 2.x dev release?

Hi. I got the same error:

"An error occurred. http://localhost/..../update.php?id=20&op=do
Fatal error: Cannot access empty property in C:\Program Files\xampp\htdocs\....\sites\default\modules\backup_migrate\includes\crud.inc on line 355"

when trying to upgrade from
6.x-1.2 to 6.x-2.x-dev

I'm having the same issue as the original post, running update.php after installing 6.x-2.x-dev, snapshot dated 9/27 and downloaded today.

An error occurred. http://[site]/update.php?id=10&op=do <br /> <b>Fatal error</b>: Cannot access empty property in <b>/var/www/vhosts/[sitepath]/sites/all/modules/backup_migrate/includes/crud.inc</b> on line <b>355</b><br />

Version 6.x-1.2 works just fine for me, but I'm trying to figure out how to use http://drupal.org/project/backup_migrate_profile

There's nothing in my error log or watchdog table. Rerunning update.php returns the following warnings, but also indicates that all queries were executed successfully (blockquote).

Warnings:

    * user warning: Table 'backup_migrate_profiles' already exists query: CREATE TABLE backup_migrate_profiles ( `profile_id` VARCHAR(32) NOT NULL DEFAULT '0', `name` VARCHAR(255) NOT NULL, `filename` VARCHAR(50) NOT NULL, `append_timestamp` TINYINT unsigned NOT NULL DEFAULT 0, `timestamp_format` VARCHAR(14) NOT NULL, `filters` TEXT NOT NULL, PRIMARY KEY (profile_id) ) /*!40100 DEFAULT CHARACTER SET UTF8 */ in /var/www/vhosts/[sitepath]/httpdocs/includes/database.inc on line 529.

    * user warning: Table 'backup_migrate_destinations' already exists query: CREATE TABLE backup_migrate_destinations ( `destination_id` VARCHAR(32) NOT NULL DEFAULT '0', `name` VARCHAR(255) NOT NULL, `type` VARCHAR(32) NOT NULL, `location` TEXT NOT NULL, `settings` TEXT NOT NULL, PRIMARY KEY (destination_id) ) /*!40100 DEFAULT CHARACTER SET UTF8 */ in /var/www/vhosts/[sitepath]/httpdocs/includes/database.inc on line 529.

    * user warning: Table 'backup_migrate_schedules' already exists query: CREATE TABLE backup_migrate_schedules ( `schedule_id` VARCHAR(32) NOT NULL DEFAULT '0', `name` VARCHAR(255) NOT NULL, `source_id` VARCHAR(32) NOT NULL DEFAULT 'db', `destination_id` VARCHAR(32) NOT NULL DEFAULT '0', `profile_id` VARCHAR(32) NOT NULL DEFAULT '0', `keep` INT NOT NULL DEFAULT 0, `period` INT NOT NULL DEFAULT 0, `last_run` INT NOT NULL DEFAULT 0, `enabled` TINYINT unsigned NOT NULL DEFAULT 0, `cron` TINYINT unsigned NOT NULL DEFAULT 0, PRIMARY KEY (schedule_id) ) /*!40100 DEFAULT CHARACTER SET UTF8 */ in /var/www/vhosts/[sitepath]/httpdocs/includes/database.inc on line 529.

Query status:

The following queries were executed
backup_migrate module
Update #2000

* No queries

Update #2001

* ALTER TABLE {backup_migrate_profiles} ADD `source_id` VARCHAR(32) NOT NULL DEFAULT 'db'

Update #2002

* No queries

Update #2003

* ALTER TABLE {backup_migrate_schedules} CHANGE `profile_id` `profile_id` VARCHAR(32) NOT NULL DEFAULT '0'

Update #2004

* ALTER TABLE {backup_migrate_destinations} CHANGE `destination_id` `destination_id` VARCHAR(32) NOT NULL DEFAULT '0'
* ALTER TABLE {backup_migrate_profiles} CHANGE `profile_id` `profile_id` VARCHAR(32) NOT NULL DEFAULT '0'
* ALTER TABLE {backup_migrate_schedules} CHANGE `schedule_id` `schedule_id` VARCHAR(32) NOT NULL DEFAULT '0'

Update #2005

* UPDATE {backup_migrate_profiles} SET source_id = 'db' WHERE source_id = 'db_url:default'
* UPDATE {backup_migrate_schedules} SET destination_id = 'db' WHERE destination_id = 'db_url:default'
* UPDATE {backup_migrate_profiles} SET source_id = REPLACE(source_id, 'db_url:', 'db:')
* UPDATE {backup_migrate_schedules} SET destination_id = REPLACE(destination_id, 'db_url:', 'db:')
* ALTER TABLE {backup_migrate_profiles} DROP source_id

I'm still not able to reproduce this, but I've added some code which should hopefully mitigate it.

Thanks.

I just encountered the same error. removing ver 2.x-dev and installing the previous version works.

This problem is maybe caused by a wrong configuration of $base_url and should be prevented by inserting a warning message to the requirements system. Therefore I created a new issue #1046682: Install/Update process fails if $base_url is set to a wrong URL. Please close this bug as a duplicate, if this solves your issue. Thanks!