Error: 'A severe error occurred on the current command. The results, if any, should be discarded' during reporting data synchronization job run

Products

• Control Compliance Suite Windows

Issue/Introduction

Symptoms
Following error is displayed in the DPS logs

ReportSyncJob [7f5c12ce-19c8-45e8-b8a1-f28ac77a33c6-2] - [RPTG_ReportSyncJob] Error executing reporting database synchronization. Assembly Type: Symantec.CSM.Reporting.ManagedSync.EMScheduleSync, Symantec.CSM.Reporting.ManagedSync : System.Data.SqlClient.SqlException: A severe error occurred on the current command. The results, if any, should be discarded.

at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.SetMetaData(_SqlMetaDataSet metaData, Boolean moreInfo)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader()
at Symantec.CSM.Reporting.ManagedSync.IntegrationDBHelper.WaitForJobStart(String jobName)
at Symantec.CSM.Reporting.ManagedSync.IntegrationDBHelper.ExecuteJobSynchronously(String jobName)
at Symantec.CSM.Reporting.ManagedSync.EMScheduleSync.Execute(String adamHostAndPort, String parameterXML, Dictionary`2 dictConnString)
at Symantec.Blade.WorkerProcess.ReportSyncJob.ExecuteSync(IReportingSync reportingSync, String syncType, String adamHostAndPort, String parameterXML, Dictionary`2 dictConnString)

 

Cause

SQL commands are getting timed out before completion

Resolution

Increase the SQL.Command time out and Connection timeout values to resolve the issue. Follow the steps below to increase the time-outs

1. On the Application server machine, locate the AppserverService.exe.config file. It is present in the Application Server directory
2. Locate the following key under appsettings section

<add key="SQLCommandTimeout"value="30" />

3. Change the current value to it's at least it's double.
4. Save the changes and restart the application server service.

Additionally you may also increase the connection timeout settings in DPS config files Symantec.CSM.DPS.exe.config and Blade.WorkerProcess.exe.config

5. If the issue does not get resolved by following steps 1-4, repeat the steps a couple of times. Contact the Technical Support if it still does not get resolved.