Database error, Click here to resume your eGroupWare Session

[leendert]

Hi,

after downloading and installing egroupware I get an error trying to log in:

Database error

Invalid SQL: UPDATE egw_access_log SET session_dla=1335645216,session_action=’’,lo=NULL WHERE sessionid=7

Click here to resume your eGroupWare Session.

The link “Click here to resume” doesn’t do anything How do I repair this?
Any help would be appreciated.

Keep up the good work!
Leendert

[C_K_Wu-2]

Hi, folks,

I encountered the same problem as described by Leendert.

Just to add a bit of additional info. I installed
eGroupWare-1.8.004.20120423.tar.gz2 within the following environment,

Kubuntu 12.04, Apache 2.2.22, mysql 5.5.22, php 5.3.10

Initially, the default mysql (vs. mysqli and mysql with transaction)
setup was employed and everything was fine. I could install and login
as usual. However, response time was significantly slower than
1.8.002, so I cleared everything, dropped the entire database and
re-installed everything, choosing mysqli this time. All other items
were the same, including db host, db name, db user, db password. This
time, I could install, but could not login, as described by Leendert.
The error message was the same (except the session_dla and sessionid
figures).

Best Regards,
CK

Hi,

after downloading and installing egroupware I get an error trying to log in:

Database error

Invalid SQL: UPDATE egw_access_log SET
session_dla=1335645216,session_action=’’,lo=NULL WHERE sessionid=7

Click here to resume your eGroupWare Session.

The link “Click here to resume” doesn’t do anything How do I repair this?
Any help would be appreciated.

Keep up the good work!
Leendert

–
View this message in context: http://egroupware.219119.n3.nabble.com/Database-error-Click-here-to-resume-your-eGroupWare-Session-tp3947308.html
Sent from the egroupware-users mailing list archive at Nabble.com.

---

Live Security Virtual Conference
Exclusive live event will cover all the ways today’s security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

---

eGroupWare-users mailing list
eGroupWare-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-users

---

Live Security Virtual Conference
Exclusive live event will cover all the ways today’s security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

---

eGroupWare-users mailing list
eGroupWare-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-users

[leendert]

Hi,

solved.

When I tried to login today I got an error message that something was wrong with my database and tables and that I had to run setup. (I think the session id expired and this was a normal response)

Did that, and setup found no database. Strange. Followed the instructions (login to mysql and create database, because egw was unable to do for me (due to rights I guess)).
In mysql> I entered the command to create the database and the answer was there was a database with that name.
Ok, I then just granted permission to the tables as suggested by the instructions. Reran the check on my database and everything worked. Able to login and ready to go!

Thank you!
Best regards,
Leendert

[C_K_Wu-2]

Hi, folks,

It turns out that mysql 5.5.22 defaults to using InnoDB, whereas the
previous mysql versions use MyISAM. After setting the
default-storage-engine=myisam in my.cnf , I restart mysql and re-install
eGW + CK-ERP using eGroupware-1.8.004.20120515. The installation
(employing mysql) went OK and was completed very fast. I am guessing
that installation involves a lot of sequential inserts, and myisam
somehow handles these more efficiently than InnoDB, as InnoDB is geared
towards better CRUD locking protection.

However, installation using msqli still resulted in the same error message,

Invalid SQL: UPDATE egw_access_log SET
session_dla=1337175428,session_action=’’,lo=NULL WHERE sessionid=2

Just for interest sake, I cut and paste the above invalid sql into the
mysql client mysql> environment and it executed OK, so syntax does not
seem to be the problem.

Best Regards,
CK

your eGroupWare Session