How To, JaguarSX install, linux

Occassionally one or more tables in the database becomes corrupt. Fixing it is usually simple. Always be sure to make periodic backups of your database, just in case these tools do not work.

To test your database for corruption, issue the following command. You can include a table name at the end to just check a specific table, if desired:

mysqlcheck -u {USERNAME} {DATABASE} [TABLE]

Example:

C:\mysql5.0.45\bin>mysqlcheck -u root bytesphere alerts
bytesphere.alerts
warning  : 19 clients are using or haven't closed the table properly
error    : Found key at page 339968 that points to record outside datafile
error    : Corrupt

To fix it, make sure the system is shut down and not connected to it, then issue the following command including the -r switch to repair:

mysqlcheck -r -u {USERNAME} {DATABASE} [TABLE]

Example:

C:\mysql5.0.45\bin>mysqlcheck -r -u root bytesphere alerts

bytesphere.alerts                                  OK

Here we see that the mysql tool has fixed the alerts table. Now you can start up your application and attend to business as usual.

How To, JaguarSX corruption, database, How To

This error is caused by an incomplete PHP configuration. Both SOAP and XML extensions need to be enabled in PHP in order for the UI to work.

LoadXML Error caused by PHP mis-configuration

On linux, make sure the following packages are installed (PHP SOAP, PHP XML, PHP DOM). You can install them by typing in the following commands:

yum install php-xml

yum install php-soap

yum install php-dom

On Windows, make sure the php.ini file has the following extensions enabled in the php.ini file and then restart Apache:

extension=php_soap.dll

JaguarSX, KnowledgeBase Configuration, error, JaguarSX, PHP, SOAP, XML

How To, JaguarSX debugging, JaguarSX

The problem:

You get a message stating “Your system is not compatible with your license file or your license file does not exist!”

Very rarely, you may experience this error when trying to start OidView. Usually occurs after a system upgrade (hardware or software). What this means is that the HARDWARE-ID in the computer has changed (you can tell this by running OIDVIEW REGISTER from the command line).

The solution:

The problem is easily solved, all you must do is to transfer your old license with your original HARDWARE-ID to a new license with your new HARDWARE-ID. You can issue transfers at the following URL: http://www.oidview.com/key-request-txfr.html

For more information on how to license OidView (including license Transfers) please see the following URL: http://www.oidview.com/wordpress/2008/10/07/how-to-activate-oidview/

KnowledgeBase, OidView error, KB, licensing