After running update.php, got this? Normal? (UR)

Hmm there should not have been any errors. What is the version of mysql you're using, and if it MyISAM or perhaps InnoDB (not tested this one). Also, what version did you update from, just in case. Thanks.

I'm also seeing this error with the Feb 28 dev update (updating from the Feb 27 dev version):

user warning: Incorrect table definition; there can be only one auto column and it must be defined as a key query: ALTER TABLE user_relationships DROP INDEX rid in /var/www/vhosts/domain.com/httpdocs/includes/database.mysql-common.inc on line 448.

user warning: Duplicate key name 'rid' query: ALTER TABLE user_relationships CHANGE rid `rid` INT NOT NULL auto_increment, ADD INDEX rid (rid) in /var/www/vhosts/domain.com/httpdocs/includes/database.mysql-common.inc on line 520.

user warning: Table 'user_relationship_type_roles' already exists query: CREATE TABLE user_relationship_type_roles ( `rtid` INT unsigned NOT NULL DEFAULT 0, `rid` INT unsigned NOT NULL DEFAULT 0, PRIMARY KEY (rtid, rid), INDEX rtid (rtid) ) /*!40100 DEFAULT CHARACTER SET UTF8 */ in /var/www/vhosts/domain.com/httpdocs/includes/database.inc on line 515.

and

user_relationships_api module
Update #6100
Failed: ALTER TABLE {user_relationships} DROP INDEX rid
Failed: ALTER TABLE {user_relationships} CHANGE rid `rid` INT NOT NULL auto_increment, ADD INDEX rid (rid)

Update #6101
Failed: CREATE TABLE {user_relationship_type_roles} ( `rtid` INT unsigned NOT NULL DEFAULT 0, `rid` INT unsigned NOT NULL DEFAULT 0, PRIMARY KEY (rtid, rid), INDEX rtid (rtid) ) /*!40100 DEFAULT CHARACTER SET UTF8 */

I had the same error. Do you have xmlsitemap installed? Uninstall xmlsitemap and the error went away.

I do have xmlsitemap installed. Un-installing it is not an option or a solution.

I wonder if it's because you picked up the dev release with an incorrect update_N function in it. I by mistake added an update_6200 function whereas it should have been update_6101. It was corrected in CVS on Feb 27, see http://drupal.org/node/228206#comment-1299746
But if you did the 6200 update, and then tried to update again, I guess it tried to apply the changes twice which is a problem. Since you get in your error logs "Table 'user_relationship_type_roles' already exists " it looks like that's what happened.

Pls update.php again and see which updates are available. If user_relationships_api shows that none are available, then you are at 6101 already and there is nothing to be done. I have just tested this "update" from 6200 to 6101, and after the errors you posted everything's fine. There is no need to disable any other modules, i think. Sorry about the trouble.

Marking fixed, please reopen if you still have issues.