Symptom:

When selecting the Upgrade Wizard, the following error message appears:

./upgradeWizard.log could not be created/written to. Please fix permissions
on your SugarCRM directory.

Cause:

The root directory of the SugarCRM instance is not writable.

Solution:

Ensure that the root directory of the SugarCRM instance permissions include read, write and execute. For Windows installations, ensure that inheritable permissions are allowed.
To change permissions on Linix installations, run the command chmod -R 777 on the following directories and files:

• cache
• custom
• data
• modules
• config.php

For more information on the permissions required for SugarCRM, see the appropriate installation guide on our Product Documentation page.

Symptom

Attempting to test the connection to an IMAP email account fails with the following error:

Can't connect to {email server}: Permission denied
Please check your settings and try again.

Origin

If it is possible to establish a telnet connection to the email server, the issue is most likely that SELinux is enabled.

Solution

Reconfigure SELinux to allow the httpd process to connect via the port specified by the email server.

Symptom

Non-admin users are unable to access a module possibly after an upgrade or after the module has been deployed from Module Builder. The following error message is displayed when trying to access the module:

You are not authorized to access this module.

Administrators are able to access the module as expected.

Origin

Roles for the user do not contain information about the module.

Solution

To resolve this issue, repair Roles.

1. From the Admin Panel, select the Repair link under the “System” heading.
2. Return to the Repair window and select the Repair Roles link to repair roles.
3. Ask all users to log out and log back in (user roles are calculated during log in)

Symptom

Attempting to access a SugarCRM page results in one of the following errors:

Internal Server Error – 500
or
Page Cannot Be Displayed

Origin

The Internal Server Error – 500 is a generic error message, generally caused by configuration issues with php or system permissions.

Solution

To resolve this issue, first obtain more specific error information by changing to the settings of the the web browser.

To see more specific detail on the error in Internet Explorer:

1. Click on Tools/Internet Options/Advanced.
2. Under “Browsing,” uncheck the box “Show friendly HTTP error messages”. You will now be able to see the full error message, including specific issues that will help you in determining the problem.

Common issues:

1. Directory/file Owners and Permissions. The most common error message is related to file permission. By default, most directories are read only and will need to be manually correct to allow writing/executing permissions.
2. Apache conflicts in the .htaccess file. Adding “RewriteEngine” options to the .htaccess file without having the mod_rewrite module loaded in Apache will cause 500 errors.
3. PHP incorrectly installed. To check if PHP is running correctly, create a test.php file and with the line “<?php phpinfo(); ?>”. Run the test.php file; if the 500 error is returned, then the PHP installation is misconfigured.

As of SugarCRM 5.1, the config.php file contains the following section defining default permissions for new directories and files:

'default_permissions' => array (
	'dir_mode' => 1528,
	'file_mode' => 432,
	'user' => '',
)

If this section of code appears to be missing from your SugarCRM 5.1 or above installation, repair the config file from the Admin > Repair menu. Note:  This code does NOT affect existing files and directories, only new ones.

See the table below for common directory permission settings.