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 ...Error om DNN 4.0.2 Installation (step by step)Error om DNN 4.0.2 Installation (step by step)
Previous
 
Next
New Post
1/18/2006 12:36 AM
 
Tony Trinh

Joined: 5/22/2005
Posts: 7

I would drop the database and try again...I didn't use the ASPNET account...I just created another user and set the user's default database to the dotnetnuke database.  Also remember to update the account with what user you created.  So here are my steps:

  1. drop dotnetnuke database
  2. delete any user you may have created
  3. create the blank dotnetnuke database
  4. create the user for the dotnetnuke database
  5. set the user's default database as the dotnetnuke database
  6. add the user as the dbowner, dbdatareader, dbdatawriter for the database
  7. make sure the user can log into the default database via logging out of sql manager and logging back in as the user...you should only see the dotnetnuke database you created
  8. edit the web.config strings for the database connection (remember to comment out any unnecessary lines depending on what database you are connecting to)
  9. try to open the website to see if the database populates

Good Luck! 

 
New Post
2/28/2006 9:21 AM
 
Kiril Emilov

Joined: 2/27/2006
Posts: 2
Hi,

I follow all the steps here and I always have the same problem with the upgrade error:

DotNetNuke Upgrade Error

The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )

ERROR: Could not connect to database.

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

 I search for this problem in the web and many many many people have this problem. Is there a solution? Can DNN 4.02  use Sql Server 2000? I tried over 10 solutions and nothing helps. Creating the database, re-creating it and so, user rights, also i tried over 4-5 clean isntallations and so, also I make a stupid changes to the web config and nothing... Now I must use SQL Server 2005 or another database. 10x to everyone who helps, and if somebody knows how to make DNN 4.02 to run with SQL Server 2000 will be superb to tell here. Thank you and I hope this problem will be solved soon

Kiril Chobanov
 
New Post
3/5/2006 8:38 AM
 
Wael Boghdady

Joined: 2/23/2006
Posts: 1

Hi,

I faced the same problem, but fortunately it is solved by the following:

1- in the documentation file "DotNetNuke Code Access Security" page7:

"Medium trust does not allow access to Sql Server using the sa account and a blank

password."

so, I used a "New Login", with strong password.

2- Change the connection string to by removing the "Integrated Security" and 'User Instance"

i hope this can fix your problem,

Good Luck
 
New Post
3/6/2006 3:47 AM
 
Marco van Vliet

Joined: 9/21/2004
Posts: 2

Hi,

I'm having the same problem, running SQL2000. What I find rather strange: the table 'Version' is created, even the SP's that handle version management. After that step the installation fails. I think this definitely has something to do with the way the connection is handled.

On my home machine (VS2005 installed, SQL Express installed (connectionstring used the way SQL 2000 does)) it works fine with the install package, but at the office (Win2k server, SQL2000, IIS 5.1 (i think)) I can't get it to work. Even the option 'UseDnnConfig' is removed from web.config. Maybe this option is default set to true? Maybe we should manually add this option again to web.config?

I try and try but can't figure it out yet, although I haven't tested the last suggestion about UseDnnConfig myself yet...

Anyone who could help me: Thanx in advance

JMvV

 

JMvV
 
New Post
3/6/2006 11:10 AM
 
Robert Bradford

Joined: 8/21/2003
Posts: 1

hey everyone,

I've been experiencing a similar problem today - install and get an error about not being able to connect to the database.
My connection string is correct (verified it by creating another application and connecting to the DB).  After 2 painstaking hours, I realized there seems to be some issue (probably a configuration thing on my end given my lack of familiarity with DNN) that if you have the Small Business template selected, it won't work.  I couldn't find the SmallBusiness.Install.Config file in the project, so I imagine that's where the problem lies.  But I changed the install to use DotNetNuke and it worked fine.  Hope that helps someone else.  Good luck!

<

<appSettings>

<!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules -->

<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"/>

-->

...

</appSettings>

 
 
 Page 3 of 6
Previous1234...6Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Error om DNN 4.0.2 Installation (step by step)Error om DNN 4.0.2 Installation (step by step)


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