CiviCRM Community Forums (archive)

I have done the upgrade to 3.2.1 because of this issue http://forum.civicrm.org/index.php/topic,14816.msg63934.html#msg63934; thanks for the fix.

However, I had a failure on the upgrade.  

DB Error: already exists

Database Error Code: Duplicate key name 'UI_activity_type_id', 1061
This is a CiviCRM instance that I have run since at lease version 1.6, and have managed to squeak through some upgrade schema issues.  Perhaps this is another legacy upgrade schema issue?

In testing after-wards the CiviMail module appears broken
Sorry. A non-recoverable error has occurred.

Invalid response code received from SMTP (outbound mail) server while attempting to send email. This is often caused by a misconfiguration in the CiviCRM Outbound Email settings. Please verify the settings at Administer CiviCRM >> Global Settings >> Outbound Email (SMTP).
Checking the global settings SMTP, just opening the settings and hitting the "Save and Send Test Email" still seems to be fine.
Your SMTP settings are correct. A test email has been sent to your email address.
Any ideas, please?

As for your smtp error: might be that your smtp server doesn't allow to have a different/custom sender. Do check what you have configured in the bounce (the default mailbox)

And do try to use php mail instead of smtp, might work better.

http://en.flossmanuals.net/CiviCRM/SystemConfiguration

As for your smtp error: might be that your smtp server doesn't allow to have a different/custom sender. Do check what you have configured in the bounce (the default mailbox)

And do try to use php mail instead of smtp, might work better.

http://en.flossmanuals.net/CiviCRM/SystemConfiguration

Has the 3.2.0 to 3.2.1 version introduced changes that are expected to confound an existing working SMTP configuration?

Well I did have bounces working with SMTP because occasionally when there was a problem with the SMTP, all my recipients would go on hold.

However, changing from SMTP to Mail has resolved this issue.  I am now able to send out again.

I see, no I hadn't set up the EmailProcessor.php.

Another change to the 3.2.1/3.2.0 has meant that although my existing cron for civimail.cronjob.php does not produce errors, neither does the queue get processed now.  Everything stays as either Scheduled or Running.  I have to manually push the queue (./civicrm/mailing/queue) now. To get a message out. 

Yep, we got the same issue going from 3.1.5 to 3.2.1.

 * DB Error: already exists
 * Database Error Code: Duplicate key name 'UI_activity_type_id'

Pity the error is fatal (especially when it's just trying to create an index which already exists, and there's no real error to be worried about).

MySQL doesn't have a CREATE INDEX IF NOT EXISTS so this isn't something which can be handled at SQL level, unfortunately.

The resulting DB state is inoperational under both 3.1.x and 3.2.x, so we're lucky it was just a trial run.

I am just upgrading from Civi 2.0.7 on Drupal 5.x and just bumped into this "Database Error Code: Duplicate key name 'UI_activity_type_id', 1061"

Mind sharing a work-around for this situation so we can get our site back up?

*** Update: I went looking in the "issue tracker" for the 3.2.2 release and see nothing which looks related to the issue described here.

All right, I will "hold on"... 

I guess this is what I get for going ahead and trying the 3.2x branch already! (head shaking)