|
|
|
|
when using previous versions of DNN, make sure, the database is using max compatibility level (like done by executing my TurboDBConfig803.sql)
|
|
|
|
| |
|
|
Joined: 1/1/0001
Posts: 0
|
|
|
I think I tracked it down to a conflict between having SQL Server 2012 and 2016 on the same server. Since the back up I received from the host is 2016 and you can't restore down to an earlier version, I have a lot of databases to move to 2016. Hope this resolves the issue.
|
|
|
|
| |
|
|
Joined: 1/1/0001
Posts: 0
|
|
|
I backed up my data, then removed SQL 2012. I am now able to clone an existing site using the backup from our site out on the hosting server, but trying to create the dnndev.me site for module development gives me this when I try to go to the site. I have seen several reports of this behavior when trying to go to a new site
http://dnndev.me/Default.aspx?tabid=59&error=Object+reference+not+set+to+an+instance+of+an+object.&content=0
Since it has been going on for several versions, I can only hope that I am just not finding the fix. Here is what I am getting now since running the TurboDNN804.sql script, which is at least trying to tell me something useful. Sure enough, the sp, AddEventLog is not present. It IS present in the backup copy of the site I got from my hosting company, so. . . . .????
SQL Exception
Error Details
File |
|
Error |
Index #: 0
Source: .Net SqlClient Data Provider
Class: 16
Number: 2812
Procedure:
Message: System.Data.SqlClient.SqlException (0x80131904): Could not find stored procedure 'dbo.AddEventLog'. at System.Data.SqlClient.SqlConnection. (SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() 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, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds, Boolean describeParameterEncryptionRequest) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteScalar() at PetaPoco.Database.ExecuteScalar[T](String sql, Object[] args) at DotNetNuke.Data.PetaPoco.PetaPocoHelper.ExecuteScalar[T](String connectionString, CommandType type, String sql, Object[] args) at DotNetNuke.Data.SqlDataProvider.ExecuteScalar[T](String procedureName, Object[] commandParameters) at DotNetNuke.Data.DataProvider.AddLog(String logGUID, String logTypeKey, Int32 logUserID, String logUserName, Int32 logPortalID, String logPortalName, DateTime logCreateDate, String logServerName, String logProperties, Int32 logConfigID, ExceptionInfo exception, Boolean notificationActive) at DotNetNuke.Services.Log.EventLog.DBLoggingProvider.WriteLog(LogQueueItem logQueueItem) ClientConnectionId:0411353b-652b-4521-8145-a4b59bf0fa29 Error Number:2812,State:62,Class:16 |
|
|
|
|
| |
|
|
Joined: 1/1/0001
Posts: 0
|
|
|
DNN 8.0.0 installed without trouble. Must be the version. Even after I purged anything SQL 2012 from my server, 8.0.3 was still not installing correctly. At least I can move ahead now. Thanks for looking at this.
|
|
|
|
| |
|
|
|
jschlosser wrote:
I think I tracked it down to a conflict between having SQL Server 2012 and 2016 on the same server. Since the back up I received from the host is 2016 and you can't restore down to an earlier version, I have a lot of databases to move to 2016. Hope this resolves the issue.
AFAIK, Microsoft supports side by side installation of both versions. However, using same instance for all sites should be most efficient.
|
|
|
|
| |