Dear dnn-fellows
I really need your help...
Perhaps this can say something more...
I can see in the log viewer (after upgrading) that by a sheduler Exception
the AssemblyVersion: -1
Sheduler exception
AssemblyVersion: -1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider:
ExceptionGUID:
InnerException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
FileName:
FileLineNumber: -1
FileColumnNumber: -1
Method:
StackTrace:
Message: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(SqlConnection connection, SqlTransaction transaction, CommandType commandType, String commandText, SqlParameter[] commandParameters, SqlConnectionOwnership connectionOwnership) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Services.Scheduling.DNNScheduling.SqlDataProvider.GetSchedule(String Server) at DotNetNuke.Services.Scheduling.DNNScheduling.SchedulingController.GetSchedule(String Server) at DotNetNuke.Services.Scheduling.DNNScheduling.CoreScheduler.LoadQueueFromTimer() at DotNetNuke.Services.Scheduling.DNNScheduling.CoreScheduler.Start()
Source:
Server Name: -------
And by a General Exception the AssemblyVersion is set to 03.03.04.
General Exception
AssemblyVersion: 03.03.04
PortalID: 1
PortalName: Givabo
UserID: -1
UserName:
ActiveTabID: 89
ActiveTabName: Home
RawURL: /default.aspx
AbsoluteURL: /default.aspx
AbsoluteURLReferrer: ----
UserAgent: Mozilla/4.0 (compatible; HostTracker.com/1.0;+http://host-tracker.com/)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 2220be02-82bb-401d-9e0f-3f3288db6437
InnerException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Data.SqlClient.SqlCommand.ExecuteReader
StackTrace:
Message: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(SqlConnection connection, SqlTransaction transaction, CommandType commandType, String commandText, SqlParameter[] commandParameters, SqlConnectionOwnership connectionOwnership) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Services.Scheduling.DNNScheduling.SqlDataProvider.GetNextScheduledTask(String Server) at DotNetNuke.Services.Scheduling.DNNScheduling.SchedulingController.GetNextScheduledTask(String Server) at DotNetNuke.Services.Scheduling.DNNScheduling.DNNScheduler.GetNextScheduledTask(String Server) at DotNetNuke.Services.Scheduling.SchedulingProvider.set_ScheduleLastPolled(DateTime Value) at DotNetNuke.Common.Global.Application_BeginRequest(Object sender, EventArgs e)
Source:
Server Name: -------
I think an upgrade process shall take me a lot of time and I'm afraid that not everything shall work... I shall have a lot of nightmares I think...
When you see that... Is it wise to try the upgrade to version 4.3.4?