Macrobyte Resources Conversant Developer Central
Internet groupware development platform
installation problems




 

Topic: installation problems

Shown in forward chronological order.
Reverse chronological order | Hierarchical outline view

Messages: 10 of 10.
Pages: 1
installation problems (#277)
Posted: 5/28/2002; 7:07 PM by Ned Balzer
Modified: 5/28/2002; 7:07 PM by Ned Balzer
Response to: Top of Thread.
Edit | Reply
Hello all,

Hope I'm not in the wrong place.

I want to try out Conversant because Manila isn't doing it for us as a discussion group platform. But I haven't gotten past the installation yet. I should mention I'm a Frontier/manila newbie -- still haven't gotten my bearings

OK, I followed the instructions: downloaded conversant_1.0b2.exe (windows self-extracting archive). Wan't sure where to put it so initially put it in d:frontierconversant (so when it extracted, it extracted to d:frontierconversantconversant_1.02b). Read the readme.txt which said to open installer.ftds from inside Frontier. Got a mesasge saying that the isntaller would now open in my browser.

Here's the rub: this machine is primarily a multihomed IIS server. It has about 8 different IP addresses. One of them is reserved for Frontier, but that's not the primary address. So, the installer didn't open in the browser, instead I got a 404: http://198.93.224.59/installconversant/ - page not found. When I changed this URL to http://198.93.224.82/installconversant/, it seemed happier -- I didn't get an error, I just got a blank page.

That's where I sit. In case it's important this is a winnt 4.0 (service pack 6a) and I'm using Internet Explorer 5.0 as a browser. Oh, and Frontier is v 7.0.1

Thanks in advance for any suggestions.

-- ned balzer n.balzer@cgnet.com

Re: installation problems (#278)
Posted: 5/28/2002; 7:48 PM by Seth Dillingham
Modified: 5/28/2002; 7:48 PM by Seth Dillingham
Response to: 277
Edit | Reply

On 5/28/02, Ned Balzer said:

>Hope I'm not in the wrong place.

You certainly are.

>I want to try out Conversant because Manila isn't doing it for us as a
>discussion group platform.  But I haven't gotten past the installation
>yet.  I should mention I'm a Frontier/manila newbie -- still haven't
>gotten my bearings

How long have you been using Frontier?

>OK, I followed the instructions: downloaded conversant_1.0b2.exe
>(windows self-extracting archive).  Wan't sure where to put it so
>initially put it in d:frontierconversant (so when it extracted, it
>extracted to d:frontierconversantconversant_1.02b).

That's a good start. We should tell you (on the download page) that it doesn't matter where you put it when you download it.

>Read the readme.txt which said to open installer.ftds from inside
>Frontier.  Got a mesasge saying that the isntaller would now open in my
>browser.

Good, everything's working as it should.

>Here's the rub: this machine is primarily a multihomed IIS server.  It
>has about 8 different IP addresses.  One of them is reserved for
>Frontier, but that's not the primary address.  So, the installer didn't
>open in the browser, instead I got a 404:
>http://198.93.224.59/installconversant/ - page not found. When I
>changed this URL to http://198.93.224.82/installconversant/, it seemed
>happier -- I didn't get an error, I just got a blank page.

Darn. I've been waiting for someone to run into a problem with how the installer gets started, but I certainly didn't want it to be a relatively new user (for your sake, not mine).

Some questions:

Is Frontier listening on the default port (80)?

How do you have Frontier set up to listen to just the one ip address? I think there may be two ways to do that, and it'll be easier to help if we know how you're set up.

Just to confirm: you have managed to serve something from Frontier (including Manila) before this, right? (I ask this because I want to make sure that you know the web server is working for other things.)

>That's where I sit.  In case it's important this is a winnt 4.0
>(service pack 6a) and I'm using Internet Explorer 5.0 as a browser. Oh,
>and Frontier is v 7.0.1

Ah, I think we have found the problem.

The installer requires Frontier 8 or Radio 8.

If your Frontier license is out of date so you can't upgrade to Frontier 8, then I recommend downloading a copy of Radio Userland, which is free for 30 days (which will hopefully be enough time for you to evaluate Conversant).

The truth is that the installer probably shouldn't require Radio 8 or Frontier 8, as 99.9% of Conversant is compatible with Frontier 7. We may have to rectify that.

If you have any more questions, be sure to write again.

Seth

this is the right place (#279)
Posted: 5/28/2002; 7:55 PM by Seth Dillingham
Modified: 5/28/2002; 7:55 PM by Seth Dillingham
Response to: 278
Edit | Reply

On 5/28/02, Seth Dillingham said:


>>Hope I'm not in the wrong place.
>
>You certainly are.

I mean to say that you are certainly in the RIGHT place.

That was confusing, and sounded rude, which wasn't my intention at all.

Sorry,

Seth

Re: installation problems (#280)
Posted: 5/28/2002; 8:04 PM by Ned Balzer
Modified: 5/28/2002; 8:04 PM by Ned Balzer
Response to: 278
Edit | Reply
Hi Seth,

Muchas Gracias!

Well, I'll see tomorrow if I can talk the powers that be into upgrading Frontier.

Yes, Frontier is listening on default port 80, on only IP 198.93.224.82; IIS listens on all the other IPs (but *not* on "all unassigned").

And yes, we are successfully serving a number of manila sites from this server.

As for how I got Frontier to listen only on the single IP, I followed the advice at http://q.queso.com/stories/storyReader$213, to whit: -------------- snip ---------------------- The Frontier configuration side of things

... Once installed and updated, you need to configure Frontier to only use the single intended IP address:

Open up the user.inetd.config.http table. Add a new object named ip, a string, and set its value to the IP address that you would like Frontier to use. Quit and restart Frontier. ------------- pins -----------------------

Does this help (or make a difference)? And is there a newbies forum I should be asking these questions in?

Thanks.

-- Ned

RE: this is the right place (#281)
Posted: 5/28/2002; 8:05 PM by Ned Balzer
Modified: 5/28/2002; 8:05 PM by Ned Balzer
Response to: 279
Edit | Reply
no offense taken.

-- ned

RE: installation problems (#282)
Posted: 5/28/2002; 8:31 PM by Seth Dillingham
Modified: 5/28/2002; 8:31 PM by Seth Dillingham
Response to: 280
Edit | Reply

On 5/28/02, Ned Balzer said:

>Well, I'll see tomorrow if I can talk the powers that be into upgrading Frontier.

OK, good.

>Yes, Frontier is listening on default port 80, on only IP
>198.93.224.82; IIS listens on all the other IPs (but *not* on "all
>unassigned").
>
>And yes, we are successfully serving a number of manila sites from this
>server.

That's good info. I thought the installer was watching for the ip entry in user.inetd.config.http, but apparently it ws forgotten.

>As for how I got Frontier to listen only on the single IP, I followed
>the advice at http://q.queso.com/stories/storyReader$213, to whit:
>-------------- snip ----------------------
>The Frontier configuration side of things
>
>... Once installed and updated, you need to configure Frontier to only
>use the single intended IP address:
>
>
>Open up the user.inetd.config.http table. 
>Add a new object named ip, a string, and set its value to the IP
>address that you would like Frontier to use. 
>Quit and restart Frontier. 
>------------- pins -----------------------

OK, good. I was just checking... you said that you were new to this, so I wanted to make sure you'd done everying correctly. Sounds like you're not *completely* new. :-)

>Does this help (or make a difference)?  And is there a newbies forum I should be asking these questions in?

No, this is the right place for questions like this.

Seth

RE: installation problems (#296)
Posted: 5/31/2002; 6:19 PM by Ned Balzer
Modified: 5/31/2002; 6:19 PM by Ned Balzer
Response to: 282
Edit | Reply
Hi Seth (and everybody),

I've got other projects so unfortunately only can work on this in fits and starts. Today I finally had time to try some of your suggestions out, so I upgraded the Frontier server to v 8.0.5, and also updated all the roots I could think of (frontier,mainResponder, manila, prefs, TheXMLroot). I tried to update Installconversant.root too, but got an error: 'Can't update the root because "The server, madrid.userland.com, returned error code 4: Can't send you an update because the sysop hasn't registered a database named "InstallConversant.root".."

Probably because Conversant isn't distributed by Userland! Maybe also because conversant insn't installed yet.

Anyway, I then tried to run the installer.ftds script again and got exactly the same results: - got the message inside frontier that the installer would open in my browser - a browser window opened at address http://198.93.224.59/installconversant/, with a 404 - I edited the URL to read http://198.93.224.82/installconversant/ - I got a blank browser screen

Any idea what I should try next?

Thanks!

-- Ned

RE: installation problems (#297)
Posted: 5/31/2002; 8:24 PM by Seth Dillingham
Modified: 5/31/2002; 8:24 PM by Seth Dillingham
Response to: 296
Edit | Reply

On 5/31/02, Ned Balzer said:

>I've got other projects so unfortunately only can work on this in fits
>and starts.  Today I finally had time to try some of your suggestions
>out, so I upgraded the Frontier server to v 8.0.5, and also updated all
>the roots I could think of (frontier,mainResponder, manila, prefs,
>TheXMLroot).

For our purposes, the only one that mattered was Frontier.root.

>I tried to update Installconversant.root too, but got an error: 'Can't
>update the root because "The server, madrid.userland.com, returned error
>code 4: Can't send you an update because the sysop hasn't registered a
>database named "InstallConversant.root".."
>
>Probably because Conversant isn't distributed by Userland! Maybe also
>because conversant insn't installed yet.

Actually, there are two reasons you saw that error message:

1. Your copy of Frontier hasn't been told who to contact for an update to the installer, so it tried to contact userland (that's the default). Userland doesn't have an update to the installer.

2. We don't provide automatic updates for the installer anyway, so even if Frontier had requested the update from one of Macrobyte's servers, there still would have been an error message like that one.

>Anyway, I then tried to run the installer.ftds script again and got
>exactly the same results:
>
>- got the message inside frontier that the installer would open in my
>browser
>
>- a browser window opened at address
>http://198.93.224.59/installconversant/, with a 404
>
>- I edited the URL to read http://198.93.224.82/installconversant/
>
>- I got a blank browser screen
>
>Any idea what I should try next?

It looks to me like you have another "web responder" grabbing the request that should have gone to the installer.

Although the page you listed (the second one which should have worked) appears blank, if you view the source you'll see that there's a very minimal web page containing "<%"this is a test"%>".

Here's a guess: you have a "tool" running whose name starts a letter lower than "i" (so it would be hit before the installer's), and which includes an incomplete web responder whose condition is something like "return true" (or a script which always returns true).

Can you give us a list of what is in your user.webser.responders table?

I'd like to help you work this out, I'll send you my telephone number in a separate (private) email. Hopefully what we learn here will help us create a better installer.

Seth

RE: installation problems (#298)
Posted: 6/4/2002; 2:47 PM by Balzer, Ned
Modified: 6/4/2002; 2:47 PM by Balzer, Ned
Response to: 297
Edit | Reply
I have succeeded in installing conversant. Thanks to Seth, the trick turned
out to be modifying installConversant.installConversantData.prefs.accessFrom
to be the same IP address as the one Frontier is listening on.

Thanks again.

-- Ned

-----Original Message-----
From: Seth Dillingham [mailto:seth@macrobyte.net]
Sent: Friday, May 31, 2002 5:24 PM
To: macrobyte.developers@lists.macrobyte.net
Subject: RE: [Conv] installation problems [Msg#297]


Msg URL: http://conversant.macrobyte.net/297
--------------------------------------------------

On 5/31/02, Ned Balzer said:

>I've got other projects so unfortunately only can work on this in fits
>and starts. Today I finally had time to try some of your suggestions
>out, so I upgraded the Frontier server to v 8.0.5, and also updated all
>the roots I could think of (frontier,mainResponder, manila, prefs,
>TheXMLroot).

For our purposes, the only one that mattered was Frontier.root.

>I tried to update Installconversant.root too, but got an error: 'Can't
>update the root because "The server, madrid.userland.com, returned error
>code 4: Can't send you an update because the sysop hasn't registered a
>database named "InstallConversant.root".."
>
>Probably because Conversant isn't distributed by Userland! Maybe also
>because conversant insn't installed yet.

Actually, there are two reasons you saw that error message:

1. Your copy of Frontier hasn't been told who to contact for an update to
the installer, so it tried to contact userland (that's the default).
Userland doesn't have an update to the installer.

2. We don't provide automatic updates for the installer anyway, so even
if Frontier had requested the update from one of Macrobyte's servers,
there still would have been an error message like that one.

>Anyway, I then tried to run the installer.ftds script again and got
>exactly the same results:
>
>- got the message inside frontier that the installer would open in my
>browser
>
>- a browser window opened at address
>http://198.93.224.59/installconversant/, with a 404
>
>- I edited the URL to read http://198.93.224.82/installconversant/
>
>- I got a blank browser screen
>
>Any idea what I should try next?

It looks to me like you have another "web responder" grabbing the request
that should have gone to the installer.

Although the page you listed (the second one which should have worked)
appears blank, if you view the source you'll see that there's a very
minimal web page containing "<%"this is a test"%>".

Here's a guess: you have a "tool" running whose name starts a letter
lower than "i" (so it would be hit before the installer's), and which
includes an incomplete web responder whose condition is something like
"return true" (or a script which always returns true).

Can you give us a list of what is in your user.webser.responders table?

I'd like to help you work this out, I'll send you my telephone number in
a separate (private) email. Hopefully what we learn here will help us
create a better installer.

Seth

--------------------------------------------------
To Unsubscribe from this list visit:
http://conversant.macrobyte.net/members/settings/preferences$conversation=de
velopers&plugin=Email%20Interface

Please be thoughtful when quoting messages. Do not
quote more than is necessary (just what you are
responding to).

Re: installation problems (#426)
Posted: 10/8/2004; 8:01 PM by felipe santana
Modified: 10/8/2004; 8:01 PM by felipe santana
Response to: 278
Edit | Reply
Messages: 10.
Pages: 1


 
© 2002 Macrobyte Resources. All rights reserved.