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 ...WhatWhat's up with the installer (again)
Previous
 
Next
New Post
10/14/2006 8:54 PM
 

I installed the 4.3.5 upgrade over a 4.0.2 install, and had the problem described above - on a remote server. Fortunately I was not in production on this portal. I dropped the database, deleted the entire file system, and tried again with the 4.3.5 install package instead.

Same thing ...

Error Installing DotNetNuke

Current Assembly Version: 04.03.05

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

I can connect to the database specified using QA from my home machine. How come DNN can't?

 


pmgerholdt
 
New Post
10/14/2006 9:20 PM
 

In QA, using the credentials in the connection string in web.config, I created and dropped a table. Remotely, like, from the other side of the country. Then I built a classic asp page using the connection string credentials from the web.config file, and uploaded it to the same directory that the web.config for DNN is in, and ran the same create table command. I browsed to that page, and it loaded without error. I did sp_tables in QA and the new table showed up.

Something isn't right. I don't believe it is a connection string problem. At least, it's hard to believe that. Copied and pasted out of the old web.config that was working fine, after all.


pmgerholdt
 
New Post
10/15/2006 9:15 AM
 

pmichael

Pulled my hair out on this one as I installed dnn a million times and never had a connection string problem. What it turned out to be was that the aspnet account was not set up. the host thought he had it running on 2.0 and setup the network service account but in actuality it was running 1.1.

Added the aspnet account with right permissions and it went in fine. not without a frustrating hour of messing around with it.

 

 
New Post
10/15/2006 11:34 AM
 

Color me stupid, and sorry to waste y'alls time.

The SQL 2000/2005 connection string is commented out by default in the web.config file, and the SQLExpress connectcion string is not ... it isn't obvious in my non-color-coded text editor. Still ... stupid me.

So now that problem is fixed, and the portal still does not come up, the PortalAliasInfo problem I've seen referenced ... I'll go read.

 


pmgerholdt
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...WhatWhat's up with the installer (again)


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