Last post Dec 30, 2005 09:14 AM by windmi
Dec 28, 2005 10:09 AM|windmi|LINK
Call me a newbie and a procrastinator.
As usual I don't work well untill deadlines approach.
I have been experimenting with DNN 3.0 the past year and found it to be a good platform for my College class reunion page. Presently I have Dell server w/MS SBS 2003 standard ed. using MSDE as Db. Original install was OK with Db working. I wanted to
start tweeking the site with added modules such as articles forums etc and hit some major snags. Modules could not be uploaded.
Word came from DNN forum that I needed to upgrade to DNN 3.1 ver or higher. Tryied to do this and ran into big road blocks. (see previous forum posts by windmi) Upgrade did not work and basic page set up lost.
I have DNN book by WROX Publishing and all instructions seem very simple.
What platforms should I have to better serve DNN and reduce errors for install and upgrading DNN and subsequent modules etc. I am willing to go with MS SBS 2003 upgrade to Premium to have MY SQL 2000 db server available. Also any sugestions on server set
up such as memory, hard drive etc. Presently server is bare bones: Dell Power edge 400SC, P4 2.8GHz,256 Ram, 40G HD using DSL.
Time is running short for me as usual. This is not anyone elses problem but mine. Your help is appreciated. Thanks.
Should this also be placed on DNN Forum.
Dec 28, 2005 11:40 AM|IcthusTech|LINK
Dec 28, 2005 12:20 PM|windmi|LINK
Does that include MS SBS 2003 stardard edition without
SQL Server 2000?
I'm looking for ease in the future for upgrading and adding future modules.
Dec 28, 2005 02:51 PM|windmi|LINK
I assume you mean the same for Windows Small Business Server withour SQL Server 2000?
Dec 28, 2005 04:37 PM|xddg|LINK
I've posted a few things about the hosting environment and have a few thoughts on the matter, since my website is DNN 2 and I'm a procrastinator when it comes to upgrading - so much so that I decided to wait until there was alot of users on one platform
and suss out the problems I thought I could foresee in the future. (Because I'm not a developer, I rely very much on the upgradability functionality)
Firstly - module upgradability - well, you're at the mercy of the developer for that - there is no single way to ensure and ever upgradable build unless you have only standard modules in your site. That's the cold hard facts of it all since DNN has that
as part of their roadmap and you'll see that the DotNetNuke website itself is upgraded each time prior to a release. Does it mean you won't have any headaches, unfortunately not, but they will be minimised alot more. And no matter what you do, backup, backup,
backup is your only security for managing upgrades that go awol.
Secondly - While the finger can be pointed at the DotNetNuke builds - I think that the aspnet 2 framework itself also requires more ram and a server running sql and web requires more ram regardless and any site that is going to have activity and lots of
visitors, logs being updated, well, you're going to have to beef it up with some ram. You've heard the saying - feed the man meat - well, Feed the server Ram.. since SQL is also hungry. Fortunately we have an environment now where ram is so cheap, putting
in a few more slots of ram doesn't break the bank and for non critical servers, you don't need to invest in the expensive server ram. (I do because I don't have quick access to my server to replace it should it have problems) If you''re not running SQL on
the server, then that should lighten the load up considerably.
Next - Getting it into perspective - You have a site you're putting together for a reunion page, not a college website with thousands and thousands of hits per day - so, the necessity to make it really well tweaked is not as critical and you probably have
a little more breathing space than others who need as close to complete reliability as possible.
But what version of DNN is right? To me, I would think that the most reliable build to date of DNN has been - DNN 2.1.2 & DNN 3.1.1 - great builds, lots of usage, most success with modules overall. DNN 4 is not, in my opinion a commercial release build
at the moment with issues around aspnet2 framework, fine tuning the DNN4 build itself and Medium/Full trust issues that are being looked at.
I had a talk with Chris Paterra (for my own site) and we sort of both concluded that upgrading to 3.2.2 was a good idea, based how dnn is performing. I think there have been a few modules affected by the upgrades.
If you want to know what modules to run and have upgradablity - look at the developer's history - that's all you've got to go on - since no one can predict the future. Contact them and ask their committment for the future if it's important to you and critical
for your sites.
To be honest, for me, I don't upgrade my sites once their released. There would have to be a really really excepctionally fantastic reason for me to hit that upgrade button, just because a release came out. I have very happy clients on DNN2 and DNN3.. and
they are all extremely happy and most have the standard install and perhaps one or two of my favourites / must haves on the install.
Icthus Tech is right - 256 mb of ram simply isn't enough. The other specs sound fine, but running an app like small business server and such, along with sql - you're going to want to have more ram to run those applications in itself.. does that mean you're
running exchange server on there too?
I have a laptop which is old *sigh* I really don't need one at this stage, and my grandkids won't even turn it on to play a game - citing that it's not worth it... I think they've been spoilt having granny's lan to play on so when there's not spare computer,
not even the laptop can entice them.. cos she's just too slow!
It seems to me, like on the side of the box with instructions, they give you the bare bare minimum to use - and I thought that SBS was about 512 mb of ram.
Grab a couple of sticks of ram, switch it on and see what the response is.. I think lots of people here would also like to know.
That's my thoughts on the matter - since I'm in upgrade mode myself at the moment and I hope it helps you make a few decisions.
Dec 28, 2005 04:38 PMfirstname.lastname@example.org|LINK
Hardware doesn't matter to DNN, and neither does the OS as long as it's Windows and SQL Server (MSDE/SQL2005 are okay). The DSL line is restrictive, but a class reunion page is not normally a high traffic site.
My first suggestion is to find a decent host that supports DNN. My second suggestion is to fix the problems you're having with upgrading, not consider new hardware or operating systems with an eye to making those upgrades work. They aren't the problem
and won't help you with upgrades.
My third suggestion is to stop worrying about having to upgrade. You'll have to upgrade everything eventually. Worry about your site, the content and getting it running. The reunion will be over before an upgrade is absolutely required.
Kep in mind, an awful lot of sites still run on DNN 2.x...
Dec 28, 2005 07:37 PM|windmi|LINK
Thanks Nina for your time and great advice on this matter. Jeff, who replied after you calmed my fears also. The site, up and running is most important at the present time.
I had no problem seting up ver. 3.0.13 using MSDE Db created using asp.net web matrix. Upgrading to ver. 3.2.1 or 3.2.2 did not work.
I noticed web config. was not included in either source.zip or install.zip downloads. Is this the cause of my problems? Where and what download is complete for me to get a clean upload for ver. 3.1. or greater? I was told I need this version to run the
DNN forums and maybe an Article module.
I will stay with present server op system MS SBS 2003 standard ver. and increase ram to 1G or max this week.
I hope we can get this going. I found out a simple site for class (this one is college) reunions makes organizing the event easy with the class communicating prior to the weekend a great asset.
Dec 28, 2005 09:58 PMemail@example.com|LINK
web.config is no longer a file in any of the newer distributions. You'll find it as release.config. Rename it to web.config, then edit that. If upgrading, pay attention to the documentation and make sure you copy the machine keys between web.config files.
This is in the docs, though poorly worded.
Dec 29, 2005 02:50 PM|windmi|LINK
The site kp81.com has been updated to 3.2.2 however I can't log in as host or admin. Any thoughts. I'm going through documentation to see if something has changed in newer version.
Also I'm off for memory
Dec 30, 2005 12:21 AMfirstname.lastname@example.org|LINK
When you updated, did you pay attention to the docs and backup your web.config and change the machine keys? If not, the encryption for the passwords uses a different key and you won't get logged in until you restore a backup of the web.config and upgrade
Dec 30, 2005 09:14 AM|windmi|LINK
Went with a new clean install of 3.2.2. All is well. Thanks for the help!