Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

In this Discussion

osTicket v1.10 (stable) and Maintenance Release v1.9.15 are now available! Go get it now

Opening Closed Tickets results in DB Error #2027

Hi,

We've started having a problem with our osticket installation. I haven't been able to track down the cause of the problem but we're suddenly unable to open the closed tickets page. The only way I've been able to resolve the problem is to restore the mysql db to a date before the problem happens. The only thing is that it keeps happening. 

IIS6
PHP 5.2.9-2
MySQL 5.6
PHP Warning:  mysql_query() [<a href='function.mysql-query'>function.mysql-query</a>]: Unable to save result set in <path to website dir>\include\mysql.php on line 88
Line 88 and surrounding from mysql.php
It will also email this error message
The IIS logs and HTTPERR logs don't really show anything helpul other than the get for the closed tickets page.
Thanks in advance,
Case
Tagged:

Comments

  • Version of osTicket your running?

    Actually after some quick google fu... I came across this.
    http://bugs.mysql.com/bug.php?id=70664
    It looks like that might be a MySQL bug? 
    Can you upgrade your MySQL to 5.3+ to test?

  • Apologies, I thought I had included the version. We're running 1.7.0 right now. In the process of upgrading but wanted to fix the problem first if that makes sense.

  • 1.7.0 is pretty old at this point and has had 8 bug fix releases.  The current version of 1.7 is 1.7.8.  This tree is on the verge of no longer being support so you may want to seriously consider upgrading to to 1.7.8 or better 1.8.1.4 or even better the current version which is 1.9.1.  I do not even have a 1.7.x installation anymore to see if I can replicate your issue.
  • ntozier,

    Thanks for the help and sorry I've been out of pocket on this. Schedule has been difficult. Rather than mucking around with our existing setup I've tried to migrate to another windows server which has created issues of it's own. I guess what I wanted to accomplish was creating a test environment that wouldn't cause issues if I bring things to a screeching halt with testing various things. The end goal is for us to wind up on more current versions of mysql, osticket and windows server. Here's what my plan is:
    1. Migrate existing php, mysql and osticket to identical test environment and make sure it functions
    2. Upgrade mysql
    3. Upgrade php
    4. Upgrade osticket
    5. address DB error if it still exists
    6. Migrate whole setup to IIS 7.5 or 8. (currently on 6).

    Thanks again for your help.
  • Sounds like a plan to me.. but honestly I think that I would setup IIS 7.5 or 8, then install mysql and PHP.  After doing that clone and copy the database from production to the new server... and then upgrade the clone.  But thats just what I would do.
Sign In or Register to comment.