Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-2723: When migrating a database to another DirectAudit host, the database shows an "Unknown Problem" message

Auditing and Monitoring Service ,  

12 April,16 at 11:08 AM

Applies to: All versions of Centrify DirectAudit
 
Problem:
 
With a DirectAudit database being migrated to another server, it needs to be attached to either a "Default Installation" or a "New Installation" of the new host with the same version of DA installed. 
 
But when selecting that database, an alert appears stating the "Validation Result" is an "Unknown Problem". 
 
Hence, the attached process in DA is stuck.
 






















 
 
 
Causes:

Possible reasons might be attributed to this:

1. The SQL server and DA are not sitting on the same host. By default, TCP/IP is disabled in SQL Server.

2. When migrating a database to another SQL server, a trust is required in addition to permissions.

3. .NET Common Language Runtime(CLR) is disabled in SQL server by default. It may be required by some processes or procedures.

Resolution:
 
1. Bring up SQL Server Configuration Manager:

- Protocols for DIRECTAUDIT -> TCP/IP -> Enabled
- SQL Server 2005 Services -> Make sure all 3 services on the right pane are running.

2. Bring up the SQL server. Set TRUSTWORTHY attribute by running the following SQL statement:

use [UnixStore-2012-12-1];
ALTER DATABASE [UnixStore-2012-12-1] SET TRUSTWORTHY ON;

3. Restart the SQL server

4. (Optional) If still doesn't work, please enable .NET Common Language Runtime(CLR) by running the statements below and then restart SQL server:

sp_configure 'clr enabled',1

RECONFIGURE

sp_configure 'clr enabled'

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-2727: How to migrate SQL databases associated with a Centrify_DirectManage Audit installation from one database server to another articleKB-6041: How to show current license type in use by adclient articleKB-20210: Common Questions Regarding Centrify DirectControl and CoreOS articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-10203 How to rename DirectAudit Database? articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-6056: How to report the group policy settings that are in effect for the local computer? articlehow to migrate databases associated with a Centrify DirectManage Audit 3.x installation articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin?