magento : exception printing is disabled by default for security reasons

magento : exception printing is disabled by default for security reasons

August 4, 2026 · Illustrated author avatarBy Stefan Bogdanescu
magento : exception printing is disabled by default for security reasons

Solving Magento Installation Errors: Exception Printing Disabled

Understanding the Error Message

When installing or updating Magento, you might encounter errors like this one:

Exception printing is disabled by default for security reasons.

Error log record number: 1970080033

Error in file says:
"D:\websites\magento\app\code\core\Mage\SalesRule\sql\salesrule_setup\upgrade-1.6.0.0-1.6.0.1.php" - SQLSTATE[42000]: Syntax error or access violation: 1067 Invalid default value for 'period'"

The key points here:

  • Exception printing is disabled by default in Magento.
  • The error occurs during the setup process (upgrade script).
  • The issue lies in a SQL syntax error in the salesrule_setup table.

Investigating the Underlying Issue

Identifying the Problematic File

The error log points to a specific file:

"D:\websites\magento\app\code\core\Mage\SalesRule\sql\salesrule_setup\upgrade-1.6.0.0-1.6.0.1.php"

This is an upgrade script for the SalesRule module, which handles promotional pricing rules.

Analyzing the SQL Error

The error message states:

SQLSTATE[42000]: Syntax error or access violation: 1067 Invalid default value for 'period'"

This indicates a syntax issue in the SQL statement within this upgrade script. The period column likely has an invalid default value.

Resolving the Error

You can temporarily enable exception printing by setting the following configuration:

<config>
    <global>
        <install>
            <exception_logging>enabled</exception_logging>
        </install>
    </global>
</config>

Add this to your app/etc/local.xml file. Note: This exposes sensitive data and should only be done for debugging purposes.

Step 2: Check the SQL Statement

The error suggests an issue with a default value in the salesrule_setup table. Verify the structure of this table:

DESCRIBE salesrule_setup;

Look specifically at the period column’s definition for any discrepancies or invalid defaults.

Step 3: Review and Fix the Upgrade Script

Open the problematic file (upgrade-1.6.0.0-1.6.0.1.php) and find the SQL query causing the issue. It likely looks something like this:

$sql = "ALTER TABLE salesrule_setup ADD COLUMN period INT DEFAULT 365";

Ensure the data type is appropriate (INT in this case) and verify that the default value is valid (365 days). If necessary, modify the script to fix the default value or remove it altogether.

Step 4: Re-run the Upgrade

Once you have fixed the SQL syntax error, re-run the upgrade process. Magento should now be able to apply the changes without encountering the exception.

Best Practices for Future Avoidance

Keep Magento Up-to-date

The error occurs due to an outdated version of Magento (1.7). Always ensure you are using the latest stable release or a long-term support (LTS) version.

Use a Staging Environment

Perform upgrades and testing in a staging environment first. This allows you to catch errors like this before they impact your production site.

Regularly Monitor Error Logs

Keep an eye on your Magento error logs for any recurring issues or syntax errors that might require attention.

Conclusion

When faced with exception printing disabled messages in Magento, follow these steps:

  1. Identify the problematic file and table.
  2. Analyze the SQL error message.
  3. Verify the database structure and script logic.
  4. Make necessary corrections to fix the issue.
  5. Re-run the upgrade or installation process.

Remember to always maintain a clean backup of your site before making any changes, especially when dealing with upgrade scripts. If you continue encountering errors, consider consulting the official Magento documentation here for more advanced troubleshooting techniques and community support.

Database Security Extensions Configuration

Our network