Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
help -- Cassini Server 2.0 plus DNN 4.3.6 is 99.9% good and then ...
Options
Previous Topic Next Topic
vois2
#1 Posted : Friday, November 17, 2006 7:05:46 PM(UTC)
Groups: Member
Joined: 11/17/2006(UTC)
Posts: 3
Thanks in advance to any experts who can reply.

I have successfully used Cassini Web Server 2.0 with DotNetNuke on other machines, but I am frustrated by today's installation. This is on my main box which is truly in great shape. (Injured pride!)

Here's the deal: I am on XP Home, so I set up the combo of SQL Server 2005 Express + SQL Server Management Studio + the latest Cassini Web Server 2.0 build.

All goes as expected, beautiful DNN 4.3.6 installation, etc.

But when I click on the "Click Here To Access Your Portal" ... a problem occurs. It is repeatable and I have restored my machine and attempted this installed this combo three times with repeatable error.

The error is below ... it seems to do with the URL that Cassini is attempting to use when serving up the DNN application.

When I press "Click Here To Access Your Portal" ...
* in Firefox, the URL appears as htt p:/ /localhost : xxxx/ (where xxxx is the port assigned by the system's install of DNN)
Shortly thereafter, I get the following error from Firefox:
"The page isn't redirecting properly --
Firefox has detected that the server is redirecting the request for this
address in a way that will never complete. This problem can sometimes
be caused by disabling or refusing to accept cookies."

* in IE 6.0, it does indeed do exactly that ... the process just loops trying to load the page, and I eventually have to kill IE 6.0


One Clue (?) the URL ... isn't it supposed to be a longer URL with a specific numerical domain after the xxxx/ ???

Note: I haven't done anything to cookies ever on either browser platform.

Again, thanks in advance for all help!!
Back to top
 |  Edit by user
Ultidev Team
#2 Posted : Friday, November 17, 2006 8:50:50 PM(UTC)
Ultidev Team

Groups: Administration
Joined: 11/3/2005(UTC)
Posts: 2,253

Thanks: 28 times
Was thanked: 60 time(s) in 59 post(s)
Hi there!

Although our experience with DNN is limited, here a couple of pointers:

- When registering DNN with Cassini please be sure to uncheck the "Always keep application in memory to improve first page response time" check-box, otherwise DNN will get into invalid state. The reason for that is DNN does a lot of initialization on first call. What "Always keep application in memory..." flag does is generating brief requests to the application to keep it in memory, but since Cassini does not care for response, it abandons the connection right away. That messes up DNN.

- If you reinstall Cassini, make sure you start with a pristine DNN clean database. DNN saves its address in the database, so if subsequent installations assign different port to DNN, redirect will not work;

- Be sure to make the first request to DNN by the host name you plan to use in the future, because, again, DNN saves its address in the database. So if you point browser to http://localhost:DnnPort/ to bring DNN up for the first time, subsequent requests will be redirected to http://localhost:DnnPort/, which will prevent users from other computers from accessing DNN.

Please let us know if any of this has helped.

Best regards,
UltiDev Team.
Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
Back to top
WWW
vois2
#3 Posted : Saturday, November 18, 2006 1:49:33 PM(UTC)
Groups: Member
Joined: 11/17/2006(UTC)
Posts: 3
Ultidev Team wrote:
please be sure to uncheck the "Always keep application in memory to improve first page response time" check-box



You are correct about that, and I did do so during all installation attempts. (By the way, thanks for the response!)


Ultidev Team wrote:
If you reinstall Cassini, make sure you start with a pristine DNN clean database. DNN saves its address in the database, so if subsequent installations assign different port to DNN, redirect will not work



I discovered this along the way, so before my third install combo attempt, I did a number of things to make the database disappear. First, I uninstalled all SQL products appropriately. Then I physically removed all databases from the remnant folder the SQL leaves behind for my data. Then, I restored the machine to a previous date, to further make SQL footprints disappear to a day and state in which SQL had never touched the machine. I figured this would do the trick in fixing my problem, but it did not.


Ultidev Team wrote:
Be sure to make the first request to DNN by the host name you plan to use in the future, because, again, DNN saves its address in the database. So if you point browser to http://localhost:DnnPort/ to bring DNN up for the first time, subsequent requests will be redirected to http://localhost:DnnPort/, which will prevent users from other computers from accessing DNN.



I'm not really sure how to make the first request to DNN by anything other than the URL which Cassini serves up when I press the "Click Here To Go To Your Portal" button -- which occurs immediately after installation of DNN. Can you explain to me further what is meant? Maybe you can tell me what I should ask Cassini to serve (in the Address Bar, by typing it) instead of hitting the "Go To Your Portal" button. Thanks in advance!!
Back to top
vois2
#4 Posted : Saturday, November 18, 2006 4:48:49 PM(UTC)
Groups: Member
Joined: 11/17/2006(UTC)
Posts: 3
Well, I have just now had a clue in determining what is the problem here.

The current version of DotNetNuke is version 4.3.6 . This is the version I have been attempting to install and serve via Cassini during these last two days.
All my efforts have been met with the problems describe above, in my posts before this one.

So... I went back and picked up an old copy of DNN 4.0.2 . I knew that at one time (circa May 2006) I was using this DNN version 4.0.2 with whatever version of Cassini was available back in May 2006.

Using the current Cassini Web Server (v. 2.0.6 I believe) and I used the *old* version of DNN v 4.0.2 .
And .. it worked.

So it is safe to say that problem lay within the most recent versions of DNN, specifically 4.3.6 .

I'm going to mention this on the DNN forums, since Cassini is hugely popular for those of us who enjoy DNN alongside Cassini on our XP Home machines.
EDIT: The thread at DotNetNuke can be followed here: ( http://tinyurl.com/va3vt ) -- seems to be confirmed bug.

Cassini Experts, I am happy to assist in fixing this problem for the benefit of all. I already have a few hunches and clues, if you wish to hear them. (file attachments would be required, I can be contacted at memorex_1 @ graffiti . n e t )

And thanks again !!!
Back to top
 |  Edit by user
Ultidev Team
#5 Posted : Sunday, November 19, 2006 5:53:59 AM(UTC)
Ultidev Team

Groups: Administration
Joined: 11/3/2005(UTC)
Posts: 2,253

Thanks: 28 times
Was thanked: 60 time(s) in 59 post(s)
Thank you for finding this out!

Best regards,
UltiDev Team.
Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
Back to top
WWW
Rss Feed  Atom Feed
Users browsing this topic
Guest (7)
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You can vote in polls in this forum.

Powered by YAF 1.9.5.5 | YAF © 2003-2011, Yet Another Forum.NET