what is InstantDB ?

[Richard]

Oh my, so many questions in this newsgroup go unanswered --- but I will try.

Installed WAS 3.02 development kit (came with Dreamweaver UltraDev) and set
it for InstantDB database. But when starting the AdminServer, I got the
infamous "Error 2140: An internal error has occurred". According to an IBM
Redbook, this is usually due to a bad database name or password in the
admin.config file. But the InstantDB selection during setup doesn't allow a
name or password entry, so my problem must be something else.

I can't find anything about InstantDB anywhere - does anybody know what is
going on here?

And what else might cause error 2140 ??

Thanks,
Richard

[David Baran]

InstantDB is a free RDBMS in Java. Go to http://instantdb.enhydra.org/ to
learn more about it.

For your problem, try to install WAS in the default directory
(/opt/WebSphere/AppServer on Solaris,
/usr/WebSphere/AppServer on AIX). I've resolved some problems (starting
AdminServer...) with this.

Richard a écrit dans le message <8nid9p$ooe$1...@news.software.ibm.com>...

[Ken Hygh]

Richard,
Lots of things can cause a 2140. Check <wasroot>\AppServer\logs\tracefile for
more information. You can also try starting WAS by executing
<wasroot>\AppServer\bin\debug\adminserver.bat, it will output more diagnostics.
If this succeeds, then it's something in how you're launching the service. I
usually click 'start as local system account', and don't check 'allow service to
interact with desktop'.

Ken

[Richard]

Ken -

Thanks so much for the tips !

Running ...\debug\adminserver.bat seems to work OK - no error messages at
all., ends with "WebSphere Administration server open for e-business".
Hooray!

The trace log from when I tried before has lots of entries similar to:
"Failure while locating a vhost for My_PC_Name and port 80, return code = 9"
So I will check the configuration again.

At least you helped get something to work.

Thanks,
Richard

[Ken Hygh]

Richard,
Bring up the Network window, and make sure that your DNS hostname matches your
PC name. I've seen problems when they're different...it seems to make NT
schizophrenic.

Ken

[Richard]

Ken - You guessed it, the DNS hostname is not the same as the PC name.

I've been distracted all day by my "real" work, but will give WAS another
try this weekend.

I'll post my results and let you know how it goes.

Richard

Ken Hygh <ken...@attglobal.net> wrote in message
news:399D378D...@attglobal.net...

[Richard]

David -

Thanks for the URL - looks like lots of good documentation and info - never
would have found it on my own.

Thanks,

Richard

[Richard]

Changing the DNS hostname to match the PC name didn't help anything.

But I continue to find more resources to work with - I found the list of all
WebSphere forums so I will keep researching. The computer I'm experimenting
with is an older 486 clone with 192 MB RAM - everybody who is succeeding
with WAS seems to have something newer than what I'm using.

Anyway, thanks again for the help. I'll keep trying as time permits.

Richard

[Ken Hygh]

Richard,
I can't conceive of it working on a 486.

Ken