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 ...Manual Installation on GodaddyManual Installation on Godaddy
Previous
 
Next
New Post
5/7/2006 8:51 PM
 

"Setting up DNN in IIS is different from setting up DNN in a Shared Hosting environment, which is what my instructions and the other instructions in this thread are addressing."

This is exactly what I am trying to do.  We have a shared hosting account with godaddy.  I never accessed IIS at any time during the steps I took.  I followed all the instructions given for installing DNN on our shared hosting account, and this is what came up. The only reason I asked if I should have done something in IIS was because of what the error message said. Oh well, the value application works most of the time.  I have wasted way too much of my time on this already.  Maybe I will try again sometime this summer.

Thanks again for all your help,
Michelle

 
New Post
5/8/2006 7:15 PM
 

This is it!  I cannot suffer anymore.  I have installed DNN 4.0.3 on a GoDaddy Windows Deluxe account at least 30 times.  I read everything I can get my hands on and I still can't get it to work.  I have gotten to the point where I finally get a clean install then the portal reports an error on every module on the page including the Login module.  After many of these, I am now getting an "ERROR: Could not connect to database specified in connectionString for SqlDataProviderSystem.Data.SqlClient.SqlException: Invalid object name 'dbo.Lists'."  However, I see it still creates about 15 stored procedures.  How can that be?  No connection, how is it creating these stored procedures.  Almost every one of my installs have been completely clean installs.  This includes new database, new folder privileges and new DNN.  So much trouble, I've never seen anything like it.  It is easy to deploy locally, why can't I move the local version up to the GoDaddy servers and script out the database and apply it up on the SQL Servers?  Does anyone know if this is possible?

I challenge anyone to get this working on my account.  There is nothing up there right now so I don't mind giving someone a temporary userid and password.  I am that desperate.

Wayne

 
New Post
5/9/2006 10:03 AM
 

I am getting the same error message even after making the changes accordingly.   Please help.

Thanks

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>

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>

 
New Post
5/11/2006 12:28 PM
 

Woo-hoo!  I finally got dotnetnuke 4.0.3 up on GoDaddy.  I first want to thank everyone that posts all of this useful information on this forum.  Once I got a clean install, I kept getting these Unhandled Error messages for various modules.  Each time they varied.  I started looking at the EventLog in the database and each time it would list a different module.  So I would re-FTP that module and the problem would go away and sometimes a new one would emerge as I tested throughout the site.  In each case I could track down the error and re-FTP the file.  Remember that this only worked after the clean install and successful portal creation.  I can't explain why there is so many problems with my FTPed files.  I have always used WS_FTP, but I could never get it to work for GoDaddy, so I use FileZilla now.  It troubles me that the integrity of the FTP is so fragile.  If anyone can get WS_FTP to work with GoDaddy, let me know.

Thanks again,

Wayne

 
New Post
5/13/2006 12:00 AM
 

When you install the portal are you getting any error messages?  Is it actually stating the the portal was installed?  The first several times I didn't realize that the message was actually "Portal Installation Failed".  It's baried in the messages.

As for your webconfig error.  Have you modified the webconfige to <customErrors mode ="Off"/> and re-uploaded the file? (have to ask).  Also, double check your database connection string.  Quite often an inproperly configured database connection string is the culprit.  Make sure that there are no line breaks, that it is all on the same line.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Manual Installation on GodaddyManual Installation on Godaddy


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