Jeff Tangen’s Wordpress

Consider the following scenario in a Plesk control panel.

You need to restore a ftp account password, or a Frontpage account password, or an email password, or a specific domain admin password.
But you can not reset the password.

Perform a backup of the effected domain and only backup the configuration. There is no need for the data. Once you have the backup, extract the corresponding XML file and open it up in your favorite text editor. The passwords contained are the passwords that Plesk is aware of.

If the password(s) were changed using an alternate method then the Plesk control panel, then the password(s) are not recoverable with this process and the only option is to reset the password(s).

If you just changed your domain administrator password, this would cause the error message.   Close your browser session and re-open.

Consider the following scenario:

Plesk control panel installed on top of a hosted mail server.
Inside of Plesk, an email object is created and then enabled for a mail group. Email addresses (recipients) are added to the mail group.
An email is sent to the mail group and is never received by the recipients.
The email log file shows that the email was received successfully however it was never delivered on to the intended recipients (in the mail group).

Resolution:
The mail object in Plesk has the mail group and mailbox enabled. Because both are enabled the email is sent to the mailbox and the mail transaction is complete.
Once the mailbox was turned off in Plesk the email is properly sent to the intended recipients (in the mail group).

Smartertools has shown me how to “disable” smmailfilter.exe from running inside of Plesk in Smartermail. Actually, it is not disabling it, so to say…but more of not have it run.

In Smartermail
Settings/General Settings
Spool Tab

If C:\Program Files (x86)\Parallels\Plesk\admin\bin\smmailfilter.exe %filepath is in the “command line file to run on new mail” is enabled, disable it.

However, this will disable all email functions inside of Plesk.

When doing a migration of sites, the Plesk migration reports an error “Agent already used by another migration session”.

To correct this item, stop and start the migration agent on the souce server.

Plesk may report an error during the migration of a domain.

plesk::validateSchema.\xml_parse.cpp412Failed validation of the document with its internal DTD. The errors are: Element ‘redirect’, attribute ‘enabled’: [facet ‘enumeration’] The value ” is not an element of the set {‘true’, ‘false’}.
Element ‘redirect’, attribute ‘enabled’: ” is not a valid value of the local atomic type.
.

I have not found the ultimate solution to this error message.
What I have done as a work around was to recreate the domain by hand and manually copy the data.

If you have a better way to correct this error message, please let me know.

During a Plesk migration process, the migration may fail with a blank error log. I have found a few things that have been able to correct this.

1. Stop and restart the Plesk agent on the source server.
2. Do a backup of the domain on the source server to verify the integrity of the data which is being migrated.
3. Verify that there isn’t any “network” issues or that there are any “rogue” or “run-away” processes that are running on either the source or destination server.

Per Plesk, this error can occur in “rare” occurances in which 64 bit operating systems are in the mix (destionation server) for domain migrations.

To resolve the issue, reboot the destination server.