DotNetNuke FAQ's

The problem is that the user in the database is an "orphan". This means that there is no login id or password associated with the user. This is true even if there is a login id that matches the user, since there is a GUID (called a SID in Microsoft-speak) that has to match as well.

This used to be a pain to fix, but currently (SQL Server 2000, SP3) there is a stored procedure that does the heavy lifting.

All of these instructions should be done as a database admin, with the restored database selected.

First, make sure that this is the problem. This will lists the orphaned users:

EXEC sp_change_users_login 'Report'

If you already have a login id and password for this user, fix it by doing:

EXEC sp_change_users_login 'Auto_Fix', 'user'

If you want to create a new login id and password for this user, fix it by doing:

EXEC sp_change_users_login 'Auto_Fix', 'user', 'login', 'password'

We've been building DotNetNuke modules since the framework came out and we have a track record of completing visually detailed and functionally powerful web applications for various clients.

• None:
  This removes the registration link from your website. The administrators of your website can only add new users manually.
• Private:
  The register link appears. When a user registers, the administrators have to approve the user before the user will be granted access.
• Public:
  This is the default setting for your DotNetNuke portal. The register link appears. When a user registers, they are given instant access to your site as a member without any verification.
• Verified:
  The registration link appears. When a user registers, they are sent an email with a verification code. The first time they login, they are asked to enter the verification code, if they are verified correctly; they are given access to your site as a member. Once they are verified, they no longer need to enter the verification code