Unable to recreate FSAReporting Database when re-installing FSAreporting

book

Article ID: 100009278

calendar_today

Updated On:

Description

Error Message

Failed to connect to the SQL server “ServerName”
Check that This SQL server exist and is running. Your Vault Service account has the correct privileges.
 
To validate if this is the issue a Dtrace is needed, please perform the following steps on the EV server while re-creating the issue.
Dtrace the process FSAReportingConfigUtility for no less than 5 minutes while re-creating the issue.
Open the log file created and search for either of the following the strings:
 
(FSAReportingConfigUtility)  <9096> EV-H   {REPORTINGDBCONFIG.EN_US} Exception: Info: Diag: Type:Symantec.EnterpriseVault.OperationsManager.DataAccessLayer.MonitoringAccessDBException ST:   at Symantec.EnterpriseVault.OperationsManager.DataAccessLayer.Common.ConnectionProvider.OpenConnection()|   at Symantec.EnterpriseVault.OperationsManager.DataAccessLayer.Common.DBHelper.ExecuteNonQuery(SqlCommand cmd, ConnectionProvider connProvider)|   at Symantec.EnterpriseVault.OperationsManager.DataAccessLayer.Common.DBHelper.ExecuteNonQuery(String query, ConnectionProvider connProvider)|   at Symantec.EnterpriseVault.FSAReporting.Config.ReportingDBConfig.CreateReportingDB()
(FSAReportingConfigUtility) <9096> EV-M   {REPORTINGDBCONFIG.EN_US} Executing GrantAccessToEVOMUser
(FSAReportingConfigUtility) <9096> EV-M   {REPORTINGDBCONFIG.EN_US} ConnectionString is = Data Source=SQLServer1; Initial Catalog=EnterpriseVaultDirectory;Integrated Security=true; Pooling=false;
(FSAReportingConfigUtility) <9096> EV-M   {REPORTINGDBCONFIG.EN_US} Exception: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) at Symantec.EnterpriseVault.FSAReporting.Config.ReportingDBConfig.GrantAccessToEVOMUser()
(FSAReportingConfigUtility) <9096> EV-H   {REPORTINGCONFIGAPP.EN_US} Could not grant access EVOM Reporting User.

Cause

1. Windows Firewall enabled on Enterprise Vault Server and on SQL server.
2. No Named pipes enabled on the SQL server.
3. Named instance on SQL Server.
4. Old FSAReporting Database files exist on SQL Server.

Resolution

1. Make sure, Windows Firewall on Enterprise Vault Server and on SQL server is disabled.
2. Confirm, Named pipes enabled on the SQL server.
3. While recreating the FSAreporting database if there is named instance, need to select the SQL Server\Instance name in wizard.
4. If the earlier FSAreporting mdf and ldf file exist on the same location, move them to another location.

 

 

Issue/Introduction

While recreating the new FSAreporting database, using the FSAreporting configuration an error is returned and configuration fails.
Powered by Wolken Software