This chapter provides a list of startup errors, their meanings, and possible solutions.
If you encounter a problem that is not covered in this chapter, contact SUMO technical support and submit any include relevant log entries or configuration files to sumoam-support@lists.sourceforge.net

Startup errors are printed to standard output when application starts and you can view a message like this:

SUMO ERROR Configuration error! code: E00002S register_globals must to be OFF! Change it in your php.ini! Note: This error page might contain sensitive information because SUMO is configured to show verbose error messages using SUMO_VERBOSE_ERRORS=TRUE. Consider using SUMO_VERBOSE_ERRORS=FALSE in production environments. SUMO Access Manager © Copyright 2005-2006 by Basso Alberto

IMPORTANT:
If only a blank page are displayed and no error is available enable SUMO_VERBOSE_ERRORS on <sumo_dir>/configs/config.server.php to view all possible messages from PHP engine.


Error codes help you to identify the cause of a problem and the actions that might be needed to solve the problem.
Error codes provide a unique entry to application procedures. Each error code has an error ID that uniquely identifies the condition that caused the error. Error could be recorded on database, on filesystem or sended via e-mail. The following errors types are possible:

• E: Error
  This type identifies maximum severity level
• W: Warning
  This type identifies medium severity level by an unexpected conditions that might be experienced during user operations. These conditions can result from network errors or incorrect user actions.
• I: Information
  This type identifies conditions where a user might want to be notified of the completion of an event.

The error code tables list the various error codes and describe the actions that you may take.

The following table list only startup error codes:

Error Code	Message / Action
E00000S	Undefined error! CAUSE: No error details ACTION: Set SUMO_VERBOSE_ERRORS to TRUE on <sumo_dir>/configs/config.server.php to view all possible messages from PHP engine.
E00001S	You have accessed this URL improperly! CAUSE: You have accessed directly to application from an improperly URL. ACTION: No action available.
E00002S	Configuration error! CAUSE: The parameter "register_globals" on your php.ini is set to ON. ACTION: Set register_globals to OFF in your php.ini.
E00003S	Database connection failed! CAUSE: Various reasons can generate this error, these are most frequent: Wrong configuration on <sumo_dir>/configs/config.database.php. Wrong configuration on your hosts file. SUMO database is on different server (remote) and a firewall between servers prevents network communications. SUMO database is on different server and not accept remote connections. SUMO database is stopped (listener or database daemon is down). Database server overloads or network down. ACTION: Verify that any parameters on <sumo_dir>/configs/config.database.php is correct (verify these parameters also on database server). Six parameters are required: Database type (mysql, oracle, etc...) Hostname or IP address of database Database name Database port Database user Database password This is an example of configuration file for MySQL database at localhost: $sumo_db['type'] = 'mysql'; $sumo_db['host'] = 'localhost'; $sumo_db['port'] = '3306'; $sumo_db['name'] = 'sumo'; $sumo_db['user'] = 'RogerWaters'; $sumo_db['password'] = 'TheWall'; If you try to connect to database via hostname (see <sumo_dir>/configs/config.database.php) verify if in your hosts file (on Unix/Linux system is /etc/hosts) there is correct IP address and hostname for your database. Verify your firewall configuration: port, protocol, source and destination IP's between servers (see your database specifications for correct settings). Note: you can verify a connection from application to SUMO database via telnet, so open a shell (or a command prompt on Windows systems) and type: telnet <your_database_ip> <database_port> for example on MySQL: telnet <your_database_ip> 3306 # (default port) If you can't connect to database server contact your DBA to verify database settings. Verify if database accept remote connections (in MySQL set bind_address=<your_database_ip>), and if database user can connect to it from remote server. If you can't connect to database contact your sysadmin to verify firewall and network settings. Verify if database is running, if not restart it and reload a page. Contact your database administrator to find overload reasons or your sysadmin for system or network overload.
E00004S	Template not found! CAUSE: Can't load a template file or template not exist. ACTION: Verify if you have required .tpl files for defined theme, and if web user have read permission on these files.
E00005S	PHP version check failed! CAUSE: the version of PHP interpreter is not fully supported. You cannot run SUMO on this server. ACTION: The application need PHP version 5.0 or above.
E00006S	Missing GD extension! CAUSE: The GD extension for PHP are missing. This extension is required to manipulate images into some SUMO modules. SUMO try to loads this extension at runtime using "dl" function, however don't work. ACTION: Use phpinfo() function to view which extensions have been loaded. The php.ini file is used to configure it, then add the missing extension.
E00007S	Service denied! CAUSE: You not have permission to access this service, or you have accessed this service improperly. ACTION: Check your user permissions, and ask to your SUMO system administrator if necessary.
E00008S
E00009S	Configuration error! CAUSE: Your SUMO server it's configured to use SQLite as database, but store sessions to SQLite don't work. ACTION: Set SUMO_SESSIONS_DATABASE to false in your server configuration file: <SUMO_PATH>>/configs/config.server.php.
E00010S	Configuration error! CAUSE: Your SUMO server it's configured to use SQLite as database, but sessions replica don't work on this database. ACTION: Set SUMO_SESSIONS_REPLICA to false in your server configuration file: <SUMO_PATH>>/configs/config.server.php.
E00011S	Database error! CAUSE: Can’t load Server configuration from database table. ACTION: Look at your Sumo server configuration file <SUMO_PATH>>/configs/config.sumo.php the name of the configuration table (SUMO_TABLE_CONFIGS), it can be sumo_configs. Then verify if this table is not empty, must contain at least two lines, one for the server and one for the console configuration. Each line have an XML data file that describe the relative configuration parameters.