Right after a new user agrees to "Rules and Policies", when it redirects to the registration page,

/default.aspx?g=register

the following error occurs:

Server Error in '/' Application.

Object reference not set to an instance of an object.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[NullReferenceException: Object reference not set to an instance of an object.]

YAF.Pages.register.FillLocationData(DropDownList country, DropDownList timeZones) +726

YAF.Pages.register.Page_Load(Object sender, EventArgs e) +2192

System.EventHandler.Invoke(Object sender, EventArgs e) +0

System.Web.UI.Control.LoadRecursive() +70

System.Web.UI.Control.LoadRecursive() +189

System.Web.UI.Control.LoadRecursive() +189

System.Web.UI.Control.LoadRecursive() +189

System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3177

Anyway, here are my stats:

SQL Server Version:

What version of SQL Server is running. Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64) Jun 17 2011 00:54:03 Copyright (c) Microsoft Corporation Developer Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1)

Operating System:

What version of operating system is running. Microsoft Windows NT 6.2.9200.0

.NET Runtime Version:

What .NET Runtime is running. .NET 4.0.30319.18051

Processor Cores:

Number of Processor cores. 6

Application memory:

Application memory used. 210 MB of 329 MB

This is an known issue (and fixed in yaf 2.1) when geolocation service is enabled it will only crash when you load the register page locally on the server.

The only workaround is to disable that feature, until the next version comes out.