Knowledgebase

Unable to clone or backup MSSQL database in Plesk: Property TextHeader is not available for StoredProcedure <...>. The text is encrypted

The error message you're encountering, "Property TextHeader is not available for StoredProcedure <...>. The text is encrypted," indicates that the stored procedure in your MSSQL database is encrypted, which is preventing Plesk from performing certain operations on it.

Here are some steps you can take to address this issue:

  1. Decrypt the Stored Procedure:

    • If possible, try to decrypt the stored procedure. Keep in mind that this might not be feasible if the stored procedure is proprietary or if you do not have access to the original source code.
  2. Check Database Permissions:

    • Ensure that the user account you're using to access the MSSQL database in Plesk has the necessary permissions to clone or backup stored procedures.
  3. Update Plesk and Extensions:

    • Make sure that both Plesk and any related extensions or components are up-to-date. Sometimes, updates include bug fixes and improved compatibility.
  4. Verify Database Integrity:

    • Run integrity checks on your MSSQL database to ensure there are no underlying issues that might be causing this error.
  5. Contact Database Administrator:

    • If you're not the database administrator, consider reaching out to the person or team responsible for managing the MSSQL server. They might have specific insights or actions they can take.
  6. Check MSSQL Server Logs:

    • Review the MSSQL server logs for any error messages or warnings related to this specific stored procedure. This might provide more context about the issue.
  7. Consult Plesk Support:

    • If none of the above steps resolve the issue, consider reaching out to Plesk support for further assistance. They can provide specific guidance based on your server's configuration and the nature of the error.

Please note that if the stored procedure is encrypted for security reasons or due to licensing restrictions, decrypting it might not be an option. In such cases, you may need to consult with the creator or owner of the stored procedure for guidance on how to proceed.

  • 0 Users Found This Useful
Was this answer helpful?