gulfpaddler wrote
I figured this out. I should have thought about this a little more before I made the post. I am up and running! Still doesn't change the fact that this is a bug! I now just know to avoid it, and fix it if I accidentally do this again. jb
I spoke too soon. I got my site back by going to host settings and turning the banners setting to none and this allowed my child portal to reappear. I am ignoring altogether the banners set up provided through the skin and am using the banners module instead. This has been more successful in that the entire site doesn't crash now, however, I still can't get my Ad-Sense banner to display using the banners module using the banner options settings.
To the best of my understanding there are two ways to use banners in DNN:
1) by showing a banner by means of the skin setting: none, site or host. If you try to use this method the site will crash in dnn 4.0.2. So let’s forget this approach.
2) by adding a banners module to one of the panes on a page. Using this method, the site doesn’t crash. It displays the banner. Actually before you assign a particular banner using the banners module option setting, the banner module displays as a normal looking empty banners module: no errors. The error occurs when you use the banners option setting of the banners module to assign the script banner to the module. Then you get the error below. Please see the difference at www.gulfpaddler.net . The home page has the error module where I am trying to display the Google Ad-sense script module, and the feedback page has an empty module with no banner assignment.
It seems to me that the fix is to modify the stored procedure problem. Is there someone who can provide me the code for this stored procedure? Is the DNN interface calling the wrong sp? Does it simply need to be renamed? It seems that this would be a pretty simple patch to install. Please let me know what you think. Thanks, jb
Error: Banners is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: The stored procedure 'dbo.seba_FindBanners' doesn't exist. ---> System.InvalidOperationException: The stored procedure 'dbo.seba_FindBanners' doesn't exist. at System.Data.SqlClient.SqlCommand.DeriveParameters() at System.Data.SqlClient.SqlCommandBuilder.DeriveParameters(SqlCommand command) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.DiscoverSpParameterSet(SqlConnection connection, String spName, Boolean includeReturnValueParameter, Object[] parameterValues) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSetInternal(SqlConnection connection, String spName, Boolean includeReturnValueParameter) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName, Boolean includeReturnValueParameter) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Data.SqlDataProvider.FindBanners(Int32 PortalId, Int32 BannerTypeId, String GroupName) at DotNetNuke.Services.Vendors.BannerController.LoadBanners(Int32 PortalId, Int32 ModuleId, Int32 BannerTypeId, String GroupName, Int32 Banners) at DotNetNuke.Modules.Admin.Vendors.DisplayBanners.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---