PHP4 or PHP5 GD Image Library or ImageMagick Error

When you run into this PHP4 or PHP5 error stated below.

Critical Error

PHP running on your server does not support the GD Image Library, check with your webhost if ImageMagick is installed.

Simply remove the ';' semi-colon from the 'extension=php_gd2.dll' in php.ini

Removing disconnected mailboxes in Exchange Server 2007

Article Source

Description: Removes a given user from AD and disconnects their Mailbox
Comamnd: Remove-Mailbox -Identity contoso\john

Description: Removes a given user from AD and purges their mailbox from the database
Command: Remove-Mailbox -Identity contoso\john -Permanent $true

Description:Purges from the database a single already disconnected mailbox. Uses Get-MailboxStatistics to get the identity of the user before passing to remove-mailbox
Command: $Temp = Get-MailboxStatistics | Where {$_.DisplayName -eq 'John Peoples'}
Remove-mailbox -Database Server01\Database01 -StoreMailboxIdentity $Temp.MailboxGuid

Description:Removes all disconnected Mailboxes from a Database
Command: Get-MailboxStatistics -database "server\database" | where {$_.disconnectdate -ne $null} | foreach {Remove-mailbox -database $_.database -storemailboxidentity $_.mailboxguid}

Addtional Info - Article Source

Exchange Server 2007 doesn't allow us to purge the disconnected mailbox. In order to remove one or multiple disconnected mailboxes we can be performing these steps:

Listing all disconnected mailboxes

Get-MailboxStatistics | where-object { $_.DisconnectDate -ne $null } | Select DisplayName,MailboxGuid

Removing a single entry

Remove-Mailbox -Database -StoreMailboxIdentity -confirm:$false

Removing all users at the same time

$users = Get-MailboxStatistics | where-object { $_.DisconnectDate -ne $null } | Select DisplayName,MailboxGuid

Now that we have all disconnected mailboxes in a var, we can run the following cmdlet to remove all of them:

$users | ForEach { Remove-Mailbox -Database "Mailbox Database" -StoreMailboxIdentity $_.MailboxGuid -confirm:$false }

Understanding Exchange 2007 Disconnected Mailboxes

Article Source

Exchange 2007
Understanding Disconnected Mailboxes

Applies to: Exchange Server 2007, Exchange Server 2007 SP1 Topic Last Modified: 2007-01-30

In Microsoft Exchange Server 2007, each mailbox consists of an Active Directory directory service user and the mailbox data that is stored in the Exchange mailbox database. (For an illustration of the components of a mailbox, see Figure 1.) All configuration data for a mailbox is stored in the Exchange attributes of the Active Directory user object. The mailbox database contains the mail data that is in the mailbox associated with the user account.

When you create a mailbox for a new or existing user, the Exchange attributes that are required for a mailbox are added to the user object in Active Directory. The associated mailbox object in the Exchange mailbox database is not created until the mailbox either receives a message or the user logs on to it. If you create a new mailbox, and then remove or disable that mailbox before the mailbox object in the Exchange mailbox database is created, it will not be available as a disconnected mailbox.

Figure 1 Components of a mailbox

Parts that make up a mailbox

A disconnected mailbox is a mailbox object in an Exchange mailbox database that is not associated with an Active Directory user account. When you remove or disable a mailbox, the data that is stored in the Exchange mailbox database is no longer associated with the user account in Active Directory and becomes a disconnected mailbox.

If you remove a mailbox, the mailbox data that is stored in the Exchange mailbox database is marked for deletion and the associated user account is also deleted from Active Directory. To retain the user account and only disassociate the mailbox data from the user account, you must disable the mailbox. For detailed instructions, see How to Disable a Mailbox.

To provide a method for recovering mailbox data without having to restore the entire mailbox database, disconnected mailboxes are retained in the mailbox database for a specific amount of time. By default, Exchange retains a disconnected mailbox for 30 days. During this time, the disconnected mailbox can be recovered by associating it with an existing Active Directory user account. To learn more about deleted mailbox retention, see Configuring Deleted Mailbox and Deleted Item Retention.

There are two operations you can perform on a disconnected mailbox:

  • Connect it to an existing user account in Active Directory
  • Permanently delete it from the Exchange mailbox database

Connecting a Disconnected Mailbox

During the time a disconnected mailbox is retained in the Exchange mailbox database, you can connect it to an existing Active Directory user account that is not associated with another mailbox. Scenarios in which you may want to connect a mailbox include the following:

  • You disabled a mailbox and now want to reconnect the mailbox to an Active Directory user account.
  • You removed a mailbox by using the Remove-Mailbox cmdlet without the Permanent or StoreMailboxIdentity parameters and now want to reconnect the mailbox to a different Active Directory user account.
  • You want to convert a user mailbox to a linked mailbox that is associated with a user account external to the forest in which your Exchange organization exists. The resource forest scenario is an example of when you would want to associate a mailbox with an external account. In a resource forest scenario, user objects in the Exchange forest have mailboxes, but the user objects are disabled for logon. You must associate these mailbox objects in the Exchange forest with enabled user objects in the external accounts forest.

You can use the Connect-Mailbox cmdlet in the Exchange Management Shell or the Connect Mailbox wizard in the Exchange Management Console to connect a mailbox. The Connect Mailbox wizard is available from the action pane when you select the Disconnected Mailbox node under Recipient Configuration. For detailed instructions about how to connect a disconnected mailbox, see How to Connect a Mailbox.

After you connect a mailbox to an existing Active Directory user account, that user account becomes the owner of the mailbox and has full access to any content within the mailbox.

Permanently Deleting a Disconnected Mailbox

Exchange retains disconnected mailboxes in the mailbox database based on the deleted mailbox retention settings configured for that mailbox database. After the specified retention period, a disconnected mailbox is permanently deleted from the Exchange mailbox database.

You can also permanently delete a disconnected mailbox at any time by using the Remove-Mailbox cmdlet in the Exchange Management Shell. To do this, you need to set the Permanent parameter to $true when you run the command.

If you want to permanently delete the data within the mailbox database for a previously disconnected mailbox, you must use the StoreMailboxIdentity parameter with the Remove-Mailbox cmdlet. You can use the Get-MailboxStatistics cmdlet to determine the value you need to supply to the StoreMailboxIdentity parameter for a disconnected mailbox. For an example of this scenario, see the third code example in the reference topic Remove-Mailbox.

For detailed syntax and parameter information, see the Remove-Mailbox and Get-MailboxStatistics reference topics.

For detailed information about how to connect a disconnected mailbox, see How to Connect a Mailbox.

For more information about deleted mailbox retention, see Configuring Deleted Mailbox and Deleted Item Retention.

For more information about the Exchange Management Shell cmdlets that relate to disconnected mailboxes, see the following topics:

To learn more about mailboxes, see Understanding Recipients.

To learn more about managing mailboxes, see Managing User Mailboxes.


Check PHP version

create a php file and copy this codes into the file.


Test MySQL Server database login

create a php file and copy the below contains to test your MySql Server Database login

// hostname or ip of server (for local testing, localhost should work)

// username and password to log onto db server

// name of database

$link = mysql_connect("$dbServer", "$dbUser", "$dbPass") or die("Could not connect");
print "Connected successfully
mysql_select_db("$dbName") or die("Could not select database");
print "Database selected successfully

// close connection

phpbb Field 'user_from' doesn't have a default value [1364]

Article Source

Do take note that the solution recommend can solve the username shown as [BLOB] error as well.

When carrying out any one of many actions on your board you may find your self getting errors such as the one in this example error.
Field 'forum_last_post_subject' doesn't have a default value [1364]
This can happen on any one or multiple database columns in the database so the column mentioned in the error could vary but the problem is very likely the same.

This is usually a result of the database being upgraded. For example from MySQL 3.0.x or 4.0.x to 4.1.x or 5.x, quite often the web host will do such an upgrade without warning.

The problem is that the schema of the databases in older versions will not work correctly in newer versions without various things being changed. The result of such an upgrade without fixing the database schema is the above mentioned error.

This issue has become more common on the support forums recently and more importantly many people have been incorrectly submitting this as a phpBB bug. As a result the Development team decided it would be in their best interests to address the problem. Thus they produced a script which could be executed producing a set of SQL queries to correct the database schema.

The Fix
  • Make complete backups of the boards database before executing any queries this script provides.
  • Please make sure that you are running the latest version of phpBB3 and then download
  • Extract the compressed archive to your desktop.
  • Open the file in a plain text editor and read the instructions at the top of the extracted file and act accordingly.
  • Use your ftp client to upload the mysql_upgrader.php into the board root. This is the same location as the boards config.php.
  • Browse to this file in your web browser via its URI. So using the board as an example you would browse to
    Code: Select all
  • This will cause the script to scan your database and then provide the correct schema for you MySQL version. As such it will output a list of SQL queries which can
    • Be run all in one go via phpmyadmin
    • Or run via the MySQL console
    • Or given to the host to run.
  • Once the provided queries have been executed the errors should be fixed and the board working correctly.
  • Now use your ftp client to remove the files mysql_upgrader.php from your board root.