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 tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off".

I entered the customeErrors right under the system.web in the webconfig as instructed. This same error still comes up.  Is this because it hassnt really "built" the site yet?  Does anyone know how to determine what is causing the error? 

Site = www.chickenplus.info

       

Hi Mark,

Is this a fresh installation, or is it an additional portal somewhere?

Double check your database is set up correctly, the web.config file points to the database, the permissions are correctly setup for your DotNetNuke files, and that you are using ASP.NET 2.0

Thanks,

Hi lee,

This is a new 4.5.5 installation.  I setup all the folders with minimal RW some with RWW.   The folder that is acting like the root, has the root permisions checked. 

I can not check on the individual file permissions, godaddy dosent allow that , and when I asked them to check on it, they said they could not provide application specific information.

I wondered that if Default.aspx wasnt enabled as a default file in the IIS could that casue the problem, I have asked that question as well.  I just wish there was some way to see what the acutal error is

AS far as the database goes. I have to use the godaddy script which is pretty simple. The you click on an icon and godaddy provides you with the string that you can copy and past.  I then checked the way I had the string entered to a known working webconfig and they were the same.
I changed the password and made the change in the string to make sure I had entered that correctly as well.
The only difference between the one I setup manually and the one their script setup is I chose to create DSN and Schema.

I just told it to uninstall the DSN and Schema so the database of the almost working site will match the database of the non working site.