DNN

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

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

Adding .OFT Fonts to IIS Mime for DNN DotNetNuke

Making .OTF Font work in DotNetNuke DNN Skin To get a DotNetNuke DNN site to correctly display .OTF fonts, it is necessary to add a MIME type to IIS. Making this change is easy. In IIS, click on the Server Name.Double Click on MIME Types Add a New MIME Type – .otf – Font/otf That’s it. For good measure you could restart IIS from a command prompt with “IISRESET”