Let It Shine DotNetNuke Support

Host Account is broken or forgotten

Mark Buelsing — Wed, 09 Jun 2010 10:10:44 GMT

If the host account is not working and there was only one, you are in trouble. However if you have access to the database, you can turn any other user into a host user account. Just open the Users table, and put a -1 in the IsSuperUser column for a user account you know. Then the next time you log in to that account, you will have host level access again.

If you are using a shared host, you might not have access to the database directly like this yet. You can ask for it, or you might just ask the technical support to perform this record update for you once.

Upgrading the Events Module causes it to report "Argument 'Length' must be greater or equal to zero."

Mark Buelsing — Sat, 10 Apr 2010 09:43:10 GMT

If you have upgraded the Events module and then when viewing the module’s page you are presented with the error: "Argument 'Length' must be greater or equal to zero.", there was a problem with one of the upgrade processes. You can read about it here.

http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/20/threadid/285350/scope/posts/threadpage/2/Default.aspx

But essentially, to fix it, you paste this code into the host, SQL window and run it as a script. It sets the module up to restart the upgrade process. After you run the script, go to the Host Settings and restart the application. Hopefully that will take care of it.

UPDATE {databaseOwner}{objectQualifier}EventQueue
SET IsComplete = 0,
Attributes = '<Attributes><Attribute><Name>BusinessControllerClass</Name><Value>DotNetNuke.Modules.Events.EventController, DotNetNuke.Modules.Events</Value></Attribute><Attribute><Name>DesktopModuleId</Name><Value>'
+ CONVERT(varchar, DesktopModuleID)
+ '</Value></Attribute><Attribute><Name>UpgradeVersionsList</Name><Value>04.01.00</Value></Attribute></Attributes>'
FROM {databaseOwner}{objectQualifier}EventQueue CROSS JOIN
{databaseOwner}{objectQualifier}DesktopModules
WHERE (EventQueue.EventMessageID IN
(SELECT MAX(EventMessageID) AS Expr1
FROM {databaseOwner}{objectQualifier}EventQueue AS EventQueue_1
WHERE (Attributes LIKE '%DotNetNuke.Modules.Events.EventController, DotNetNuke.Modules.Events%') AND
(ProcessorCommand = N'upgrademodule'))) AND (ModuleName = N'DNN_Events')
GO

Error when upgrading DNN: Executing Script: 05.01.00.SqlDataProvider Error!

Mark Buelsing — Thu, 01 Apr 2010 13:00:49 GMT

When upgrading DNN from 4.X to 5.X, if you see an error in the upgrade Status Report that looks like this:

00:00:00.046 - Upgrading to Version: 05.01.00
00:00:00.296 - Executing Script: 05.00.00.SqlDataProvider Success
00:00:05.859 - Executing Script: 05.00.01.SqlDataProvider Success
00:00:08.093 - Executing Script: 05.01.00.SqlDataProvider Error! (see 05.01.00.log for more information)
00:00:19.718 - Executing Application Upgrades: 05.00.00 Success
00:00:57.203 - Executing Application Upgrades: 05.00.01 Success

This is a relatively benign issue concerning the EventLog table. It can be safely ignored, however it will make your site just a little faster if you take care of it.

The following explanation was taken from a forum post found here: http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/107/threadid/315586/scope/posts/threadpage/2/Default.aspx

“When you upgrade a 04.09.04 install version with the upgrade script from 05.01.00, the script tries to (an succeeds) in adding a new bigint field (autonumber, not null) called "LogEventID". The script fails however in making this field the primary field.

You can manually remove the primary key from the field LogGUID (but leave the field in the table) and make the LogEventID a primary key. As already stated this error will have no impact on the application, however when it is not the primary key it will slow down performance when doing lookup's in the table with this field because it is not indexed”

Helferlein Form 2.00.0x Settings return an error

Mark Buelsing — Sun, 14 Mar 2010 19:18:18 GMT

The popular and free Helferlein form has a reported bug that shows an error message when attempting to get into the module settings. The work around is reported on the following link:

http://www.helferlein.com/Forum/tabid/195/forumid/3/threadid/1134/scope/posts/threadpage/4/language/en-US/Default.aspx

Specifically, the instructions state to copty the following SQL code and paste it into the SQL page in the host menu.

INSERT INTO {databaseOwner}{object Qualifier}PortalSettings(PortalID, SettingName, SettingValue)
VALUES(portalID, 'Security_EmailValidation', '\b[a-zA-Z0-9._%\-+'']+@[a-zA-Z0-9.\-]+\.[a-zA-Z]{2,4}\b')

I found that I had to actually edit the database in MS< SQL Server Management Studio and enter the missing record myself.

It did solve the problem.

Cannot insert the value NULL into column 'DefaultLanguage', table

Mark Buelsing — Sun, 31 Jan 2010 19:08:14 GMT

If you run DNN 5.01.00 or higher, and you see this error while trying to update your site settings:

Error: Site Settings is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Cannot insert the value NULL into column 'DefaultLanguage', table ...

The problem is the Default Language dropdown on the Site Settings page, Advanced Settings, Other Settings is null (empty), and DNN won't let you save the Site Settings with a null in this field. You can't choose a default language because the drop-down is empty.

Here's what to do:
1. Go to the Site menu and choose Languages.
2. Click the "Edit Language" link near the top of the page.
3. Click Enabled and Update - or choose a language and a fallback language - and then click the enabled checkbox.
4. Click Save at the bottom of the Languages page.
5. Now go back to the Site Settings page.
6. Go to Advanced Settings, Other Settings and choose a Default Language.
7. Now you can make your other Site Settings changes and you won't see the error.

My DNN Login page is broken!

Mark Buelsing — Fri, 29 Jan 2010 09:40:38 GMT

At one time or another, I've been faced with the problem that the DNN login page is broken. This can happen if the skin causes an error or a module on the same page throws an error or worse yet, you've assigned your login page to a page that does not have the login module on it yet and you logged out.

I have seen this a number of times and have assembled this short list of things to try. Hope it helps someone else out there!

Here is the first one. It's from John Mitchell. He has created a file that adds a login page to your site. Check out his post here: http://blogs.snapsis.com/CommentView,guid,3078311e-6925-4c03-8243-d1b9c8a11906.aspx

And here is the second, from Will Strohl
HOW TO : Access the DNN Login Page from Any Page - http://www.willstrohl.com/Blog/tabid/66/EntryId/118/HOW-TO-Access-the-DNN-Login-Page-from-Any-Page.aspx

Another way I have devised is to have a second portal on the install that has a valid working login page. I can login there and go to the host, portals and edit or view the non-working portal from there - already logged in as host. That one takes some pre-planning unfortunately.

And last of my suggestions is a concept only as I have not tried it yet, since one of the above has rescued me each time. Is the idea that a person could conceivably get access to the database, and insert a new login module on any existing page.