Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > SolarWinds Information Service V3 fails to start

SolarWinds Information Service V3 fails to start

Created by Chris Klinedinst, last modified by Caroline Juszczak on Mar 16, 2018

Views: 3,608 Votes: 0 Revisions: 7

Overview

The Solarwinds Information Service v3will not start up correctly. The Service will show as running but does not accept any new requests.

The following error appears in the Orion Information Service log:

2016-01-27 11:09:54,651 [4] INFO  SolarWinds.Data.Providers.Orion.Containers.LimitationSnapshotService.LimitationSnapshotService - (null)     Starting limitation snapshost service e92e7dd9-bee1-4803-91fe-779c89099c89
2016-01-27 11:09:54,856 [4] ERROR SolarWinds.Data.Providers.Orion.Containers.LimitationSnapshotService.DAL.LimitationSnapshotDAL - (null)     Cannot purge orphaned Limitation Snapshots. System.Data.SqlClient.SqlException (0x80131904): The transaction log for database 'SolarWindsOrionNew' is full due to 'LOG_BACKUP'. 
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
   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(CommandBehavior behavior)
   at SolarWinds.Orion.Common.SqlHelper.ExecuteReader(SqlCommand command, SqlConnection connection, SqlTransaction transaction, CommandBehavior behavior)
   at SolarWinds.Data.Providers.Orion.Containers.LimitationSnapshotService.DAL.LimitationSnapshotDAL.DeleteOrphanedSnapshots()
ClientConnectionId:6f67de8f-8de5-465f-b5f1-887526e26e5e

Environment

All NPM versions

Cause 

The Transaction Log on the SQL Server is full.

Resolution

 

References

SQL Server - MSDN

DBCC - MSDN

Transaction Log - MSDN

SQL Files - MSDN

 

Last modified

Tags

Classifications

Public