Hi,

I Upgraded my DNN version from 6.02 to 6.02.01 and made some setting changes. The site was working fine for a day, but next day I dont know what happened I started getting below error on the webpage. Can any one help and throw some light on this issue?

SQL Exception

Error Details

 

File

Error

Index #: 0 Source: .Net SqlClient Data Provider Class: 21 Number: 21 Procedure: AddEventLog Message: System.Data.SqlClient.SqlException (0x80131904): Warning: Fatal error 9001 occurred at Aug 5 2012 11:45PM. Note the error and time, and contact your system administrator. at System.Data.SqlClient.SqlConnection. (SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection. (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.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.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Services.Log.EventLog.DBLoggingProvider.SqlDataProvider.AddLog(String logGUID, String logTypeKey, Int32 logUserID, String logUserName, Int32 logPortalID, String logPortalName, DateTime logCreateDate, String logServerName, String logProperties, Int32 logConfigID) at DotNetNuke.Services.Log.EventLog.DBLoggingProvider.DBLoggingProvider.WriteLog(LogQueueItem logQueueItem)

---

Thanks Sushil

Here at Network Solution we had a long day with this issue, and finally we expertise and solved this specific error (Fatal Error 9001) at server configuration level.

Result of our work is a shared server where newly created DB are 9001-free thanks to our config scripts (made in years of expertise), preconfigured with the SessionState DB, the ideal for Windows-IIS-ASP.NET-MSSQL shared hosting!

Please contact me to see if our solution is applicable in your case to definitely solve the root cause of this annoying issue