Koozali.org: home of the SME Server

Addressbook issues

Offline doublecaps

  • **
  • 24
  • +0/-0
Addressbook issues
« on: February 25, 2010, 08:37:34 PM »
We appearently have more people using webmail then I thought.
Last week the addressbook option stopped working.

Running SME 7.4


Whenever a user tries to browse the address book I receive the following error:
DB Error: no such field
While if I try to searchor browse the address book I receive the following message.
There was an error adding the new contact. Contact your system administrator for further help.

I tried browsing the forum and found a couple posts witht he same error message but they all made reference to this happening after an upgrade. We have been runinng on the same version for a while and hadn't had any issues.

This is the "messages" log from the server
Quote
Feb 25 15:25:09 mail slapd[4452]: conn=1870 op=0 RESULT tag=97 err=0 text=
Feb 25 15:25:09 mail HORDE[10260]: [turba] DB Error: no such field: INSERT INTO turba_objects (object_type, object_firstname, object_lastname, object_middlenames, object_nameprefix, object_namesuffix, object_alias, object_bday, object_spouse, object_anniversary, object_children, object_photo, object_homestreet, object_homepob, object_homecity, object_homeprovince, object_homepostalcode, object_homecountry, object_workstreet, object_workpob, object_workcity, object_workprovince, object_workpostalcode, object_workcountry, object_tz
Feb 25 15:25:09 mail HORDE[10260]: [turba] DB Error: no such field: INSERT INTO turba_objects (object_type, object_firstname, object_lastname, object_middlenames, object_nameprefix, object_namesuffix, object_alias, object_bday, object_spouse, object_anniversary, object_children, object_photo, object_homestreet, object_homepob, object_homecity, object_homeprovince, object_homepostalcode, object_homecountry, object_workstreet, object_workpob, object_workcity, object_workprovince, object_workpostalcode, object_workcountry, object_tz
Feb 25 15:25:09 mail HORDE[10260]: [turba] DB Error: no such table: SELECT alarm_id, alarm_uid, alarm_start, alarm_end, alarm_methods, alarm_params, alarm_title, alarm_text, alarm_snooze, alarm_internal FROM horde_alarms WHERE alarm_dismissed = 0 AND ((alarm_snooze IS NULL AND alarm_start <= '2010-02-25T15:25:09') OR alarm_snooze <= '2010-02-25T15:25:09') AND (alarm_end IS NULL OR alarm_end >= '2010-02-25T15:25:09') AND (alarm_uid = '' OR alarm_uid = 'user@domain.com') ORDER BY alarm_start, alarm_end [nativecode=1146 ** Tabl
Feb 25 15:25:09 mail slapd[4452]: conn=1870 op=1 UNBIND
Feb 25 15:25:09 mail slapd[4452]: conn=1870 fd=7 closed
Feb 25 15:25:53 mail HORDE[10628]: [imp] DB Error: no such table: SELECT alarm_id, alarm_uid, alarm_start, alarm_end, alarm_methods, alarm_params, alarm_title, alarm_text, alarm_snooze, alarm_internal FROM horde_alarms WHERE alarm_dismissed = 0 AND ((alarm_snooze IS NULL AND alarm_start <= '2010-02-25T15:25:53') OR alarm_snooze <= '2010-02-25T15:25:53') AND (alarm_end IS NULL OR alarm_end >= '2010-02-25T15:25:53') AND (alarm_uid = '' OR alarm_uid = 'user@domain.com) ORDER BY alarm_start, alarm_end [nativecode=1146 ** Table
Feb 25 15:28:08 mail slapd[4452]:

Any help would be appreciated.

Offline Stefano

  • *
  • 10,894
  • +3/-0
Re: Addressbook issues
« Reply #1 on: February 25, 2010, 09:01:51 PM »
We appearently have more people using webmail then I thought.
Last week the addressbook option stopped working.

Any help would be appreciated.

please open a bug in bugzilla, thank you

Offline janet

  • *****
  • 4,812
  • +0/-0
Re: Addressbook issues
« Reply #2 on: February 26, 2010, 12:16:51 AM »
doublecaps

Quote
I tried browsing the forum and found a couple posts witht he same error message but they all made reference to this happening after an upgrade.

IIRC there was a recent mysql update. You should have restarted mysql after the upgrade, did you ?
Even though it's no longer displayed or requested, for anyone who does not understand when either a service restart or system reconfiguration and reboot are required following an upgrade, then it is still wise to issue the commands
signal-event post-upgrade
signal-event reboot
after any upgrade, as this will cover all requirements.
Please search before asking, an answer may already exist.
The Search & other links to useful information are at top of Forum.