Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Recovering PolicyServer when the database is corrupted

    • Updated:
    • 1 Apr 2014
    • Product/Version:
    • Endpoint Encryption 3.1 PolicyServer
    • Endpoint Encryption 5.0
    • Platform:
    • Windows 2003 Enterprise
    • Windows 2003 Enterprise 64-bit
    • Windows 2003 Standard
    • Windows 2003 Standard 64-bit
Summary
Recover the PolicyServer in case the database gets corrupted.
Details
Public
To recover the PolicyServer:
  1. Run MADB Setup for the version most recently installed. Continue with the setup and install both databases.
  2. Open SQL Enterprise Manager or SQL Management Studio and expand the Database folder.
  3. Right-click the Endpoint Encryption database and select Task > Restore.
  4. Click From Device > Select Device.
  5. Click Add to select the database backup that will be restored.
  6. Navigate to the directory where the backup is stored.
  7. Select the backup and click OK.
  8. On the Restore Database screen, select the Options tab.
  9. Select Force Restore Over Existing Databases (2000) or Overwrite the Existing Database (2005) and click OK to begin the restore process.
    This may take a few minutes, depending on the size of the database and hardware being used.
  10. Repeat steps 3 to 8 for the Endpoint Encryption Log database.
  11. Follow the procedure depending on your SQL version.
    For SQL 2000:
    1. Open the Databases folder in the Enterprise Manager and expand the Endpoint Encryption DB.
    2. Click Users.
    3. Right-click MADB or the account used during the initial setup of the databases and select Delete.
    4. Right-click Users and select New Database User.
    5. Select the new MADB account as the Username.
    6. Tick the db_owner, db_datareader, and db_datawriter check boxes and click OK.
    7. Repeat steps A to F for the Endpoint Encryption Log database.
    For SQL 2005:
    1. Open the Databases folder in the SQL Server Management Studio and expand the Endpoint Encryption DB.
    2. Select Security > Schemas folder.
    3. Double-click the schemas with MADB or the account used before.
    4. Click the Search button in the Schema Owner field.
    5. Enter DBO and click Check Names. The object name should change to DB once it is found.
    6. Click OK.
    7. Repeat steps A to F for Endpoint Encryption Log database.
    8. Open the Databases folder in the SQL Server Management Studio and expand the Endpoint Encryption DB.
    9. Select Security > Users folder.
    10. Right-click the MADB account and select Delete.
    11. Right-click Users and select New User.
    12. Select the new MADB account as the User Name.
    13. Tick the db_owner, db_datareader, and db_datawriter check boxes for Owned Schemas and Database Role Memberships and click OK.
    14. Repeat steps H to M for the Endpoint Encryption Log database.
  12. Reinstall the PolicyServer Service.
    Note: You may skip this step if you are using the same account used throughout the Endpoint Encryption deployment. The PolicyServer Service should have the correct credentials to access the Endpoint Encryption databases.
Premium
Internal
Rating:
Category:
Configure; Troubleshoot; Deploy; Install; Migrate
Solution Id:
1059580
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.