I was giving a presentation at an Open Source event this morning to over 300 business IT managers.
I was parading DotNetNuke 4.9.1 to the audience and installed DNN on a Win2003 Server (clean machine). Everything went to plan. I setup a basic DNN installation, 8 pages, a forum and contact form. I then setup a portal alias for a customer only portal called "Customers" and one for suppliers called "Suppliers".
So I had the main site located at http://192.123.151.1/ and the child portals as http://192.123.151.1/cusomters etc
I explained what was possible with have a child portal and then proceeded to delete the portals from the Host > Portals page.
Bang, I got this error when I attempted to delete the first child portal:
############################################
Error: Portals is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression. The statement has been terminated. ---> System.Data.SqlClient.SqlException: Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression. 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.DeletePortalInfo(Int32 PortalId) at DotNetNuke.Entities.Portals.PortalController.DeletePortalInfo(Int32 PortalId) at DotNetNuke.Entities.Portals.PortalController.DeletePortal(PortalInfo portal, String serverPath) at DotNetNuke.Modules.Admin.Portals.Portals.grdPortals_DeleteCommand(Object source, DataGridCommandEventArgs e) in C:\DNN491\Admin\Portal\Portals.ascx.vb:line 394 --- End of inner exception stack trace ---
#######################################
Needless to say I was the laughing stock of the conference, the tweets are flowing all afternoon about it.
The conference had other .net and .php Open Source applications on display and DNN came away with its tail between its legs.
Just to be clear, this was a DNN 4.9.1 download from Codeplex, a clean Windows Server 2003 with SQL Enterprise and .NET 2+3.5
Installation went as follows:
Setup db in SQL.
Download DNN Installation zip from CodePlex.
Unzip into folder and give permissions.
Create website in IIS.
Run DNN Installation.
Create 8 basic Pages in DNN
Create Forum Page and install Forum Module
Create Customer Child Portal with alias
Create Supplier Child Portal with alias
Delete Customer Child Portal from Host > Portals ==== bang
We have recreated the exact same scenario on two machines in the office, one with Server 2003 and one with XP Pro with the exact same results.
Anybody have any ideas as to the reasons for this ?