Another Backup Error

[mikelegg]

Today Plesk started reporting another error in the "migration.result" file attached to the daily backup notification email

<?xml version="1.0" encoding="utf-8"?>
<execution-result status="warnings">
<object name="domain.tld" type="domain">
<message code="InformationalException" severity="error">Cannot dump database content database_name of type mssql'</message>
</object>
</execution-result>

There's no explanation of why it cannot dump the content of the database, it just can't do it for some unspecified reason.

Does anyone have any ideas what might be causing this one?

 

[Nataliya Zagr]

Hello,

The problem is known to be caused by active "On-Access Scanner" feature of McAfee VirusScan anti-virus software installed on Parallels Plesk Panel server. This functionality prevents Parallels Plesk Panel from backing up MySQL databases properly. To resolve this issue, exclude the folder where MySQL databases are stored from the list of folders scanned by McAfee VirusScan.

Below is the folder location on default Parallels Plesk Panel installation:

"C:\Program Files\SWsoft\Plesk\Databases\MySQL\Data\"

It is also recommended to enable the "Also exclude subfolders" option in McAfee VirusScan.

Please, see the following article for more information:

http://kb.odin.com/en/5830

Thank you

 

[mikelegg]

The error isn't being generated on a MySQL database, it's an MSSQL database (which is running on stand-alone DB server).

Additionally, McAfee AntiVirus isn't installed on the server.

 

[IgorG]

Seems problem in that this database has encrypted stored procedure. Try to decrypt it and then you should be able to backup database. We have already submitted bug regarding this problem. It is under developer's investigation now.

 

[mikelegg]

Seems problem in that this database has encrypted stored procedure. Try to decrypt it and then you should be able to backup database. We have already submitted bug regarding this problem. It is under developer's investigation now.

The error disappeared from today's backup. Perhaps the domain owner decrypted the stored procedure.

 

[mikelegg]

The error came back today on a completely different mssql database. It has nothing to do with encrypted stored procedures because I created this database myself and I know that none of the stored procedures are encrypted.