Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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
4/25/2006 11:23 PM
 
George Whitwell

Joined: 4/14/2006
Posts: 4

Michael,

I've been using IE with the ftp: prefix, but now have also tried WS_FTP Home. 

The unzip gives me a Portals/_default (Install or Starter 4.0.3) only.  I renamed to Portals/default before uploading.  I had to use FrontPage to delete the (3) _default folders in Portals and subs Containers and Skins from the previous attempts. The first time I load mydomain/Install/Install.aspx?mode=install/ , I get:

An error has occurred writing to the exception log.

Upon reloading, I get the same error as previously:

Error Installing DotNetNuke

Current Assembly Version: 04.00.03

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

There is no /0 subfolder created in Portals.  As far as I can see the site duplicates the unzipped structure.  Am I missing something fundamental about this process?

George
 
New Post
4/27/2006 8:12 AM
 
Michael Winter

www.NorthernStarSolutions.com
Joined: 11/23/2003
Posts: 79
whitweg wrote

Michael,

I've been using IE with the ftp: prefix, but now have also tried WS_FTP Home. 

The unzip gives me a Portals/_default (Install or Starter 4.0.3) only.  I renamed to Portals/default before uploading.  I had to use FrontPage to delete the (3) _default folders in Portals and subs Containers and Skins from the previous attempts. The first time I load mydomain/Install/Install.aspx?mode=install/ , I get:

An error has occurred writing to the exception log.

Upon reloading, I get the same error as previously:

Error Installing DotNetNuke

Current Assembly Version: 04.00.03

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

There is no /0 subfolder created in Portals.  As far as I can see the site duplicates the unzipped structure.  Am I missing something fundamental about this process?

George

You should not be renaming any real folders.  By renaming your default folder from _default.  When you do this the install engine can no longer find it and your portal will not install properly. 

From looking at your error message there is also a problem with your database connection string.  It should look something like this

 <connectionStrings>
    <!-- Connection String for SQL Server 2000/2005 -->
    <add name="SiteSqlServer" connectionString="Server=Enter Server Urn;Database=Enter Database Name;uid=Enter UserId;pwd=Enter Password;" providerName="System.Data.SqlClient" />
  </connectionStrings>

The Urn is the path to the database.  The database Name is the full name of the database, in Go Daddy this usually starts with DB_######.  You assigned the user id and password when you created the database, enter those.

I hope that this helps.
 
New Post
4/27/2006 10:43 AM
 
George Whitwell

Joined: 4/14/2006
Posts: 4

You should not be renaming any real folders.  By renaming your default folder from _default.  When you do this the install engine can no longer find it and your portal will not install properly. 

From looking at your error message there is also a problem with your database connection string.  It should look something like this

 <connectionStrings>
    <!-- Connection String for SQL Server 2000/2005 -->
    <add name="SiteSqlServer" connectionString="Server=Enter Server Urn;Database=Enter Database Name;uid=Enter UserId;pwd=Enter Password;" providerName="System.Data.SqlClient" />
  </connectionStrings>

The Urn is the path to the database.  The database Name is the full name of the database, in Go Daddy this usually starts with DB_######.  You assigned the user id and password when you created the database, enter those.

I hope that this helps.

Believe me, renaming  _default was a desperation move that I tried after all else failed. 

I was retracing this thread again looking at the difficulties Patrick found with an errant LF when your reply arrived; that doesn't seem to be my problem.  For reference, here is the section of web.config that I edited with my connection string:

  <connectionStrings>
   <!-- Connection String for SQL Server 2005 Express
    <add
      name="SiteSqlServer"
      connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"
      providerName="System.Data.SqlClient" /> -->
   <!-- Connection String for SQL Server 2000/2005  -->
 <add
      name="SiteSqlServer"
      connectionString="Server=//whsql-v08.prod.mesa1.secureserver.net;Database=DB_#####;uid=myuid;pwd=mypwd;"
   providerName="System.Data.SqlClient" />
  </connectionStrings>
  <appSettings>
   <!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules
    <add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"/>   -->
   <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules -->
   <add key="SiteSqlServer" value="Server=//whsql-v08.prod.mesa1.secureserver.net;Database=DB_#####;uid=myuid;pwd=mypwd;"/>
   <add key="InstallTemplate" value="DotNetNuke.install.config" />
   <!--  Alternative Install Templates (included in package)
    <add key="InstallTemplate" value="Club.install.config" />
    <add key="InstallTemplate" value="Personal.install.config" />
    <add key="InstallTemplate" value="SmallBusiness.install.config" />
    -->
    <add key="AutoUpgrade" value="true" />
    <add key="InstallMemberRole" value="true" />
    <add key="ShowMissingKeys" value="false" />
    <add key="EnableWebFarmSupport" value="false" />
    <add key="EnableCachePersistence" value="false"/>
  </appSettings>

Note that the 'add key="SiteSqlServer"' bit is all one line, although wrapped in this post.  I've checked and rechecked these values; I can connect to the database through the control panel.

Thanks for your input.
 
New Post
4/27/2006 10:47 PM
 
George Whitwell

Joined: 4/14/2006
Posts: 4

Yep, me again.  I'm happy to say that my GoDaddy / manual DNN install issues are settled.  For anyone who may be confused by any of the issues that stumped me, I will review my mistakes and revelations.  First, let me thank MichaelWinter and dempseyonline for providing all the needed elements. 

As Michael noted in his post this morning, I had a problem with my connectionString.  Oddly, release.config provides the add connectionString example over 3 lines (separating name, connectionString and providerName) as I had in my previous post.  Don't be fooled; it has to be 1 continuous line with the 3 sections separated by only spaces.  Application of the folder permissions was also tricky, and I can't be sure what the minimum was there.  I removed and reapplied permissions, deleted and reinstalled the virtual folders and even set and unset root permission.  At some point, the ability to write the web.config backup to Config works and then it's off to the races.  The final items are move SiteUrls.config from Config to root, add a single quote to rem out the line "strError += Config.Save(xmlConfig)" (line 105 in my file) in file Install.aspx.vb function InstallApplication() and copy the file root/Config/Backup_2006mmddhhmm/web_.config to root/web.config.  Reload the site, the install process completes and I'm ready to customize my root level dnn website on GoDaddy. 

See you on the dotnet,
George
 
New Post
5/1/2006 10:18 PM
 
Michael Winter

www.NorthernStarSolutions.com
Joined: 11/23/2003
Posts: 79

Wonderful,

Glad to hear you are up and running![EMO]bigsmile.gif[/EMO]
 
 Page 12 of 55
Previous123...111213...55Next 
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