T.R | Title | User | Personal Name | Date | Lines |
---|
3776.1 | | MR1MI1::VILCANS | | Tue Jul 09 1996 17:04 | 7 |
3776.2 | LiveWire Pro status? | UCROW::GIBSON | | Tue Dec 10 1996 11:25 | 5 |
3776.3 | "Error in LiveScript services" accessing Informix on NT/Intel | LGP30::FLEISCHER | without vision the people perish (DTN 381-0426 ZKO1-1) | Tue Feb 11 1997 20:22 | 152 |
| This looked like a reasonable place to put this:
I'm running Windows NT Workstation 4.0 (with SP2) on a
Venturis GL 6200 with 32MB main memory.
Today I installed Netscape Enterprise Server V2.01 -- and
that appears to work.
I then proceeded to install LiveWire Pro V1.01. It took me a
while to realize that if I wanted LiveWire Pro, I first had
to install the LiveWire V1.01 kit -- the LiveWire Pro
download kit is just the extra components that come in the
"Pro" version.
I was able to run the "hello world" and hangman LiveWire demo
apps with no problem. But I wanted to test out the video
database application, so I needed the database.
The only part of the "Pro" kit that installed (for now) is
the Informix OnLine Workgroup Server 7.12 kit. I installed
it several times before I actually achieved the 20MB database
that the LiveWire Pro readme suggests -- the default
installation appears to reserve half of the remaining space
(which in my case is 500MB!); even the "minimal"
installation reserved 50MB.
(I'm a novice when it comes to databases. Nothing told me
that I needed to go to the Informix "Command Center" app and
set the server "on-line" -- I eventually figured that out.)
To run the video LiveWire demo the database must be built --
there's a procedure in Netscape's LiveWire release notes to
do that. That ran OK (once I had the server and database
name straight, and the server online). This is some evidence
that the database was running OK.
Then one line in the video demo start pages needs to be
edited and the video demo compiled. I chose to use the
"build.bat" procedure:
> C:\Netscape\Server\LiveWire\samples\video>build.bat
>
> C:\Netscape\Server\LiveWire\samples\video>lwcomp -v -o video.web start.htm home.htm rentals.htm cust
> omer.htm add.htm remove.htm videos.htm rent.htm client.htm status.htm return.htm category.htm pickme
> nu.htm delete.htm pick.htm support.js url.js
> Livewire Compiler Version 14.4
> Copyright (C) Netscape Communications Corporation 1996
> All rights reserved
> Reading file start.htm
> Compiling file start.htm
> Reading file home.htm
> Compiling file home.htm
> Reading file rentals.htm
> Compiling file rentals.htm
> Reading file customer.htm
> Compiling file customer.htm
> Reading file add.htm
> Compiling file add.htm
> Reading file remove.htm
> Compiling file remove.htm
> Reading file videos.htm
> Compiling file videos.htm
> Reading file rent.htm
> Compiling file rent.htm
> Reading file client.htm
> Compiling file client.htm
> Reading file status.htm
> Compiling file status.htm
> Reading file return.htm
> Compiling file return.htm
> Reading file category.htm
> Compiling file category.htm
> Reading file pickmenu.htm
> Compiling file pickmenu.htm
> Reading file delete.htm
> Compiling file delete.htm
> Reading file pick.htm
> Compiling file pick.htm
> Reading file support.js
> Compiling file support.js
> Reading file url.js
> Compiling file url.js
> Writing .web file
OK -- so that looked good as well.
My only problem is that when I select the video app and "run"
with the LiveWire Application Manager, I get a Dr. Watson
error for httpd.exe. If I hit "debug" instead, I get the
following trace (and then httpd.exe dies again):
> Request for address: home.htm
>
> Creating request object:
> ip = "16.30.16.15"
> protocol = "HTTP/1.0"
> method = "GET"
> agent = "Mozilla/3.01Gold
> (WinNT; I)"
>
> Creating server object:
> hostname = "gigi32.zko.dec.com"
> host = "gigi32.zko.dec.com"
> protocol = "http:"
> port = "80"
> httpdlwVersion = "1.01
> WindowsNT"
>
> Serving page...
>
> Error in LiveScript services:
> redirection to start.htm
>
> Redirected to new address:
> start.htm
>
> Final server object:
> hostname = "gigi32.zko.dec.com"
> host = "gigi32.zko.dec.com"
> protocol = "http:"
> port = "80"
> httpdlwVersion = "1.01
> WindowsNT"
>
> Request for address: start.htm
>
> Creating request object:
> ip = "16.30.16.15"
> protocol = "HTTP/1.0"
> method = "GET"
> agent = "Mozilla/3.01Gold
> (WinNT; I)"
>
> Creating server object:
> hostname = "gigi32.zko.dec.com"
> host = "gigi32.zko.dec.com"
> protocol = "http:"
> port = "80"
> httpdlwVersion = "1.01
> WindowsNT"
>
> Serving page...
>
> Database connect function: SQL
I've also saved the Dr. Watson dump -- but it doesn't make
any sense to me.
Any suggestions of how to proceed to fix this problem?
Bob
|
3776.4 | | RELYON::VILCANS | | Wed Feb 12 1997 12:27 | 11 |
|
re: last
Bob,
I actually have a book on Livewire Pro that your welcome to
borrow. I'm located in MRO. Livewire is a very poor software package, I
strongly recommend moving to IIS 3.0 with Active Server Pages and make
database connections using IDC or dbWeb.
=Paul=
|
3776.5 | User accounts perhaps | UCROW::GIBSON | | Wed Feb 12 1997 15:21 | 7 |
| It might be related to privs where the web server can not
access the database (or database client). You could try starting up and
running the Netscape server under the Informix account. That is what
I wound up doing in order to workaround database access problems with
the Livewire/Informix combo.
/Tom
|
3776.6 | FastTrack w/LiveWire runs standalone on NT WS or Win95 | PCBUOA::BAYJ | Jim, Portables | Wed Feb 12 1997 16:34 | 10 |
| IIS used to require NT Server, NTFS Partitions, SQL Server (which at
that time implied BackOffice), several other things I don't recall now,
and it really didn't run comfortably in less than 64MB. It took me
several weeks of reinstalling everything over and over before I finally
met all its criteria.
Have any of these requirements changed?
jeb
|
3776.7 | | RELYON::VILCANS | | Wed Feb 12 1997 16:43 | 8 |
|
re: last
IIS -- Comes with Server, runs on Workstation.
SQL Server -- SQL Server is preferred, but ODBC works adequately.
NTFS -- I have both NTFS and FAT systems running IIS.
=Paul=
|
3776.8 | | JGODCL::BOWEN | Set mode/papa=on/noexpire | Thu Feb 13 1997 11:11 | 3 |
| Also IIS runs on Windows95 Just there it's called Personal Web Server.
|
3776.9 | To switch, or not to switch... | PCBUOA::BAYJ | Jim, Portables | Thu Feb 13 1997 13:40 | 8 |
| Well, in that case, does IIS have a means for accessing network drives?
Supposedly FastTrack can, but I'm having trouble getting it to work.
If IIS is easier to work with now, is less of a pig, and can access
remote drives, then perhaps I should switch?
jeb
|
3776.10 | | JGODCL::BOWEN | Set mode/papa=on/noexpire | Fri Feb 14 1997 10:21 | 9 |
| Er yes and no.
I have a function that is loaded by the Global.asa file that maps a
network drive so the later ASP pages can refer to it, but it's not
really part of the Functionality of IIS
HtH
Kevin
|