Last post Dec 17, 2005 12:03 AM by cmatiuk01
Dec 14, 2005 03:43 PM|Bgard68|LINK
I am trying to install DotNetNuke 4.0.1.
Cannot find DotNetnuke_template.mdf
Solution: I found DotNetnuke_template.mdf from a dnn webstie and copied it to the correct folder.
DotNetNuke Upgrade Error
The Assembly Version ([ASSEMBLY VERSION]) does not match the database version ([DatabaseVersion]).
Im not trying to install the starter kit! I downloaded the install version and this is the first time installing DotNetNuke. Can someone please help?
Thanks in advance
Dec 15, 2005 07:51 PM|cmatiuk01|LINK
For what it's worth, I ran into the same exact problem the same day as you did. I too am new to DNN and have installed the .NET Framework 2.0, SQLServer 2005 Express Edition, and the Virtual Web Developer 2005 Express Edition to create a Web site with tremendous
dynamic and interactive capabilities but with a minimal amount of monetary investment. I've seen DNN in action and am very anxious to get all these pieces hooked together and fully functioning.
I am assuming that others in the community have encountered this same missing DotNetnuke_template.mdf issue and subsequent version mismatch. Hopefully someone with more DNN experience will post a solution soon. A fallback option might be to install an
older version of DNN, but that would probably mean losing the hooks into the SQLServer and VWD Express editions (just guessing on that).
Thanks for the initial post. It is a comfort to know I'm not the only one trying to deal with this situation.
Dec 17, 2005 12:03 AM|cmatiuk01|LINK
I struggled for two days trying to tie the various software application components together to make DNN install and function properly. Some of that time was due to my steep learning curve and dealing with documentation that assumed
more technical expertise than I could muster without asking a lot of Google questions and reading a whole bunch of entries on this forum. I snatched snippets of useful information here and there and made some educated guesses. What follows is what I've figured
out as the step-by-step process that got me to a clean install. Please remember: if for any reason your insatllation process bombs out, it is best to blow away all directories created during the aborted process and re-start with a clean slate.
First, gather all the necessary software components to start the process. I chose these [roducts because they were the right price (free) and would give me at least a platform on which to start my DNN evaluation. More robust
(and more pricey) development tools may be an option if my DNN evaluation process is fruitful - - and if my boss is generous.
Microsoft .NET Framework
Microsoft Visual Web Developer 2005
Version 8.0.50727.42 (RTM.050727-4200)
Microsoft SQL 2005 Server Express Edition
If you're starting as a brand new DNN user, make sure you have IIS installed. If not, go to
Control Panel>>Add or Remove Programs>>Add/Remove Window Components and add Internet Information Services (IIS). You may need your Windows CD depending on whether you kept the installation files after originally installing the OS.
Although this may sound obvious, make sure the local drive partition to which you're installing DNN is NTFS and that the "Use simple file sharing" check box is unchecked (Windows Explorer>>Tools>>Folder Options>>View
- at the bottom of the list). You'll need to to set permissions later in the installation process.
Install (or upgrade to) .NET 2.0).
Install SQLServer Express.
Install Virtual Web Developer (VWD).
Follow steps in documentation starting at page 28 in DocNetNuke Installation Guide - Installation of DNN 4.x:
(1) Use the starter kit (DotNetNuke_4.0.1_StarterKit.vsi) - see pages 28-30.
(2) Create a DNN site in VWD - see pages 31-32. I created the DNN site in the C:\DotNetNuke directory. You can put it anywhere you like.
(3) You'll now have all the DNN files in whatever directory you specified in step #2. Before proceeding, copy or move the "SiteUrls.config" file from C:\DotNetNuke\Config to the root C:\DotNetNuke. Copy the
"DotNetNuke_template.mdf" file (Zip file available at http://www.altweb-design.com/dnn/DotNetNuke_template.zip)
to the C:\DotNetNuke\Providers\DataProviders\SqlDataProviders directory. Save a copy of this file in case you need to do a re-install of DNN 4.0.1.
(4) Follow the directions found on the "Welcome.html" that displays in your browser window.
(5) Create/Configure the Database section: follow the link on the Welcome page to the "SQLServerXpressConfig.html" page and do as instructed.
(6) Edit the SQL Server Connection String in web.config section: this section is misleading. The examples provided imply the following code edits:
. . . in the <connectStrings> node, <add name="DotNetNuke" . . .
. . . in the <appSettings> node, <add key="DotNetNuke" . . .
DO NOT MAKE THESE CHANGES! Leave the "SiteSqlServer" values
AS IS! Also, the line breaks (contrary to the Note in the documentation) can be left alone.
(7) Configure the Web Server section: follow the link on the Welcome page to the "WebServerConfig.html" page as do as instructed. However, in the "Application pool:" box I did not see a drop-down selection for
"ASP.NET V2.0." I've tried this routine on 3 different PCs with the same results. I selected "Low (IIS process)" for no particular reason other than intuitively I thought "Low" established a threshold I could get over (after having bombed
out too many times in the previous two days) and "IIS process" sounded logical. So much for my technical reasoning!
(8) Configure NTFS File Permissions section: even though I used the "File System" parameter and the documentation says setting file permissions for the ASP.NET user is unnecessary, I set them to "Full Control" any way figuring
it couldn't hurt. Again, perhaps a reflection of my technical reasoning, or lack thereof.
(9) Install DNN section: cross your fingers and hit Ctrl/F5.
(10) When the DNN Web page first initialized in the browser (I'm using IE) there were five (5) Error icons indicating "An error has occurred. Unhandled error loading modules." I clicked on "Home" to get past
them. I'm still looking into that issue.
(11) One final thing before I close this post: when I logged in as "admin" and tried to create a new user and assign adminstrator rights, I got an error indicating the User rights module wasn't functioning. I logged on as "host"
and put a valid email address in for the host under "host settings", saved that change, logged out and logged back in as admin and was able to change the user privileges.
That's it for tonight. Time to relax.