Help, this is driving me crazy.

I can create a child portal without any problem but whenever I try to create a parent portal with a URL like parent.someurl.com I get an error.  My subdomain points to the same directory as the main domain which I recall I have used before in earlier versions of DNN with success.  I am using DNN 4.3.5 and my main portal is called portals.mydomain.com but I get the same problem on another of my domains which starts with www.mydomain.com so I doubt that is the problem.  The error I get is:

Server Error in '/' Application.

---

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

Any help would be appreciated.

Taz

Once you get the hang of how these things work, it's not too challenging. But yes there is a little bit of thought involved.. I created a video a few months back that discusses Portals - Information is here - And it's free for registered users to download here.

I don't think you need an entirely new installation if its working correctly except the child portals, but I suppose we get faster with each installation don't we!!

Nina Meiers