I have a brand new install of DNN 4.9 and am attempting my first DNN site.

I have a simple site with a custom skin.  It works fine if I RDP to the server and access it via localhost, but if I try to get at the page from a different machine it errors with:

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

Source Error:

Line 603:            Dim objSkin As UI.Skins.SkinInfo
Line 604:
Line 605:            PortalId = objPortalAliasInfo.PortalID
Line 606:
Line 607:            ' get portal settings

I found threads regarding this type of error on older versions, and the fix was to change permissions on the directories to allow write.  I tried this but with no success.  I granted write access to both "NETWORK SERVICE" and "IIS_WPG" on both the DotNetNuke directory and its website subdirectory.  I even granted it to the anonymous user account just to be sure. 

Am I still missing a write permission, or is it another problem entierly?

The Event View stack trace:

AssemblyVersion: 04.09.00
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL: /dotnetnuke/website/Default.aspx
AbsoluteURL: /dotnetnuke/website/Default.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2; WOW64; InfoPath.1; .NET CLR 2.0.50727; .NET CLR 1.1.4322; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; .NET CLR 3.5.30428)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: d083deca-c04c-41e7-b444-76e0752007b2
InnerException: Unhandled Error:
FileName: C:\Inetpub\wwwroot\DotNetNuke\Library\Components\Portal\PortalSettings.vb
FileLineNumber: 605
FileColumnNumber: 13
Method: DotNetNuke.Entities.Portals.PortalSettings.GetPortalSettings
StackTrace:
Message: System.Exception: Unhandled Error: ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Entities.Portals.PortalSettings.GetPortalSettings(Int32 TabId, PortalAliasInfo objPortalAliasInfo) in C:\Inetpub\wwwroot\DotNetNuke\Library\Components\Portal\PortalSettings.vb:line 605 at DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabId, PortalAliasInfo objPortalAliasInfo) in C:\Inetpub\wwwroot\DotNetNuke\Library\Components\Portal\PortalSettings.vb:line 551 at DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) in C:\Inetpub\wwwroot\DotNetNuke\Library\HttpModules\UrlRewrite\UrlRewriteModule.vb:line 484 at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) --- End of inner exception stack trace ---

Alan

I agree with your assessment.  To extend what you said, you can do this via the database directly in the PortalAlias table on the server or you can make the change on your local machine under Admin > Site Settings (note you must be logged in as Host).  At the bottom of the page you will see Portal Aliases, choose add and add the FQDN and then save.  After that, push the updated db to the server and you should be up and running.

If this does not work, please post a reply and we can assist from there.

Best Regards,

Robert J Collins | Co-Founder & President

Netlogic Corporation

Adding the IP of the server as an additional alias did not correct the problem