Since 2 days, I am trying to solve a problem and I could use some input. I had already noticed that there was a problem registring a new user, but I was hoping to solve this next weekend. For the rest, the new installation seemed to work fine. The version is still 05.04.04 and I intend to upgrade after the release of 05.05.01 which may be this week, I read in some blog.

Then a much more disabilitating error came up. I can no longer create new modules on my tab pages. When I try to "Add Module to Page" I get this error:

An error has occurred.
DotNetNuke.Services.Exceptions.ModuleLoadException: Cannot insert the value NULL into column 'IsDeleted', table 'KhmerSupport.dbo.TabModules'; column
does not allow nulls. INSERT fails. The statement has been terminated. ---> System.Data.SqlClient.SqlException: Cannot insert the value NULL into column 'IsDeleted', table 'KhmerSupport.dbo.TabModules'; column does not allow nulls. INSERT fails. The statement has been terminated. 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.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.Data.SqlDataProvider.AddTabModule(Int32 TabId, Int32 ModuleId, Int32 ModuleOrder, String PaneName, Int32 CacheTime, String CacheMethod, String Alignment, String Color, String Border, String IconFile, Int32 Visibility, String ContainerSrc, Boolean DisplayTitle, Boolean DisplayPrint, Boolean DisplaySyndicate, Boolean IsWebSlice, String WebSliceTitle, DateTime WebSliceExpiryDate, Int32 WebSliceTTL, Int32 createdByUserID) at DotNetNuke.Entities.Modules.ModuleController.AddModule(ModuleInfo objModule) at DotNetNuke.UI.ControlPanels.ControlPanelBase.AddNewModule(String title, Int32 desktopModuleId, String paneName, Int32 position, ViewPermissionType permissionType, String align) at DotNetNuke.UI.ControlPanels.IconBar.AddModule_Click(Object sender, EventArgs e) --- End of inner exception stack trace ---

I have mainly been looking at user permissions for the login account. But as far as I understand, all the account needs is db_owner membership, it does not need to have ownership of this role.

I have come to doubt my first conclusion that the error is related to permissions. It might be related to the transfer of the database and something that went wrong there. I still have a working copy locally and the changes are minor and stored separately, so I can start the process over again. But some advice about this error would be very welcome.

---

____________________________________
The one-eyed in the land of the blind.

I've solved it by scripting out the database again with VS 2008's Publish function because that's the only way I know to have a local copy of the script. I have then split up the script in 4 parts for easy consumption by SQL Management Studio on the destination site. Then I recreated the database on the remote SQL server and added a login and account for the dnn user and gave the account db_owner role. I then executed my scripts with the account I had just created. They ran without error (I had removed the Forum stored procedure with the error in advance from the source database)

After starting the IIS again, I had a perfectly running site and the error had disappeared :-)

It is a pitty after all that I am not yet sure of what went wrong the first time round. I still have a copy of the offending database, but this weekend I won't have the time to research this. I've already downloaded 05.05.01, and as tomorrow is a national holiday in Cambodia, I will have a lot of time to put 05.05.01 to a close inspection and hope by the end of the weekend to be able to upgrade the production site.

---

____________________________________
The one-eyed in the land of the blind.

yes, I encountered already the same issues, luckily for our support tasks we have systems running SQL Server 2005, 2008 and 2008R2.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN