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 ...Yet another install failedYet another install failed
Previous
 
Next
New Post
7/6/2006 12:04 AM
 
Jack Hoelz

www.repfiles.net
Joined: 6/21/2005
Posts: 608

I belive Geert has it right. Your DB sting needs to look like the following:

<connectionStrings>
    <!-- Connection String for SQL Server 2000/2005 -->
    <add name="SiteSqlServer" connectionString="Server=(local);Database=dbname;uid=youruserid;pwd=password;" providerName="System.Data.SqlClient" />
  </connectionStrings>
  <appSettings>
    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules -->
    <add key="SiteSqlServer" value="Server=(local);Database=dbname;uid=youruserid;pwd=password;" />

Just remove or comment out all of the stuff about SQL Express

Icthus Technologies

Building Faith on the Internet
 
New Post
7/10/2006 10:24 PM
 
zenith012

Joined: 6/25/2006
Posts: 3

Firstly - I admit I'm very rusty on many aspects - so I could be missing something really obvious and not know it.

Driving me nuts....

Fresh installs of everything.

I came to the same conclusion about removing the initial SQL SERVER EXPRESS lines (I established I could connect with sqlcmd and used SQL SERVER STUDIO EXPRESS to set everything up and connect) - but now I get a different error (whereas before I was getting the database connection error initially)

I now get a :

Server Error in '/dotnetnuke' Application.

Object reference not set to an instance of an object.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error: 

Line 73: 
Line 74:             'Determine the Upgrade status and redirect to Install.aspx
Line 75:             Select Case GetUpgradeStatus()
Line 76:                 Case Globals.UpgradeStatus.Install, Globals.UpgradeStatus.Upgrade
Line 77:                     If AutoUpgrade Then


Source File: C:\website\dotnetnuke\App_Code\Global.asax.vb    Line: 75

Any help appreciated!

Thanks,
 
New Post
7/12/2006 8:50 PM
 
Niels

Joined: 6/30/2006
Posts: 19

I got it working with SQL Express and Server 2003 (IIS 6) after 4 days of dead ends.

Followed the same procedure as described by dinodod - with the same error: could not connect ....

I installed VWDExpress 2005 - downloaded the Starter Kit and maid a local build - Started it up, ran the install and added the HTTP alias for my IIS server.

Then did a WebCopy of the database.mdf and database_log.ldf files from the VWD to the website. And then did "the magic trick" on the webserver :  I deleted (renamed) the folder found inside the hidden folder "Local Settings" :

C:\Documents and Settings\[UserName]\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS

Fired up my browser - entered the HTTP alias and Voila! one clean running DNN 4.3.2 on IIS6 using SQL Express.

- Hint was found here http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=329888&SiteID=1

 

 
 
New Post
7/14/2006 9:14 PM
 
Jason Honingford

www.portvista.com
Joined: 2/20/2006
Posts: 438
Here's my connection string:

connectionString="Server=(local);Database=mydatabasename;uid=myusername;pwd=mypassword;"
providerName="System.Data.SqlClient" />

I'm moving a website to a new server. I installed a fresh copy of SQL Express, restored the database from a sql 2000 backup. All the tables and sp's are in there. I don't know if I need to, but in 2000 you delete the user and recreate him, and give him dbo. That's what I did for 2005 Express.

Well I don't know why, but DNN gives me this error on the Install page -- it's already been installed and working on the other server. This is the error:

Error Installing DotNetNuke
Current Assembly Version: 04.00.03
ERROR: Could not connect to database specified in connectionString for SqlDataProviderSystem.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException ...
Jason Honingford - Web & Software Developer
www.PortVista.com
 
New Post
7/14/2006 10:07 PM
 
Jason Honingford

www.portvista.com
Joined: 2/20/2006
Posts: 438
I solved my own problem:

I added: Data Source=.\SQLExpress; to the connection string. My SQL Express is pretty much a default install so I hope this helps someone.

The install error was due to my permissions, ya.
Jason Honingford - Web & Software Developer
www.PortVista.com
 
 Page 2 of 3
Previous123Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Yet another install failedYet another install failed


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