3 Replies Latest reply on Jul 1, 2008 8:37 AM by davidmaltby

    anyone had this same error with NTA?

    lchance

      Has anyone else seen or had this same error with NTA - causing the NTA Service to abend/stop?



       


        • Re: anyone had this same error with NTA?

          We need some additional information to diagnose this issue.  Please run SolarWindsDiagnostic.exe in the \program files\solarwinds\orion directory.  This will gather some logs and other information about your NetFlow configuration and the error that was received.  Then open a ticket with SolarWinds Technical Support and they'll ensure that the logs are sent to the development team.

          Is this the first time that the error has occured?

          Thanks,

            • Re: anyone had this same error with NTA?
              lchance

              It has not done this before. Isn't the 2am time when the daily Solarwinds SQL maintenance kick off?

              I have Orion on a Windows 2003 Enterprise server and the SQL 2005 database on another server.

              Here are three event messages from that time period in the Event Viewer SOLARWINDS.NET section:

              2008-06-25 02:24:46,729 [AlertCheckingThread] WARN Error - Error in GetAlertFromDatabase() -

              EXCEPTION STACK: --> A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) : .Net SqlClient Data Provider : 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.TdsParserStateObject.ThrowExceptionAndWarning()

              at System.Data.SqlClient.TdsParserStateObject.WriteSni()

              at System.Data.SqlClient.TdsParserStateObject.WritePacket(Byte flushMode)

              at System.Data.SqlClient.TdsParserStateObject.ExecuteFlush()

              at System.Data.SqlClient.TdsParser.TdsExecuteRPC(_SqlRPC[] rpcArray, Int32 timeout, Boolean inSchema, SqlNotificationRequest notificationRequest, TdsParserStateObject stateObj, Boolean isCommandProc)

              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(CommandBehavior behavior)

              at AlertingEngine.CheckAlert.GetAlertFromDateBase();;;

              ===============================================

              2008-06-25 02:24:46,760 [AlertCheckingThread] WARN Error - AlertDefID a3801546-35cb-4c0e-b737-4cec78fbec06 will halt processing due to the following error: Exception was thrown in GetAlertFromDatabase - EXCEPTION STACK: --> A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) : .Net SqlClient Data Provider : 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.TdsParserStateObject.ThrowExceptionAndWarning()

              at System.Data.SqlClient.TdsParserStateObject.WriteSni()

              at System.Data.SqlClient.TdsParserStateObject.WritePacket(Byte flushMode)

              at System.Data.SqlClient.TdsParserStateObject.ExecuteFlush()

              at System.Data.SqlClient.TdsParser.TdsExecuteRPC(_SqlRPC[] rpcArray, Int32 timeout, Boolean inSchema, SqlNotificationRequest notificationRequest, TdsParserStateObject stateObj, Boolean isCommandProc)

              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(CommandBehavior behavior)

              at AlertingEngine.CheckAlert.GetAlertFromDateBase();;;

              ===================================

              2008-06-25 02:24:46,760 [AlertCheckingThread] WARN Error - Exception in CheckAlerts.ClearOldAlerts.

              ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.

               

              Thanks.

                • Re: anyone had this same error with NTA?
                  davidmaltby

                  These exceptions from the Event log look to come from the "SolarWinds Alerting Engine" service.  But they probably occured for the same reason that the NTA service crashed.  If you look in the NTA install directory (by default C:\Program Files\SolarWinds\Orion\NetFlowTrafficAnalysis) and look through the swdebug.log files, you should hopefully find the exception in one of those files.  The entries, of course, are listed in time order.  Although, it looks like there is a database or network connectivity issue here, based on the Alerting engine exceptions, the NTA service should catch this exception and not crash, of course.  So, we'd really like to track this down in the NTA service and get it fixed.


                  Thanks,