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 ...Regarding Error om DNN 4.0.2 and InstallRegarding Error om DNN 4.0.2 and Install
Previous
 
Next
New Post
3/13/2006 3:03 PM
 
Asbjørn-Martin Antonsen

Joined: 3/8/2006
Posts: 7

It's working !:)

This is actually a followup my posts on:
http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/107/threadid/12499/scope/posts/Default.aspx
But since it dosn't cover all in that thread I'll post what I have found here:

Have collected bits and pices from the dotnetnuke web and come up with something thats worked for me. I am sure there stuff that you don't need to do, but I am not going to try to install another version for a while... I hope this description is complete...

This worked today on the source solution:


Files / Filesystem
1. Create your solution folder
2. Turn of simple file sharing tools folder options view
2. Add user _LOCAL_ ASPNET with  modify (and  other thats already checked) {machine}/ASPNET
3. Extracted source to the folder
4. Copied Website\Install\DotNetNuke.install.config to Website root folder
5. Copied website\config\siteurls to website root folder
6. Rename release.config to web.config
7. Changed the web.config to use correct connection string, user, password and database (see database)
8. Optional:  .Turn on debug:  <compilation debug="true" strict="false"> in web.config


Database
9. Create database user and set user default database
10. Create database and add user to it,make user dbo. to database


IIS
11. Create virtual directory choose correct framework version (under ASP) and make sure documents include default.aspx

 

Install:
- Tried to access the web ... It just kept hanging
- Closed the Browser and tried again
- Got an erorr when the app wanted to do response.redirect to: http://localhost/{MYSITE}/Install/Install.aspx?mode=install
- Access that once - Nothing happened
- Closed Browser and Tried once more to access it and the installation started.

And it was running fine!


Errors I have encountered:

Database error (DotNetNuke Upgrade Error)
For me this it looks like the error comes when some objects have been installed in database but not a complete install--> Try setting the database up again (empty).

-Could not access siteurl.*** among others
-DotNetNuke Configuration Error  - Access
Have you granted the correct file permissions and copied all files ?
Remember to use the LOCAL ASPNET {machine}/ASPNET nothing else :)

Error: Response.End cannot be executed when ApplicationInstance is not available.
Try accessing the Install URL mentioned under Install.

And even more... But all are more or less due to:
   - Skipping something in what I described in the beging
   - You have ended up with an Install thats not completly what/where it should be and one error leads to the next. You migth get it to run in the end but...Are u sure it's ok ?

My advice is to start from the top if you get on the wrong foot and one error comes after another.

Hope I didn't forget anything
 
 
New Post
4/2/2006 5:01 AM
 
Efren Ramirez Farjat


el-efren.net
Joined: 12/2/2005
Posts: 5

I follow your steps, several times like many other step by setp around the forums and no one has include what to do with:

Could not find file 'C:\Inetpub\dnn46\Website\Providers\DataProviders\SqlDataProvider\DotNetNuke_template.mdf'.

your comments?

Efrén
 
New Post
1/24/2007 1:59 PM
 
HT

Joined: 10/24/2006
Posts: 2

amantons,
Thanks for your detailed post. 

I tried your suggestions above, roughly, but basically used this as my own checklist to ensure I had the right permissions and access to my DNN4.3.7 site as well as my new SQL2000 database.  Hopefully, this will help others save some time.  (In my case, I was trying to get DNN4.3.7 site working against SQL2000 database (instead of SQL2005) on my local PC to mirror the production's SQL2000 environment.)

  • Go and download and extract the Install version of DNN that you need from dotnetnuke.com to a separate folder on your PC
  • In Windows Explorer, copy your extracted zip files from "\Install\Module\" to "<root of your DNN site>\Install\Module\"
  • Site Permission/Access
    • Turn OFF simple file sharing (tools, folder options, view)
    • Confirm that local ASPNET account is added to the root of my DNN site with Read and Write access.  If not, add {machinename}/ASPNET account and apply (or re-apply) Read and Write access to the root of my DNN site.
    • Make sure my own domain user account was also added to the root of my DNN site with Read and Write access.
  • Database Permissions/Access
    • Edit my web.config and make sure it has the right connection string values (i.e. in my case I had created a SQL2000 instance which needed to be referred to as "<machinename>\SQL2000")
    • Dropped my DNN database, created a new DNN database, created a new user (or hook an existing user to the new DNN database) with dbo access to the new DNN database, AND make sure that the user's default database was the new DNN database.
  • First close down all instances of Visual Studio 2005 (in my case this made a big difference b/c my DNN site's files were potentially locked when I had Visual Studio 2005 site open b/c it's hooked to VSS, which created errors), and then open your browser and navigate to your DNN site and just let everything run to completion (you might also need to navigate to the http://localhost/(YourDNNSite)/Install/ link if navigating to http://localhost/(YourDNNSite) doesn't work).  In my case, everything installed fine.  And once it all installs fine, if you navigate in Windows Explorer to "<root of your DNN site>\Install\Module\" directory, all the install (i.e. .zip) files are removed.  If you want to try the install again or need to reinstall for any reason, you must repeat the first two steps above to recover the zip install files to your DNN site's \Install\Module\ folder.

So I found that anytime you have database related errors or if the DNN install did not install the database components correctly through its own scripts then you will get the error like: 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.

My final dilemma is trying to find a way to recover some data from production that is schema'd for SQL2000 with DNNv2.1.2 ported to SQL2000 with DNNv4.3.7.  Originally, I tried recovering a backup of the SQL2000 database for DNNv2.1.2 to SQL2000 for DNNv4.3.7 first, and then perform the DNNv4.3.7 install but that yielded the original error mentioned above.  No matter what I did, I was never able to successfully get DNNv4.3.7 working in this scenario.  So I ended up dropping the DNN4.3.7 SQL2000 database and created one from scratch, ran the DNNv4.3.7 install and all was well.  The database fields and structures are definitely off in my first approach.

Hope this helps someone out there.
 
New Post
1/24/2007 2:02 PM
 
HT

Joined: 10/24/2006
Posts: 2
amantons,
Thanks for your detailed post. 

I tried your suggestions above, roughly, but basically used this as my own checklist to ensure I had the right permissions and access to my DNN4.3.7 site as well as my new SQL2000 database.  Hopefully, this will help others save some time.  (In my case, I was trying to get DNN4.3.7 site working against SQL2000 database (instead of SQL2005) on my local PC to mirror the production's SQL2000 environment.)

  • Go and download and extract the Install version of DNN that you need from dotnetnuke.com to a separate folder on your PC
  • In Windows Explorer, copy your extracted zip files from "\Install\Module\" to "<root of your DNN site>\Install\Module\"
  • Site Permission/Access
    • Turn OFF simple file sharing (tools, folder options, view)
    • Confirm that local ASPNET account is added to the root of my DNN site with Read and Write access.  If not, add {machinename}/ASPNET account and apply (or re-apply) Read and Write access to the root of my DNN site.
    • Make sure my own domain user account was also added to the root of my DNN site with Read and Write access.
  • Database Permissions/Access
    • Edit my web.config and make sure it has the right connection string values (i.e. in my case I had created a SQL2000 instance which needed to be referred to as "<machinename>\SQL2000")
    • Dropped my DNN database, created a new DNN database, created a new user (or hook an existing user to the new DNN database) with dbo access to the new DNN database, AND make sure that the user's default database was the new DNN database.
  • First close down all instances of Visual Studio 2005 (in my case this made a big difference b/c my DNN site's files were potentially locked when I had Visual Studio 2005 site open b/c it's hooked to VSS, which created errors), and then open your browser and navigate to your DNN site and just let everything run to completion (you might also need to navigate to the http://localhost/(YourDNNSite)/Install/ link if navigating to http://localhost/(YourDNNSite) doesn't work).  In my case, everything installed fine.  And once it all installs fine, if you navigate in Windows Explorer to "<root of your DNN site>\Install\Module\" directory, all the install (i.e. .zip) files are removed.  If you want to try the install again or need to reinstall for any reason, you must repeat the first two steps above to recover the zip install files to your DNN site's \Install\Module\ folder.

So I found that anytime you have database related errors or if the DNN install did not install the database components correctly through its own scripts then you will get the error like: 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.

My final dilemma is trying to find a way to recover some data from production that is schema'd for SQL2000 with DNNv2.1.2 ported to SQL2000 with DNNv4.3.7.  Originally, I tried recovering a backup of the SQL2000 database for DNNv2.1.2 to SQL2000 for DNNv4.3.7 first, and then perform the DNNv4.3.7 install but that yielded the original error mentioned above.  No matter what I did, I was never able to successfully get DNNv4.3.7 working in this scenario.  So I ended up dropping the DNN4.3.7 SQL2000 database and created one from scratch, ran the DNNv4.3.7 install and all was well.  The database fields and structures are definitely off in my first approach.

Hope this helps someone out there.
 
 Page 1 of 1
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Regarding Error om DNN 4.0.2 and InstallRegarding Error om DNN 4.0.2 and Install


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