Cannot start Admin Server on WAS 3.0

[Don Grodecki]

I installed WAS 3.0 on NT 4.0 under IIS, and it came up and ran just
fine. I added one directory to the reloadable path of the default server
and my servlets and JSPs ran.

I then upgraded to WAS 3.02, but when I tried to start it I got Error
2140 trying to start the Admin Server.

I started over with WAS 3.0. It still ran fine... for a while.

Now we are getting the 2140 Error with WAS 3.0 as well. We are using
InstantDB. I tried the port changes in admin.config with no luck, for
example using com.ibm.ejs.sm.adminServer.lsdPort=9997

Here is the JmonTraceBuffer that I get when I run adminserver.bat in
bin\debug. Also attached is a trace.log.iis.xxx. I have a 5.5MB
tracefile that is available on request.

Can anyone help? - Don

trace.log.iis.xxxx:
Tue Apr 04 19:38:58 2000 - Warning - Properties validate in
C:\WEBSPH~1\APPSER~1\properties\bootstrap.properties
Tue Apr 04 19:38:58 2000 - Error -
is_ok = 1

JmonTraceBuffer:
000.500 188fad ManagedServer E Version : 3.0
000.516 188fad ManagedServer E Edition: Standard
000.703 188fad ManagedServer E Build date: Sat Sep 25 00:00:00 CDT 1999
000.703 188fad ManagedServer E Build number: d28_990925d
006.157 188fad AdminServer A Initializing WebSphere Administration
server
006.344 188f17 DrAdminServer A DrAdmin available on port 1,050
045.828 3953f8 PluginCfgGene X Plugin Cfg Error
java.rmi.ServerException:
RemoteException occurred in server thread; nested exception is:
javax.transaction.TransactionRolledbackException: CORBA
TRANSACTION_ROLLEDBACK 0 No; nested exception is:
org.omg.CORBA.TRANSACTION_ROLLEDBACK: minor code: 0 completed: No
at javax.rmi.CORBA.Util.wrapException(Util.java:482)
at com.ibm.ejs.sm.beans._Node_Stub.listContainedObjects(Unknown Source)

at
com.ibm.servlet.engine.oselistener.systemsmgmt.PluginCfgGenerator$PluginCfgRunner.buildServletEngineList(PluginCfgGenerator.java:448)

at
com.ibm.servlet.engine.oselistener.systemsmgmt.PluginCfgGenerator$PluginCfgRunner.updateTransportData(PluginCfgGenerator.java:784)

at
com.ibm.servlet.engine.oselistener.systemsmgmt.PluginCfgGenerator$PluginCfgRunner.run(Compiled
Code)
at java.lang.Thread.run(Thread.java:472)
----- Begin backtrace for detail
javax.transaction.TransactionRolledbackException: CORBA
TRANSACTION_ROLLEDBACK 0 No; nested exception is:
org.omg.CORBA.TRANSACTION_ROLLEDBACK: minor code: 0 completed: No
----- Begin backtrace for detail
org.omg.CORBA.TRANSACTION_ROLLEDBACK: minor code: 0 completed: No

050.594 188fad AdminServer F Encountered an exception in the main
method java.rmi.ServerException: RemoteException occurred in server
thread; nested exception is:
javax.transaction.TransactionRolledbackException: CORBA
TRANSACTION_ROLLEDBACK 0 No; nested exception is:
org.omg.CORBA.TRANSACTION_ROLLEDBACK: minor code: 0 completed: No
at javax.rmi.CORBA.Util.wrapException(Util.java:482)
at com.ibm.ejs.sm.beans._Node_Stub.listContainedObjects(Unknown Source)

at
com.ibm.ejs.sm.server.AdminServer.getAllServers(AdminServer.java:1157)
at com.ibm.ejs.sm.server.AdminServer.getOrphanedServers(Compiled Code)
at
com.ibm.ejs.sm.server.AdminServer.completeNodeInitialization(AdminServer.java:1095)

at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:301)
----- Begin backtrace for detail
javax.transaction.TransactionRolledbackException: CORBA
TRANSACTION_ROLLEDBACK 0 No; nested exception is:
org.omg.CORBA.TRANSACTION_ROLLEDBACK: minor code: 0 completed: No
----- Begin backtrace for detail
org.omg.CORBA.TRANSACTION_ROLLEDBACK: minor code: 0 completed: No

[Don Grodecki]

[Curtis Ebbs]

Does the time/date stamp of JmonTraceBuffer match with the trace.log? I've
been caught before looking at an old JmonTraceBuffer file. I assume that
in doing the upgrade you re-booted your system (causing the webserver
to stop and unload the plug-in dlls). My recommendation would be to
to make a copy of the idbStore directory (and its contents) in WebSphere\AppServer\bin, delete the existing idbStore directory, set
install_initial_config=true in the admin.config
and then restart. This will isolate the problem to the database. If that is
the problem, my only recommendation is to go ahead and upgrade to 3.02
and then re-add your changes. Once you have your system running the
way you want, I would suggest making another backup copy of the idbStore
directory.

Good luck,
Curtis

[grod...@my-deja.com]

Using your recommendation to delete that directory and do an initial
config worked! Thanks!

Now I feel cocky, so I am going to try go to 3.02, get WAS working with
DB2, and install Site Analyzer!

Thanks again, Don

In article <38EB318D...@us.ibm.com>,

Sent via Deja.com http://www.deja.com/
Before you buy.

[Kevin McGuire]

I'ld recommend you don't waste your time with 3.0, its too buggy. Stick
with 3.02.

Did you upgrade the same product level (eg. standard to standard, advanced
to advanced)? Mixing the combinations gives subtle bugs.

Kevin

Curtis Ebbs <ce...@us.ibm.com> wrote in message
news:38EB318D...@us.ibm.com...

[grod...@my-deja.com]

Wow - thanks for that catch. Actually I am upgrading STD with Advanced.
I did not realize there were two separate upgrades. Thanks again. Now if
I could only get me download id to work .... - Don

In article <8cilmk$djo$1...@news.software.ibm.com>,