after updating from 3.1.0 to DNN 3.1.1 I am still unable to view the eventlog, but this time with a different error message:
DotNetNuke.Services.Exceptions.ModuleLoadException: Parameter count does not match Parameter Value count. ---> System.ArgumentException: Parameter count does not match Parameter Value count. at Microsoft.ApplicationBlocks.Data.SqlHelper.AssignParameterValues(SqlParameter[]
commandParameters, Object[] parameterValues) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Services.Log.EventLog.DBLoggingProvider.Data.SqlDataProvider.GetLog(Int32
PageSize, Int32 PageIndex) at DotNetNuke.Services.Log.EventLog.DBLoggingProvider.DBLoggingProvider.GetLog(Int32 PageSize, Int32 PageIndex, Int32& TotalRecords) at DotNetNuke.Services.Log.EventLog.LogController.GetLog(Int32 PageSize, Int32 PageIndex, Int32&
TotalRecords) at DotNetNuke.Modules.Admin.Log.LogViewer.BindData() at DotNetNuke.Modules.Admin.Log.LogViewer.Page_Load(Object sender, EventArgs e) --- Ende der internen Ausnahmestapelüberwachung ---
One of the SQL scripts must have failed to run. Did you check the SQLDataProvider directory for any *.log files with a size greater than 1kb? That might shed some light on the problem. It definitely seems that at least one stored procedure is not in synch
with your assembly version.
I looked into the DotNetNuke\Providers\DataProviders\SqlDataProvider directory. There is no 03.01.01.log file. The last one is 03.01.00.log and is empty. But I can view the eventlog records with SELECT * FROM EVENTLOG in the SQL exec box. There I can see that
there is also a general exception regarding my 3rd party SSL module. I do not know if this is related.
"System.Data.SqlClient.SqlException: The constraint 'PK_Users' is being referenced by table 'NewBlog_Blogs', foreign key constraint 'FK_NewBlog_Blogs_Users'.
Could not drop constraint. See previous errors.
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, CommandType commandType, String commandText)
at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions)
ALTER TABLE dbo.Users
DROP CONSTRAINT PK_Users
System.Data.SqlClient.SqlException: Table 'Users' already has a primary key defined on it.
Could not create constraint. See previous errors.
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, CommandType commandType, String commandText)
at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions)
ALTER TABLE dbo.Users ADD CONSTRAINT
PK_Users PRIMARY KEY CLUSTERED
(
UserID
) ON [PRIMARY]
The last record of the version table says Major: 3, Minor: 1, Build: 0.
After overwriting DNN 3.1.0 with the new version the first hit with browser resulted in a crash. Complained about a reference with a 3rd party module (I believe it was SSL or Watchdog). After I removed two lines from default.aspx (added two lines for watchdog)
the portal came up again, but there was no red-black update screen like the previous 3.x updates.
"System.Data.SqlClient.SqlException: The constraint 'PK_Users' is being referenced by table 'NewBlog_Blogs', foreign key constraint 'FK_NewBlog_Blogs_Users'.
Could not drop constraint. See previous errors.
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, CommandType commandType, String commandText)
at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions)
ALTER TABLE dbo.Users
DROP CONSTRAINT PK_Users
System.Data.SqlClient.SqlException: Table 'Users' already has a primary key defined on it.
Could not create constraint. See previous errors.
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, CommandType commandType, String commandText)
at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions)
ALTER TABLE dbo.Users ADD CONSTRAINT
PK_Users PRIMARY KEY CLUSTERED
(
UserID
) ON [PRIMARY]
"
I've made a upgrade from 3.0.12.
Piotr, that looks like an issue with a 3rd party module (NewBlog) adding additional FK constraints to the users table. During the upgrade, we try to drop the existing FK, and then add back in an altered one, but the additional NewBlog one is causing the drop
to fail, which then causes the alter to fail. You'll need to manually remove the additional FK constraint before running the upgrade.
DocHoliday
Contributor
2360 Points
472 Posts
DNN 3.1.1 Eventlog not available
Aug 22, 2005 09:22 AM|LINK
after updating from 3.1.0 to DNN 3.1.1 I am still unable to view the eventlog, but this time with a different error message:
DotNetNuke.Services.Exceptions.ModuleLoadException: Parameter count does not match Parameter Value count. ---> System.ArgumentException: Parameter count does not match Parameter Value count. at Microsoft.ApplicationBlocks.Data.SqlHelper.AssignParameterValues(SqlParameter[] commandParameters, Object[] parameterValues) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Services.Log.EventLog.DBLoggingProvider.Data.SqlDataProvider.GetLog(Int32 PageSize, Int32 PageIndex) at DotNetNuke.Services.Log.EventLog.DBLoggingProvider.DBLoggingProvider.GetLog(Int32 PageSize, Int32 PageIndex, Int32& TotalRecords) at DotNetNuke.Services.Log.EventLog.LogController.GetLog(Int32 PageSize, Int32 PageIndex, Int32& TotalRecords) at DotNetNuke.Modules.Admin.Log.LogViewer.BindData() at DotNetNuke.Modules.Admin.Log.LogViewer.Page_Load(Object sender, EventArgs e) --- Ende der internen Ausnahmestapelüberwachung ---
[:P]
Cheers,
DocHoliday
DocHoliday
Contributor
2360 Points
472 Posts
Re: DNN 3.1.1 Eventlog not available
Aug 22, 2005 09:27 AM|LINK
No recovery.
Cheers,
DocHoliday
pogar
Member
220 Points
44 Posts
Re: DNN 3.1.1 Eventlog not available
Aug 22, 2005 11:32 AM|LINK
Piotr Gardy
pogar@i.hate.spam.pp.org.pl
BigWebmaster
Contributor
5850 Points
1170 Posts
Re: DNN 3.1.1 Eventlog not available
Aug 22, 2005 12:12 PM|LINK
Dan
DocHoliday
Contributor
2360 Points
472 Posts
Re: DNN 3.1.1 Eventlog not available
Aug 22, 2005 12:29 PM|LINK
I looked into the DotNetNuke\Providers\DataProviders\SqlDataProvider directory. There is no 03.01.01.log file. The last one is 03.01.00.log and is empty. But I can view the eventlog records with SELECT * FROM EVENTLOG in the SQL exec box. There I can see that there is also a general exception regarding my 3rd party SSL module. I do not know if this is related.
Cheers,
DocHoliday
pogar
Member
220 Points
44 Posts
Re: DNN 3.1.1 Eventlog not available
Aug 22, 2005 12:30 PM|LINK
"System.Data.SqlClient.SqlException: The constraint 'PK_Users' is being referenced by table 'NewBlog_Blogs', foreign key constraint 'FK_NewBlog_Blogs_Users'.
Could not drop constraint. See previous errors.
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, CommandType commandType, String commandText)
at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions)
ALTER TABLE dbo.Users
DROP CONSTRAINT PK_Users
System.Data.SqlClient.SqlException: Table 'Users' already has a primary key defined on it.
Could not create constraint. See previous errors.
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, CommandType commandType, String commandText)
at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions)
ALTER TABLE dbo.Users ADD CONSTRAINT
PK_Users PRIMARY KEY CLUSTERED
(
UserID
) ON [PRIMARY]
"
I've made a upgrade from 3.0.12.
Piotr Gardy
pogar@i.hate.spam.pp.org.pl
BigWebmaster
Contributor
5850 Points
1170 Posts
Re: DNN 3.1.1 Eventlog not available
Aug 22, 2005 12:39 PM|LINK
Dan
DocHoliday
Contributor
2360 Points
472 Posts
Re: DNN 3.1.1 Eventlog not available
Aug 22, 2005 12:54 PM|LINK
After overwriting DNN 3.1.0 with the new version the first hit with browser resulted in a crash. Complained about a reference with a 3rd party module (I believe it was SSL or Watchdog). After I removed two lines from default.aspx (added two lines for watchdog) the portal came up again, but there was no red-black update screen like the previous 3.x updates.
Cheers,
DocHoliday
cathal
Star
13648 Points
2702 Posts
MVP
Re: DNN 3.1.1 Eventlog not available
Aug 22, 2005 01:02 PM|LINK
Doc, please check and remove any dnn.config file, it may be caching the upgrade version or set UseDnnConfig to False in your web.config
Cathal
cathal
Star
13648 Points
2702 Posts
MVP
Re: DNN 3.1.1 Eventlog not available
Aug 22, 2005 01:04 PM|LINK
Piotr, that looks like an issue with a 3rd party module (NewBlog) adding additional FK constraints to the users table. During the upgrade, we try to drop the existing FK, and then add back in an altered one, but the additional NewBlog one is causing the drop to fail, which then causes the alter to fail. You'll need to manually remove the additional FK constraint before running the upgrade.
Cathal