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-7537: Unable to re-attach old AuditStore database

29 September,16 at 02:30 PM

Applies to:

All versions of Centrify DirectAudit on all supported Windows platforms


Problem:

When attempting to attach an old AuditStore, the operation fails with an error "Failed ot complete the Audit Store Database Wizard...".
If logging is enabled for the console to capture the attempt, entries similar to the following may be observed:

[Mon 01/18/2016 04:04:36.373 PM] mmc.exe[6960,1] Trace: Snapin.Trace: Error - System.Data.SqlClient.SqlException: -1, message:A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)


Cause:

The likely cause of this issue is a naming mismatch for the Management Database Server between what is stored on the SQL side and what it stored within the Audit Installation details within AD. Eg. DB server registered via CNAME whereas it is defined by its FQDN within AD.


Workaround:

Open the Audit Manager Console, right click on the installation name (eg. DefaultInstallation [server.domain.com]) and select 'Management Databases'. Select the management database for this installation and select 'Connect'. This will open a separate MMC console with the same view. Try to attach the audit store once more - this time, the operation should succeed.

Following this workaround, a fresh sync should take place for what is defined within SQL vs AD, which will render the issue resolved.


 

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