leupold wrote
if you updated portal alias, you need to make sure, that the new domain is routed correctly to your web site by name server and IIS (IP, host header), depending on server configuration. Make sure asl well to restart application and clear cache from Host Settings after database changes to get data reloaded.
The domain has been on the server for a long time and I can switch it back and forth and resolve hello world.htm easily; its DNN. I've restarted IIS many times and restarted the server as well.... can't get to Host Settings because the site won't browse at all.
This is a test server with only test domains on it now, the problem is I developed a site on it took it live for a few months with Catalook; got 700 customer orders then switched it to a hosting company on another platform and now can't get to my customer data through browsing DNN under a new domain name that is setup properly. I thought by editing the DB table for portal alias it would work, but doesn't.
Both with the domain I'm trying to use and others I have 3 or 4 instances of DNN. I know get a familiar DNN error screen here:
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>
|
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
|
Server Error in '/' Application.
Runtime Error