We had a requirement today to run a DotNetNuke Website in .Net 4.0 as some code we are using as part of the Microsoft CRM 2011 SDK require .Net 4.0. Problem is that with many of the DotNetNuke websites, they have some references that will cause this error when you flip your website worker process to 4.0. in IIS. This will give you an error that looks like this: Generates an error: Server Error in ‘/’ Application. Compilation Error Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately. Compiler Error Message: CS1703: An assembly with the same identity ‘System.Web.Extensions, Version=22.214.171.124, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ has already been imported. Try removing one of the duplicate references. Source Error: [No relevant source lines] Source File: Line: 0 Show Detailed Compiler Output: Interestingly too… Read More »DotNetNuke 6 running in .Net 4.0 Server Error in '/' Application Version=126.96.36.199 Version=188.8.131.52
Professional Web Support Services InteractiveWebs Support Services At InteractiveWebs we have years of experience with DotNetNuke, with more published modules on SnowCovered than any other module developer in the store. (And we don’t publish all our modules.) We have our own full time employed team of DNN developers. We have our own full time employed Server Administrators. We have our own Data Centres with our own equipment. We have Years of Professional DotNetNuke Development Experience. Quite literally there is no one who is more experienced with everything dotnetnuke. We Offer Paid Support Services for DotNetNuke We offer paid support services for DotNetNuke in an easy and covenant process. You advise us of the issue you are facing. We estimate an up front cost and advise you. If you decide to accept the quote, we will request that you buy the equivalent number of support tickets from our store. We will… Read More »Professional DotNetNuke Support Services
Understanding Activation InteractiveWebs DotNetNuke Modules require a license to be activates on each sub domain from which the module is accessed. The license is per sub domain, and NOT for each instance of DotNetNuke. A sub domain example is: www.domain.com dev1.domain.com domain.com In the case of domain.com and www.domain.com, these are considered as one single license. EVERY other sub domain needs it’s own license. If you activate a module on dev.domain.com then browse to the same module using another sub domain (like dev2.domain.com) the module will not be activate with the new sub domain in the browser URL. Trial Each module will automatically enter into a 100% functional TRIAL mode the first time you access the module with any particular sub domain. The trial period is automatically set from the date you first visit the module with any particular sub domain. Example If you access dev1.domain.com the module… Read More »InteractiveWebs DotNetNuke Module Licensing Help
DotNetNuke 05.06.03 Pain If you look at the project downloads for dotnetnuke, you will notice that the forums module has the latest version as: 05.00.01 And if you click the link from within this page: http://www.dotnetnuke.com/Resources/Downloads/Projects-Downloads.aspx 05.00.01 is exactly what you get. All sounds neat and tidy… right? Not really, because if you install the latest version of DotNetNuke 05.06.03 (an important security release) you will kill your forums. Dead as dead. And if you check around for an update of the forum module, you will not find one either in your Module Definitions, or in the DotNetNuke website. But keep looking to codeplex and you find this: 05.00.02 and what is strange, it is released before the DNN 05.06.03 update, like significantly before it… like 1 month. This Forum Update is NEEDED if you want the forum module to work on DNN 05.06.03 http://dnnforum.codeplex.com/releases/view/67840 Release Notes The same module… Read More »DotNetNuke Forum Module 05.00.02 The missing link!
If you see this error Could Not Load file or assembly NVelocity, Version=184.108.40.206, Culture-nutral, PublicKeyToken=null (Exception from HRESULT: 0x80131040) While using one of our DotNetNuke Modules. The solution is a simple one. Update all of the InteractiveWebs DotNetNuke Modules to the latest builds by downloading the latest release from here: http://www.interactivewebs.com/DotNetNukeModules/ModuleDownloads.aspx The Problem The problem stems from a change to some of the code library of some modules that share code with other modules. Updating all modules to the latest build will resolve this issue in all our modules.
We found an issue with what is the current release version of DotNetNuke Blog module 04.01.00 or 04.01.01. First up, we don’t know what the version number should actually be, as the compiled version on the download is 04.01.00 but the source code is referenced as 04.01.01. We presume there is some difference, but who knows what it is. Anyway The Problem The problem is that any forms on a page that run the blog module, will not allow form data to be validated. By validated, we are talking about ensuring a number is entered in a number field and text in a name filed etc. The cause is the blog module is using an old ASP.Net 1.0 validation function. While it should be using ASP.NET 2.0 with the updated validation behaviours as found here: http://msdn.microsoft.com/en-us/library/0ke7bxeh.aspx With this mistake, if you use Page.Validate on ASP.NET 2.0, page validation groups are… Read More »Problem With DNN Blog Module 04.01.00 – 01
DotNetNuke can use jQuery to enable popup style and image rotator effects. These are great and a big improvements on technologies like flash. However it is not hard to find two separately coded jQuery modules that can cause conflicts when used on the same page as each other. The Reason The reason in most cases is that modules can be hard coded to use their own version of jQuery. (Think of jQuery as a plugin that is required for the code to load onto the web page). The library that powers jQuery is often updated to include new features. Earlier version of DotNetNuke did not have any ability to load jQuery or reference it as “part” of the core of DNN. So for any module written for early DNN versions, the library plugin for jQuery needed to be included or referenced to an online source like the free Google jQuery… Read More »jQuery Conflicts in DotNetNuke Modules–Advanced Login
Having installed the Module to your DNN site. 1. Login to your site with Host or Admin permissions. 2. Navigate to the page you wish to add a form to. 3. From the DNN module menu select FEEDBACK DESIGNER and the Pane Location. 4. Select ADD to add the module to the seelcted pane. 5. You will see a warning message advising that the module has yet to be configured. This message will only be seen one time. 6. From the Complete Feedback Designer menu on the module, select CONFIGURE MODULE. 7. You are now presented with the Module Menu. From her select the options you wish to edit by clicking the corresponding CLICK HERE.
It is a long running issue with modules, site and generally is caused by a user logging into a DotNetNuke website that then calls on a page (usually on a dotnetnuke child) website that references a separate .aspx web page. Most often this is caused by the use of some java script that references external .aspx files in the script. While in an ideal world this would not cause a logout issue for DNN users, especially admin users. It does and in our most recent experience with this was an updated website that used the cute soft “cute editor”. This editor was working on dotnetnuke 4.9.5 sites, but due to it’s configuration and changes to the DotNetNuke 5x standards. No child portal would support it’s out of the box configuration after upgrading to dnn 5.6.0. The fix was to throw it away and use the Telerik RAD editor. Not a… Read More »DotNetNuke–Automatic Logout on Child Sites
DotNetNuke PortalAliasInfo objPortalAliasInfo) at DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest
Problem with Outlook Sync Task ‘SharePoint’ reported error 0x80040102 Outlook cannot connect to the SharePoint List. We experienced some errors with our DNN website recently. The errors were and interesting one and a combination of a few things. Actually took some work to understand. The problem we noticed was that in the Log Viewer, we found many General Exception Errors: AssemblyVersion: 5.6.0 PortalID: -1 PortalName: UserID: -1 UserName: ActiveTabID: -1 ActiveTabName: RawURL: /_vti_bin/lists.asmx AbsoluteURL: /_vti_bin/lists.asmx AbsoluteURLReferrer: UserAgent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; WOW64; Trident/4.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729) DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider ExceptionGUID: bla InnerException: Unhandled Error: FileName: FileLineNumber: 0 FileColumnNumber: 0 Method: DotNetNuke.Entities.Portals.PortalSettings..ctor StackTrace: Message: System.Exception: Unhandled Error: —> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabID, PortalAliasInfo objPortalAliasInfo) at DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) — End of inner exception… Read More »DotNetNuke PortalAliasInfo objPortalAliasInfo) at DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest
When trying to add a file attachment to the DotNetNuke forum module, we received an error that looked like this. An Error Has Occurred When Attempting To Save The File C:\webroot\site\site.com\wwwroot\Portals\0\Forums\Attachments\imge.jpg. Please Contact Your Hosting Provider To Ensure The Appropriate Security Settings Have Been Enabled On The Server. We stuffed around for a longer than normal time looking to fix this. We played with permissions on the website host server and folders, as in most of the forum posts about this error we found, they were all blindly looking at that as the problem. Solution Check the folder exists – Look in the folder structure to see if the /Forums/Attachments/ folder is actually there. Create it if is is not – In the website File Manager (ie under the Admin / File Manager DNN menu, create the Attachments folder. ensuring that you set permissions in that file manager to allow… Read More »DotNetNuke DNN An Error Has Occurred When Attempting To Save The File Forum Mdoule
Problem You are running the InteractiveWebs DNN word editor on a website. You upgrade your DNN site (usually past an early DNN 5 release) to a later DNN 5 release. After updating your DNN website, the word editor fails to publish and reports: HTML Module requires updating. Install ‘HTML 040802k PA.zip’ or higher to your website to re-enable word editing’. If you browse to: www.yourwebsite.com//desktopmodules/html/publishtoweb.asmx You will see: The type ‘PublishToWeb’ is ambiguous: it could come from assembly ‘C:\Inetpub\vhosts\yourwebsite.com\httpdocs\bin\App_SubCode_HTMLService.DLL’ or from assembly ‘C:\Inetpub\vhosts\yourwebsite.com\httpdocs\bin\DotNetNuke.Modules.Html.DLL’. Please specify the assembly explicitly in the type name. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Web.HttpException: The type ‘PublishToWeb’ is ambiguous: it could come from assembly ‘C:\Inetpub\vhosts\arctic-it.com\httpdocs\bin\App_SubCode_HTMLService.DLL’ or from assembly ‘C:\Inetpub\vhosts\arctic-it.com\httpdocs\bin\DotNetNuke.Modules.Html.DLL’. Please specify the assembly explicitly in the type name.… Read More »HTML Module requires updating. Install "HTML 040802k PA.zip