Error launching GFI HelpDesk: 'Get() on a non-object'
The following error appears when connecting to GFI HelpDesk:
Get() on a non-object.
In this topic, we'll help you diagnose what exactly is disrupting your connection so you can go about resolving it.
We're going to go through several steps to troubleshoot the issue:
- We'll check to make sure that all of the required PHP plugins are in place.
- We'll take a look at your
config.phpfile to make sure everything is in order.
- We'll double-check that your database credentials are still valid.
- And if we still haven't found the problem, we'll show you how to edit a settings file in order to make it divulge the specific problem that it's encountering.
This error appears to Download customers when GFI HelpDesk is unable to establish a connection with your database. The trouble is, there are multiple factors involved in establishing that connection, any of which could be the culprit.
Check your PHP plugins
GFI HelpDesk officially supports MySQL for its database system and relies on PHP to initiate all connections to MySQL. PHP offers several MySQL extensions for accessing a MySQL database. GFI HelpDesk uses the following extensions:
- MySQL – required for all versions of PHP
- MySQLi – required for PHP 5.5.x or later
- MySQLnd – required for PHP 5.5.x or later
To check which extensions you have installed, consult your PHPInfo page or ask your server administrator to check it for you.
You can double-check the rest of GFI HelpDesk's server requirements.
Review your 'config.php' file
If all of your PHP extensions are present and accounted for, the next thing to look at is your server connection configuration. From your GFI HelpDesk root directory, if you navigate
to __swift/config/ and open up the
config.php file, you'll see that it's full of database connection parameters.
There are a few things you should double-check here:
- Make sure that you have a
config.phpfile: If you've updated GFI HelpDesk, there's a good possibility that you may have, instead, a config.php.new file in this directory, waiting to be activated. If this is the case, remove the
.newfrom the filename, open it up and fill in your database details.
- Double-check your database details: The
config.phpfile should reflect your current server details. The fields you want to check are as follows:
Validate your database credentials
If everything in your config.php file looks right, the next step is to make sure that your server credentials are still valid. The easiest way to validate the database credentials is to run the following MySQL command:
If you get an error here, you'll need to talk to your server admin for up-to-date credentials and then swap them into your config.php file. If the command runs without any problems then you know your credentials are still in good shape. Time to move on to our last resort.
Force your server to tell you the problem
If you've gone through each of the steps above and haven't found the source of the problem, it's time to just ask the server directly. From your root directory, go into the
__swift/models/Settings/ directory and open up the
Scroll down to line 53 and comment it out, by adding // at the beginning of the line. It should look like this:
Save and update the file, and then navigate to your support site. Commenting out that line should display a more detailed error message here on your page. Copy the error message and get in touch with our support team so we can help you resolve the problem.