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 ...Do Look: DNN 4.3.6 wonDo Look: DNN 4.3.6 won't work natively with current Cassini Web Server (a big problem for many!)
Previous
 
Next
New Post
11/18/2006 10:06 PM
 
I had previously used Cassini Web Server (ASP 2.0) with an older version of DNN 4.0.2 -- I did this successfully on several XP Home machines back around May, 2006.

Cassini Web Server is an ASP 2.0-deployed web server for those of us who use XP Home, and thus do not have the IIS offered by an XP Pro installation.

Now several months later, I wanted to do the same this week (on a very clean XP machine) with DNN 4.3.6 and the latest Cassini Web Server which is a version 2.0.6 .

During this installation of DNN 4.3.6 via Cassini now this week, I kept having a repeatable error, at the very end of the process *AFTER* DNN would install. It was the most frustrating thing, and I could not figure it out. Basically the problem is that Cassini cannot access DNN 4.3.6 even after a successful installation of DNN. I have described this repeatable error in more detail here: ( htt p:/ /tinyurl .c om / t4u45 )

But now I have some clues...

(By the way, this was with SQL Server 2005 Express and its management console, which is SQL Server Management Studio.)

After several attempts to deploy DNN 4.3.6 via Cassini, I decided to go back to the May, 2006, version of DotNetNuke, which was version 4.0.2 .

Today I used the current version of Cassini Web Server (v2.0.6) to deploy and use the older DotNetNuke v4.0.2 and .. it worked, just like it used to. So now I know the problem is with DNN 4.3.6 in as far as trying to make it a native DNN installation via Cassini.

I would greatly appreciate insight on how the error can be got around, or, what changes in DNN 4.3.6 might be causing the problem. I am happy to assist in trial-and-errors using my local machine.

Thanks,
Travis
 
New Post
11/18/2006 10:29 PM
 
check this out.
 
New Post
11/18/2006 11:15 PM
 
Thanks, ecktwo.

I wouldn't have known to look for custom port problems, but yep, that is exactly the problem here.

So ... now where can I download the installation folder for 4.3.5 ? I will need this slightly older version because 4.3.6 isn't working on these custom ports, and the work I need to do this weekend is all on my local installation.


EDIT: I now have 4.3.5 deployed locally, thanks.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Do Look: DNN 4.3.6 wonDo Look: DNN 4.3.6 won't work natively with current Cassini Web Server (a big problem for many!)


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