getActionTimestamp return bad value in soap

horde webmail 3.3.5 / turba 2.3.2 getActionTimestamp alwa

Wed, 25 Nov 2009 23:16:32 +0000

horde webmail 3.3.5 / turba 2.3.2 getActionTimestamp always return 0. http trace follows (Pdb) print server.contacts.getActionTimestamp("20091125212217.12527jgoulnhlpmh@newwebmail.eng.it","add") *** Outgoing SOAP ******************************************************

20091125212217.12527jgoulnhlpmh@newwebmail.eng.it add

************************************************************************ *** Incoming SOAP ******************************************************

************************************************************************ 0

Do you know that this is specific to SOAP (as in the bug tit

Sun, 29 Nov 2009 05:23:40 +0000

Do you know that this is specific to SOAP (as in the bug title)? Or have you tried other RPC backends?

> Do you know that this is specific to SOAP (as in the bug t

Sun, 29 Nov 2009 14:07:23 +0000

> Do you know that this is specific to SOAP (as in the bug title)? Or > have you tried other RPC backends? even with xmlrpc... Peace, R

I installed a brand new horde with a fresh db and seems this

Mon, 30 Nov 2009 13:33:59 +0000

I installed a brand new horde with a fresh db and seems this bug won't apply. So it could be a problem on sql of the horde installation. Which can be the cause? Peace, R.

So you're saying it works fine with a clean install, but doe

Mon, 30 Nov 2009 15:42:05 +0000

So you're saying it works fine with a clean install, but doesn't work for your existing install? Same code versions?

> So you're saying it works fine with a clean install, but d

Mon, 30 Nov 2009 16:36:47 +0000

> So you're saying it works fine with a clean install, but doesn't work > for your existing install? Same code versions? yes, after some troubleshooting I found the following error: Nov 30 15:19:55 HORDE [error] [turba] DB Error: constraint violation: UPDATE horde_histories_seq SET id = LAST_INSERT_ID(id + 1) [nativecode=1062 ** Duplicate entry '3223' for key 'PRIMARY'] [pid 23757 on line 198 of "/var/www/webmail/horde-webmail-1.2.4/lib/Horde/History.php"] Which could be the cause?

The sequence table maintained by MDB2 to keep track of prima

Sat, 05 Dec 2009 03:48:05 +0000

The sequence table maintained by MDB2 to keep track of primary keys is corrupted or just plain wrong. Did you change it by hand?

Either way, there isn't a problem with the method call.

Sat, 05 Dec 2009 03:48:21 +0000

Either way, there isn't a problem with the method call.