Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Network Performance Monitor (NPM) > System.Data.SqlClient.SqlException (0x80131904): The Transaction log for database 'XXXX' is full due to 'XXXX' Transaction log

System.Data.SqlClient.SqlException (0x80131904): The Transaction log for database 'XXXX' is full due to 'XXXX' Transaction log

Created by Eric Bryant, last modified by MindTouch on Jun 23, 2016

Views: 1,335 Votes: 1 Revisions: 6

Overview

This article describes the issue about the following error that appears on the Orion website:

There was no endpoint listening at net.tcp://XXXX:17777/orion/core/businesslayer that could accept the message

 

In the Corebusinesslayer.log files, this error appears: 

System.Data.SqlClient.SqlException (0x80131904): The Transaction log for database 'XXXX' is full due to 'XXXX' Transaction log

 at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
   at System.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync()
   at System.Data.SqlClient.TdsParserStateObject.TryReadNetworkPacket()
   at System.Data.SqlClient.TdsParserStateObject.TryPrepareBuffer()
   at System.Data.SqlClient.TdsParserStateObject.TryReadByte(Byte& value)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at SolarWinds.InformationService.ChangeBroker.SqlChangeBrokerDAL.BulkUpdateSubscriptionDelivery(IDictionary`2 subscriptions)
ClientConnectionId:a2e659a8-18e5-4154-bdaa-50b07571d6f6
Error Number:-2,State:0,Class:11

Environment

All versions of Orion products

 

Cause 

This issue is caused by the transaction log being full on the Orion SQL server for the Orion database and not taking any scheduled transaction log backups. 

Resolution

  • (If Database Set to Full Recovery Model) take a transaction log backup to clear the the transaction log. Or set the recovery model to simple recovery.
  • Run the Configuration Wizard from the Orion application server.
  • Check the Drive space where LDF and MDF reside and see if partition full. 
  • Add more space to Drive if full.

 

 

 

Last modified
23:42, 22 Jun 2016

Tags

Classifications

Public