Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Godaddy and 4.3.5 Install instructionsGodaddy and 4.3.5 Install instructions
Previous
 
Next
New Post
10/24/2006 9:07 PM
 

I think I followed the directions  When I attempted to load the site for the first time, I get the following error:

Server Error in '/Main' 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>

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>

The web.config already has <customErrors mode="RemoteOnly"/> but does not include the redirect.  I was not really interesting in redirecting, but interested in seeing the actual errors.  I did go into the database and there are many tables that have been created.  But without knowning the problem, I am not sure what needs fixing...

Any help would be appreciated.  I did also verify my directory settings (read, write, web, set root, but not browse).

 
New Post
10/25/2006 8:18 AM
 

I now understand that I needed to set the customErrors mode="off" and now I am getting:

The files '/Main/App_Code/ModuleName/Info.cs' and '/Main/App_Code/ModuleName/Controller.vb' use a different language, which is not allowed since they need to be compiled together.

Is this something I have any control over?  I installed the 4.3.5 Starterkit if that matters...

 
New Post
11/1/2006 9:01 AM
 
I have gone to the full source and have now regressed.  I did copy the subdirectory where I unzipped everything into a local virtual directory and ran the install as a check.  I created the godaddy directory with the permissions.  I uploaded the contents of the website directory into the directory created.  When I attempt to goto that directory to do the install, it is failing with the

ERROR: Could not connect to database specified in connectionString for SqlDataProvider

I have gone through the steps several times and not sure what I am missing.  Here is my database info:

 
SQL Server Database Information
Host Name whsql-v11.prod.mesa1.secureserver.net
Database Name DB_96582

and my web.config info:

connectionString="Server=whsql-v11.prod.mesa1.secureserver.net;Database=DB_96582;uid=xxx;pwd=xxx;"

I have used the userid and password to Connect in the database manager, so they are correct.  I also updated the other legacy location:

<add key="SiteSqlServer" value="Server=whsql-v11.prod.mesa1.secureserver.net;Database=DB_96582;uid=xxx;pwd=xxx;"/>

Any suggestions?  This seems so simple...

 
New Post
11/1/2006 3:02 PM
 
I'm having the same problem.
 
New Post
11/1/2006 3:29 PM
 
Well figured out my issue and it just had to do with carelessness on my part. I only have access to MySQL and not SQL. I guess my question is is there a way to have access to apply your own skins with only having access to MySQL?
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Godaddy and 4.3.5 Install instructionsGodaddy and 4.3.5 Install instructions


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out