2 Replies Latest reply on May 28, 2009 1:05 PM by r0berth1

    Orion Errors

    r0berth1

      Has anyone seen the following errors?


      Source .NET Runtime 2.0 Error
      Event ID 5001
      Bucket 355532195, bucket table 5, EventType clr20r3, P1 solarwinds.businesslayerhost.exe, P2 9.1.0.328, P3 48e402ab, P4 system.data, P5 2.0.0.0, P6 471ebf27, P7 23cb, P8 295, P9 system.data.sqlclient.sql, P10 NIL.


       Event ID: 1024
      Source: SolarWinds.APM.BusinessLayer
      Type: Error
      Description: Unhandled Exception caught in APM Service Engine startup. Could not find stored procedure 'apm_AddEvent'.


      Event ID: 1024
      Source: SolarWinds.NPM.BusinessLayer
      Type: Error
      Description: Unhandled Exception caught in NPM Service Engine startup. An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)


      Event ID: 4001
      Source: SolarWinds.NPM.BusinessLayer
      Type: Error
      Description: Service was unable to open new database connection when requested.
      Exception An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
      Connection string - Data Source=msdcor02;Initial Catalog=NetPerfMon;User ID=SolarWindsNPM;Password=*******;Connect Timeout=20;Load Balance Timeout=120;Workstation ID=MSDCOR01


        • Re: Orion Errors
          John King

          I am currently experiencing those errors as well as a few others in some limited situations (alerts not firing for some nodes). They were found when I submitted a diagnostic to SW support. Have you had any luck in determining the cause/avoidance of these errors? Waiting on a DBA to take a look sometime next week.