From CEO:
Database Error: 2014 - Commands out of sync; you can't run this command now.
Query: select count(*) as total from app_sessions where sesskey = '23475c3788c8b5b23e77e7e2dd2xxxxx
Page: /**REDACTED**/index.php?module=items/&action=save&id=417&token=twhovxxxxx
[3:23 PM]
Message from CEO: "every time i try to work on the **REDACTED** program this is the message i receive."
Some information may have been redacted due to security reasons.
Database Error: 2014 Commands out of sync; you can't run this command now
-
- Sponsor
- Posts: 215
- Joined: 03 Jun 2021, 22:06
- Name: Bradley Hayes
- Location: USA Palmdale
- Company Name: Two-Lifestyles, Inc.
- Contact:
Re: Database Error: 2014 Commands out of sync; you can't run this command now
Possible Fixes:
See the following page related to mysqli and unbuffered commands.
https://www.php.net/manual/en/mysqli.query.php#102904
In particular, see the following clip from that page.
See the following page related to mysqli and unbuffered commands.
https://www.php.net/manual/en/mysqli.query.php#102904
In particular, see the following clip from that page.
-
- Sponsor
- Posts: 215
- Joined: 03 Jun 2021, 22:06
- Name: Bradley Hayes
- Location: USA Palmdale
- Company Name: Two-Lifestyles, Inc.
- Contact:
Re: Database Error: 2014 Commands out of sync; you can't run this command now
Any updates on this?
It's kinda important that this be fixed.
It's kinda important that this be fixed.
- support
- Site Admin
- Posts: 6221
- Joined: 19 Oct 2014, 18:22
- Name: Sergey Kharchishin
- Location: Russia, Evpatoriya
Re: Database Error: 2014 Commands out of sync; you can't run this command now
Hard to say what is it. Try to change session handler.
Open config/server.php and set
Open config/server.php and set
Code: Select all
define('STORE_SESSIONS', '');
-
- Sponsor
- Posts: 215
- Joined: 03 Jun 2021, 22:06
- Name: Bradley Hayes
- Location: USA Palmdale
- Company Name: Two-Lifestyles, Inc.
- Contact:
Re: Database Error: 2014 Commands out of sync; you can't run this command now
This worked fine. We haven't seen it occur again since making this change.
Thanks.
Thanks.