DotNetNuke Support

BlogEvent ID 1310

DNN Event ID 1310 after moving website to new server Exception message: Unsecured Passwords Format Detected

IIS throwing Event ID 1310 Exception message: Unsecured Passwords Format Detected The Error Message Exception information: Exception type: ConfigurationErrorsException Exception message: Unsecured Passwords Format Detected. The Membership Provider that contains the unsecure passwords format is: AspNetSqlMembershipProvider. The obsoleted password format is: Encrypted. For more information, see https://go.microsoft.com/fwlink/?linkid=834784. Request information: Request URL: Request path: User host address: User: Is authenticated: False Authentication Type: Thread account name: IIS APPPOOL\DefaultAppPool The Problem was actually simple and a “user error” We tried to connect the website up to the wrong database. i.e. When we copied the database and moved it, we inadvertently copied the wrong database. This caused the above error due to the fact that the machinekey data in the web.config file was wrong for the database. This caused the error 1310 to be thrown and the Application Pool associated with the new incorrectly setup site to stop. The fix.  Connect to the… Read More »DNN Event ID 1310 after moving website to new server Exception message: Unsecured Passwords Format Detected

Google Analytics API Access V3

Accessing your Google Analytic Data via API To allow a third party module or application to view and display your Google Analytics data for your website. You need to get a few things organised. 1. You need to have a Google Analytic account with your website registered. Go to: http://www.google.com/analytics/   and follow their instructions to set up your URL under an account that you can manage and access with Admin permissions. We are not going to go through these steps here as it is a given that you will have this. Seek help from Google if you can’t manage.   2. Set up an API for your Google Analytics Account at the Google Developers Portal. Go to: https://developers.google.com/  and login with your account. To get started using Google Analytics API, you need to first create or select a project in the Google Developers Console and enable the API. Using this link guides… Read More »Google Analytics API Access V3

DotNetNuke FileHelpers, Version=2.0.0.0, Culture=neutral, PublicKeyToken=3e0c08d59cc3d657'

After Upgrading DNN 7 and browsing to the ADMIN>Site Settings you find an error: A critical error has occurred. Object reference not set to an instance of an object. FileHelpers, Version=2.0.0.0, Culture=neutral, PublicKeyToken=3e0c08d59cc3d657′ Error: File Management is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: (0): error CS1705: Assembly ‘DotNetNuke.Modules.DigitalAssets, Version=7.1.1.385, Culture=neutral, PublicKeyToken=null’ uses ‘Telerik.Web.UI, Version=2013.2.611.40, Culture=neutral, PublicKeyToken=121fae78165ba3d4’ which has a higher version than referenced assembly ‘Telerik.Web.UI, Version=2013.1.403.40, Culture=neutral, PublicKeyToken=121fae78165ba3d4’ —> System.Web.HttpCompileException: (0): error CS1705: Assembly ‘DotNetNuke.Modules.DigitalAssets, Version=7.1.1.385, Culture=neutral, PublicKeyToken=null’ uses ‘Telerik.Web.UI, Version=2013.2.611.40, Culture=neutral, PublicKeyToken=121fae78165ba3d4’ which has a higher version than referenced assembly ‘Telerik.Web.UI, Version=2013.1.403.40, Culture=neutral, PublicKeyToken=121fae78165ba3d4’ at System.Web.Compilation.AssemblyBuilder.Compile() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean ensureIsUpToDate) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at DotNetNuke.UI.Modules.WebFormsModuleControlFactory.CreateModuleControl(TemplateControl containerControl, ModuleInfo moduleConfiguration) at DotNetNuke.UI.Modules.ModuleControlFactory.LoadModuleControl(TemplateControl containerControl, ModuleInfo moduleConfiguration)… Read More »DotNetNuke FileHelpers, Version=2.0.0.0, Culture=neutral, PublicKeyToken=3e0c08d59cc3d657'

DotNetNuke DNN Spam Registrations Problem Fixed

DotNetNuke DNN Sites getting spam registrations – How to stop them In recent weeks, many of our DNN websites have systematically been targeted for Spam New User Registrations. There has been some discussion around the how and why, and as much as we can tell, the problem is this: 1. Some script kiddy has bothered to write a bot that finds DNN websites. It is not even a good bot, because it is not capable of validating registrations to automated active email addresses. (If you are the creator of the bot… “YOU ARE DOING IT WRONG” as it is not going to bring the Google results you are looking for.) 2. The bot will attempt access to:  www.yoursite.com /?ctl=Register 3. This brings into play the default DNN registration process module. 4. This page is currently available if your site has either Public or Verified registrations enabled. 5. Tricks on derating the… Read More »DotNetNuke DNN Spam Registrations Problem Fixed

DNN Popup Greeting–Kill it Good!

In the recent DNN 7 releases, they have unfortunately made by default a popup greeting after sign in, that in theory would drive clients to signup for their spam. Problem is (like lots of recent DNN features) that the “tick to never show again” does not work, and in some really recent releases, the popup goes crazy and does not allow you to progress into the site. In other words, they killed their own product with spam crap. Easy fix. Open the file in the web root, called: Default.aspx.cs Look for this line: ManageGettingStarted(); Just throw a // before it to comment it out. Save and restart the IIS site. Should fix it fast and for good.

DotNetNuke can’t upgrade as Host Login does not work

DotNetNuke Upgrade Fails. Cannot login with Host. If you are trying to upgrade your DotNetNuke site and found that you are presented with the Welcome to the DotNetNuke Upgrade Page, but can’t login with your Host (SuperUser) account. DotNetNuke Upgrade – Version 06.02.07 Current Version – 06.02.05 Welcome to the DotNetNuke Upgrade Page. The first step is to choose the language you wish to use for the Upgrade. You are about to upgrade your website to a more recent version of the DotNetNuke application. Applying upgrades on a consistent basis is the best way to ensure that you are protecting the integrity of your investment and the security of your users and assets. Before proceeding with the automated upgrade process please ensure that: you have made plans to first attempt this process in a staging environment you have documented your current installation characteristics including doing research on the compatibility of… Read More »DotNetNuke can’t upgrade as Host Login does not work

DotNetNuke – Could not load file or assembly 'Telerik.Web.UI' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference.

After upgrading a DNN website, we received this error message. The underlying cause of the problem is sloppy release version upgrades of the DNN core product. The issue is that the release.config file in the update versions of DNN references older versions of the Telerik.Web.UI .dll file in the /bin folder of the install versions of DNN. This means that the settings in your newly updated web.config file are referencing an old version of the Telerik file. The fix is easy Right click on the Telerik.Web.UI.dll file in your sites /bin folder. If the file is not there, then download the install version of your DNN site package from http://dotnetnuke.codeplex.com Then extract the file to the /bin folder. Look at the version number of the file. Edit your web.config file to match this data: Save and you are done.

DotNetNuke HTML Editor Background Black

When you get a black background in the HTML Editor. The solution is easy. Look for the file found here: \Providers\HtmlEditorProviders\Telerik\Config\ConfigDefault.xml Edit it to add this line: <property name="CssFiles">~/Providers/HtmlEditorProviders/Telerik/Config/EditorCustom.css</property> Looking like this: Then edit this file: \Providers\HtmlEditorProviders\Telerik\Config\EditorCustom.css To look like this: body {   background-color: white;   background-image: url(image_path);   color: black; }   That’s about it.

DotNetNuke Can’t Login Index #: 0

The Problem Index #: 0 Recently while working with a DotNetNuke website, we found that attempting to login to the site generated this error: SQL Exception Error Details File  Error   Index #: 0 Source: .Net SqlClient Data Provider Class: 17 Number: 1105 Procedure: AddEventLog Message: System.Data.SqlClient.SqlException: Could not allocate space for object ‘dbo.EventLog’.’PK_EventLogMaster’ in database ‘www.sitedatabase.com’ because the ‘PRIMARY’ filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. at System.Data.SqlClient.SqlConnection.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,… Read More »DotNetNuke Can’t Login Index #: 0

DotNetNuke (dnn) jQuery problems admin menu

DotNetNuke jQuery Problems Recently there was an update to jQuery that caused some problems with DotNetNuke. The problems include: Strange or missing popup effects in custom jQuery modules Admin menu hiding the menu items on Standard DNN Dark Knight Skin Modules using jQuery failing to function as desired The Problem The problem is associated with some bugs in the jQuery released and hosted googleapis. The bugs are not related to DotNetNuke directly but the jQuery used in many instances of jQuery. The Solution The solution is an easy one. You just need to login to your DotNetNuke website with a Host Account, and modify the jQuery settings under the HOST / ADVANCED SETTINGS to a more recent and bug free version of jQuery UI.   Pasting this URL: https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.23/jquery-ui.min.js into the “Hosted jQuery UI URL" and ensuring the “Use Hosted jQuery Version” is ticked.

DotNetNuke Event message: Forms authentication failed for the request. Reason: The ticket supplied was invalid. EventID 1315

The Problem We were receiving some really really strange behaviour with a dotnetnuke website. The log files showed: Event message: Forms authentication failed for the request. Reason: The ticket supplied was invalid. with EVENT ID 1315   The behaviour was this: Login with Internet Explorer worked. Login with some versions of firefox failed others worked Login with Chrome failed. When login failed, the browser would refresh and then show the page you were on before login. Now in this instance we tried nearly everything we could think of. we tried different application pools different.net settings in IIS. and we hand we have a good idea of both server management and asp.net. He also had is particularly confused that other DotNetNuke websites on this particular server were running just fine. To cut a long story short the problem turned out to be very specific that site we were using. Solution We… Read More »DotNetNuke Event message: Forms authentication failed for the request. Reason: The ticket supplied was invalid. EventID 1315

Upgrading Steps for DotNetNuke from DNN 4.x.x to DNN 6.x.x

Specifically we wanted to take a version of DotNetNuke from 4.9.1 to 6.1.3 today and actually found that it worked perfectly. We did take some steps that helped a lot. This may be of value to some of you. Before we Began 1. Backed up the entire file system for the website. 2. Backed up the database on SQL server for the site in question. 3. Ensured we had a HOST login account that worked. 4. Ensured the server we were running on (Windows 2008 R2) was patched and running .Net Framework version 3.5 SP1. 5. If your site is busy, work out a way to stop the traffic. One way is to add a portal alias, like test.domain.com in your DNN website. Setup a DNS entry to that test.domain.com points to the IP address of your DNN web server. In IIS, setup a Binding, so that test.domain.com will answer… Read More »Upgrading Steps for DotNetNuke from DNN 4.x.x to DNN 6.x.x

Problem Upgrading for DNN 4.9.5 to DotNetNuke 6x

During an update from DNN 4.9.5 to DNN 6x we experienced: All pages with HTML blank when logged out, but show this error logged in. Error: Services is currently unavailable.DotNetNuke.Services.Exceptions.ModuleLoadException: The type initializer for ‘DotNetNuke.Modules.Html.DataProvider’ threw an exception. —> System.TypeInitializationException: The type initializer for ‘DotNetNuke.Modules.Html.DataProvider’ threw an exception. —> System.InvalidCastException: Unable to cast object of type ‘DotNetNuke.Modules.HTML.SqlDataProvider’ to type ‘DotNetNuke.Modules.Html.DataProvider’. at DotNetNuke.Modules.Html.DataProvider.CreateProvider() — End of inner exception stack trace — at DotNetNuke.Modules.Html.WorkflowStateController.GetWorkflows(Int32 PortalID) at DotNetNuke.Modules.Html.HtmlTextController.GetWorkflow(Int32 ModuleId, Int32 TabId, Int32 PortalId) at DotNetNuke.Modules.Html.HtmlModule.OnInit(EventArgs e) — End of inner exception stack trace — Solution In our case, the upgrade left 2 things behind that DNN 6 did not like. in the app_code directory, we deleted the ‘HTML’ folder (since it does not seem that it was in use anymore and was potentially conflicting with new html module code) in web.config, I removed the following line in the <Codesubdirectories> section <add directoryName="HTML" />… Read More »Problem Upgrading for DNN 4.9.5 to DotNetNuke 6x