Hi All
I am a complete newbie to this thread and the software itself. I had a ticket hit my queue for the above error. It occurs after logging into
Orion through web browser and get the following screen.

Have tried restarting the solar winds orion module service
Reinstalling the information service as in the following KB Print Article - I am receiving errors in the Orion Web Console
We have some SQL errors in the logs:
From Solar winds AlertingEngine:
2015-08-13 16:46:38,481 [MainTaskThread] ERROR All - Exception in MainTask Loop - Unable to create DB connection sleeping 30 seconds
and
2015-08-13 16:46:38,481 [MainTaskThread] ERROR All - Error in SetupDBConnection System.Data.SqlClient.SqlException: The transaction log for database 'Netperfmon' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
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.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 AlertingEngine.SWAlertingEngine.SetupDBConnection(SqlConnection& DBConnection, SqlCommand& DBCommand, SqlDataReader& DBReader)
Had our Dev team look at it and they created more space but events still persist (not sure if a red herring)
Have rebooted the server several times and also installed information service a few times with no luck.
Any assistance would be greatly appreciated
Kind Regards
Adrian