I downloaded the 1.00.04 beta and installation went well.

I navigated over to the authentication page and entered my password and hit update.  I got a warning message at the top that no authentication module was found and the default dnn would be used.  Is this ok?

I cleared all browser cache/files and restarted IE.  I clicked on login and got the following error (like previous).  While on the authentication page i also told DNN to hide the login box.  This did not seem to be working.  With respect to the option for registration i.e. none, private, public should this be set to something? Right now it is public.

 A critical error has occurred.
Object reference not set to an instance of an object.

I went to look at the event viewer and saw the following message.  This one is very similar to the first post.  I dont think the problem was resolved.

AssemblyVersion: 04.08.02
PortalID: 0
PortalName: Cincinnati Association of the Blind
UserID: -1
UserName:
ActiveTabID: 36
ActiveTabName: Home
RawURL: /Home/tabid/36/ctl/Login/Default.aspx?returnurl=%2fHome%2ftabid%2f36%2fctl%2fRegister%2fDefault.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://{IP HERE}/Home/tabid/36/ctl/Register/Default.aspx?returnurl=%2fHome%2ftabid%2f36%2fDefault.aspx
UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 00477e1c-3216-459e-aea8-5faa159b491d
InnerException: Object reference not set to an instance of an object.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.Modules.Admin.Authentication.Login.DisplayLoginControl
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Modules.Admin.Authentication.Login.DisplayLoginControl(AuthenticationLoginBase authLoginControl, Boolean addHeader, Boolean addFooter) at DotNetNuke.Modules.Admin.Authentication.Login.BindLogin() at DotNetNuke.Modules.Admin.Authentication.Login.ShowPanel() at DotNetNuke.Modules.Admin.Authentication.Login.Page_Load(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---
Source:
Server Name: CABWEB1

Hmm, still at a complete loss.

Thanks - dave

Not so quick.  I took a new user account and hit the dnn site. 

The IE window just stalled and never did render the home page.  Obviously the above modification did not resolve the problem.

I am still in the situation where the login control doesnt' allow users to log in and i get error object reference not found.  If i make the modification to the web.config authentication mode=windows then new users cannot get logged in.

Still frustrated. - dave