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 ...Installing Database String ErrorInstalling Database String Error
Previous
 
Next
New Post
7/5/2007 6:30 AM
 

mike: Well that almost worked. I set up a "source" install of DNN 4.5.1 and manually configured the connection string. I did exactly as you said, checked if the connection worked during the install (it did) and then went back and set it to auto. It failed with this error:

Installing DotNetNuke

Version: 04.05.01

Installation Status Report

00:00:00.015 - Installing Version: 4.4.0
00:00:00.031 -   Executing Script: DotNetNuke.SetUp.SqlDataProvider Success
00:00:00.078 -   Executing Script: DotNetNuke.Schema.SqlDataProvider Error! (see DotNetNuke.Schema.log for more information)
00:00:10.921 -   Executing Script: DotNetNuke.Data.SqlDataProvider Success
00:00:16.765 - Installing MemberRole Provider:
00:00:16.765 -   Executing Script: InstallCommon.sql
00:00:17.218 -   Executing Script: InstallMembership.sql
00:00:18.312 -   Executing Script: InstallProfile.sql
00:00:18.640 -   Executing Script: InstallRoles.sql
00:00:19.140 - Upgrading to Version: 4.5.1
00:00:19.296 -   Executing Script: 04.04.01.SqlDataProvider Error! (see 04.04.01.log for more information)
00:00:19.421 -   Executing Script: 04.05.00.SqlDataProvider Error! (see 04.05.00.log for more information)
00:00:20.875 -   Executing Script: 04.05.01.SqlDataProvider Error! (see 04.05.01.log for more information)
00:00:21.015 - Performing General Upgrades


 

Server Error in '/Application.

The stored procedure 'dbo.GetTabs' doesn't exist.

The log files contain these errors, among others (I don't really feel like scanning through a 50kb error log)

System.Data.SqlClient.SqlException: Must declare the variable '@ModuleDefID'.
System.Data.SqlClient.SqlException: Must declare the variable
'@POrtalID'.
System.Data.SqlClient.SqlException: Must declare the variable '@Fields'.
System.Data.SqlClient.SqlException: Must declare the variable '@UserName'.

Any ideas? Googling around for those errors doesn't turn up very much. I don't really understand what's happening, I'm pretty much a DNN newbie so all tips are appreciated :)

 
New Post
7/6/2007 12:30 AM
 

i just completed the same installation on my local machine and it ran smoothly. The only things I can come up with now are that perhaps you didn't start with a fresh set of installation files or fresh database.

Usually when you get an error where the installation is looking for things in the database it means that you had a previous failed installation and you need to start it over again with a new set of installation files.

Another thing, I usually run the install without VS2005 initially. A lot of times when running under VS2005 I get the green warnings about this and that in the core modules. Once the installation is completed I open up the source files with VS2005.

Good luck,

Mike


Kist Enterprises
www.kistenterprises.com
 
New Post
7/6/2007 11:24 AM
 

A sysadmin here had an idea: I'm running the SQL 2005 native client on my development machine whilst connecting to an SQL 2000 server. Therefore, all the scripts for DNN are being executed by the 2005 client against a 2000 server. Could that be causing these issues?

 
New Post
7/7/2007 4:07 AM
 

I'm not a SQL expert by any means but I don't think that is the problem - maybe someone else participating in this forum might know for sure. I believe the SQL scripts that DNN runs are SQL version 2000/2005 independent. I did try an installation with the database configured as a SQL2000 database on my server with SQL2005 Express installed and it ran smoothly. For fun I decided to run the database configured as a SQL7 database and that did throw the DotNetNuke.Schema.SQLDataProvider error, the 04.05.00.SQLDataProvider error and portal creation errors. The error logs were available and specifically said:

"You may need to set the compatibility level of the current database to a higher value to enable this feature. See help for the stored procedure sp_dbcmptlevel."

which reminds me that I forgot to ask about whether your error logs are available from the Providers/Dataproviders/SQLDataProvider directory.

Mike


Kist Enterprises
www.kistenterprises.com
 
New Post
7/9/2007 1:04 PM
 

issijohn wrote

During the install when running under VS2005, I get this error.  The error doesn't happen, I think,  when not under VS2005.  This error is displayed and then the install process never continues.  Any clue?

Installing Database - Version 4.4.0...Upgrading Database to Version ERROR: See C:\DotNetNuke_2\Website\Providers\DataProviders\SqlDataProvider\04.04.00.log for more information...FAILURE 400 - Conversion from string "ERROR: See C:DotNetNuke_2Website" to type 'Integer' is not valid.

I had this same problem with my installation. The way i fixed it was to, 1) Delete and re-create the database. 2) In the folder: 'install/module' I noticed i forgot to upload 2 zip files 'HTML_04.05.00_Install.zip' and 'Links_03.03.07_Install.zip'. 3)Then I went back to my website and used the auto mode (legacy - i think it was called) and SUCCESS!!!!!!

I hope this helps because it caused me a damn lot of frustration.

www.zeroalpha.net

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installing Database String ErrorInstalling Database String Error


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