Centova Technologies Forum

Centova Cast v3 => Bugs and issues => Topic started by: renggap on September 06, 2015, 02:40:10 am

Title: Errors in centova client area
Post by: renggap on September 06, 2015, 02:40:10 am
Hello,
Recently I did make a payment for a license upgrade, but my invoice is still marked as awaiting payment. When I clicked on my server license, it shows error:

-------------
SQL Error: Could not execute query in /shared/www/centova/secure/cp/backend/licensing/packagetypes/class_PackageType_licensing_keysystem.php:129
Query:    SELECT * FROM licenses_history WHERE apid=220791 ORDER BY invalidated DESC
Error:   Table 'licenses_history' is marked as crashed and should be repaired
Call:   $SQL->select_query()
-------------

I also attached file errors when trying to submit ticket
Title: Re: Errors in centova client area
Post by: scysys on September 06, 2015, 03:41:28 am
Here too. Licence Error on all Systems now.

WHMCS: Error: ERROR: Your license does not permit any more services (station capacity of ).<br>Please <a href="http://support.cast-control.net">Upgrade your license</a> then re-login to update your license

Your Client Area: Table 'licenses_history' is marked as crashed and should be repaired

When Submit an Ticket, there is be an SQL Error.
Title: Re: Errors in centova client area
Post by: DJFire_CFR on September 06, 2015, 07:16:51 pm
"Table 'licenses_history' is marked as crashed and should be repaired"


That there.

repair the licenses_history table, and it should remove the error.
Title: Re: Errors in centova client area
Post by: Dennis Fallon on September 07, 2015, 09:42:32 am
There is no table called licenses_history.

It must be on the other end.
Title: Re: Errors in centova client area
Post by: Alexiu on September 07, 2015, 11:57:38 am
We had a problem with a couple of MySQL tables crashing and that's what was generating those errors. (the WHMCS error from scysys's message is unrelated to this issue)

Still, any actions you were trying to perform (e.g: license reissue) should have been successful, even if a MySQL error was being displayed.

Apologies for the inconvenience!