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 ...Proper database settings using "typical" installation? Help NeededProper database settings using "typical" installation? Help Needed
Previous
 
Next
New Post
7/29/2007 4:09 PM
 

Using shared hosting, but wilth full trust and ASP worker permissions; created an SQL 2005 db, connection strings updated in webconfig, etc.

During the installation, I selected "typical" installation, selected SQl 2005, put the database name and SQL server IP...received the following error:

Installing Database - Version 4.4.0...Upgrading Database to Version ERROR: See E:\inetpub\vhosts\mydomain.com\httpdocs\Providers\DataProviders\SqlDataProvider\04.04.00.log for more information...FAILURE 400 - Conversion from string "ERROR: See E:inetpubvhostsdealer" to type 'Integer' is not valid.

 

So I backed out of it, went for the "auto" install, all went well until the very end:

 

Domain Name www.mydomainxxx.com Does Not Exist In The Database

DotNetNuke supports multiple portals from a single database/codebase. It accomplishes this by converting the URL of the client browser Request to a valid PortalID in the Portals database table. The following steps describe the process...

 

So I botched some setting when doing the typical install.  Could you please advise me on the proper settings, given my configuration?

  • Select SQL 2005
  • Enter server IP/address
  • Enter database name
  • Run as db owner?
  • Leave object qialifier blank?
  • a few more settings that I don't recall.  ;)

Also, I was going to remove all the files and start from scrastch, but is this really needed? Could just delete the db and add a new one to ensure all the previous changes are removed?  ...just trying to avoid any conflicts and hangups for the next go around.

A sticky walking people though the install wizard with each step explained would rock.

 

 

 
New Post
7/29/2007 4:14 PM
 

One more question I just thought of.  I rarely have any problems with the auto install.  Does the auto install default to one database or the other based on the connection strings updated in the web.config? So, for example, if I have a connection string for a regular SQl 2005 db, would the auto recognize this and install accordingly?

If this is the case, what are the benefits from using a typical install?  There isn't much more to change but the host, passwords, etc...and could do this with the source before installing, if needed, right?  I only ask, as perhaps it's best for me to do auto installs in the future.  ;) ...so long as it picks up the right database and I am not going to limited in any way from doing so.

 

 

 
New Post
7/30/2007 11:59 AM
 

Terp,

I NEVER use the wizard for installation, I update the web.config to put the proper connection strings in and just trigger the install with the wizard turned off.

On a shared hosting environment, most likely your error is due to the partial install that was completed, the best thing to do if you have a partial install is to have that database dropped and re-created before you try to re-install.  I have found that the SqlDataProviders do not have very good error catching to resolve issues of that nature.


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Proper database settings using "typical" installation? Help NeededProper database settings using "typical" installation? Help Needed


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