This week's book giveaway is in the OCMJEA forum.
We're giving away four copies of OCM Java EE 6 Enterprise Architect Exam Guide and have Paul Allen & Joseph Bambara on-line!
See this thread for details.
The moose likes Websphere and the fly likes IBM WS AdminServer fails to start Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCM Java EE 6 Enterprise Architect Exam Guide this week in the OCMJEA forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "IBM WS AdminServer fails to start" Watch "IBM WS AdminServer fails to start" New topic
Author

IBM WS AdminServer fails to start

Muthuvel Chinnachamy
Ranch Hand

Joined: Jun 13, 2001
Posts: 31
Hi,
I am new to Websphere and I have installed Websphere 3.5 on my NT server. After installation, I could not start the Admin server service and it reports "Service specific error 10".
Please help me to solve this problem.
Thanks and regards
Muthuvel C.
Rahul Mahindrakar
Ranch Hand

Joined: Jul 28, 2000
Posts: 1850
Hi,
You need administrative privalages to start the service. check out if your user id has these privalages.
Muthuvel Chinnachamy
Ranch Hand

Joined: Jun 13, 2001
Posts: 31
Hi,
Thanks for your reply.
I have logged on to NT Server as Administrator and tried. Also I have checked the path for Websphere for spaces. Still the service fails to start with the same error "Service specific error 10".
Please help me.
Thanks and regards
Muthuvel C.
Rahul Mahindrakar
Ranch Hand

Joined: Jul 28, 2000
Posts: 1850
Does your IBM HTTP Server start?
Rahul Mahindrakar
Ranch Hand

Joined: Jul 28, 2000
Posts: 1850
Also check out the properties for the services for IBM HTTP Server and IBM WAS AdminServer. You will have a Log on tab if you are using windows 2000 Professional where you have to put in the user id and password for both of these. check which user id and password you have specified. This user id must have administrative privalage

[This message has been edited by Rahul Mahindrakar (edited June 13, 2001).]
Muthuvel Chinnachamy
Ranch Hand

Joined: Jun 13, 2001
Posts: 31
Hi Rahul,
Thanks for your reply.
Yes, The IBM HTTP Server starts without any problem and I have tested thro browser.
Thanks and regards
Muthuvel C.
Rahul Mahindrakar
Ranch Hand

Joined: Jul 28, 2000
Posts: 1850
Have you undertaken "Quick install" or "Custom install" or there is a third option.
Normally the "Quick install" works without a problem if the administrative rights exist with a user.
Rahul Mahindrakar
Ranch Hand

Joined: Jul 28, 2000
Posts: 1850
if you can just paste your admin.conf file found in the
websphere\appserver\bin over here so that i can check out the configuration you are using
Muthuvel Chinnachamy
Ranch Hand

Joined: Jun 13, 2001
Posts: 31
Hi Rahul,
I have checked the service properties for WAS service, there Administrator user id and password is specified. Even I changed the account type to "System account" without Desktop interaction, still the service failed.
Please help me
thanks and regards
Muthuvel C.
Rahul Mahindrakar
Ranch Hand

Joined: Jul 28, 2000
Posts: 1850
You have not sent me the admin.conf file and also try shutting down and restarting.
Muthuvel Chinnachamy
Ranch Hand

Joined: Jun 13, 2001
Posts: 31
Hi Rahul,
I have pasted the content of admin.config. and I have done Full install.
thanks and regards
Muthuvel C.
----Admin.config-------
com.ibm.ejs.sm.adminServer.nameServiceJar=f:/WebSphere/AppServer/lib/ns.jar
com.ibm.ejs.sm.adminServer.jarFile=f:/WebSphere/AppServer/lib/repository.jar,f:/WebSphere/AppServer/lib/tasks.jar
com.ibm.ejs.sm.adminServer.dbUrl=jdbc:db2:was
com.ibm.ejs.sm.adminServer.dbDriver=COM.ibm.db2.jdbc.app.DB2Driver
com.ibm.ejs.sm.adminserver.classpath=f:/WebSphere/AppServer/lib/ibmwebas.jar;f:/WebSphere/AppServer/properties;f:/WebSphere/AppServer/lib/servlet.jar;f:/WebSphere/AppServer/lib/web tlsrn.jar;f:/WebSphere/AppServer/lib/lotusxsl.jar;f:/WebSphere/AppServer/lib/compat.jar;f:/WebSphere/AppServer/lib/xalan.jar;f:/WebSphere/AppServer/lib/ns.jar;f:/WebSphere/AppServe r/lib/ejs.jar;f:/WebSphere/AppServer/lib/ujc.jar;F:/PROGRA~1/SQLLIB/java/db2java.zip;f:/WebSphere/AppServer/lib/repository.jar;f:/WebSphere/AppServer/lib/admin.jar;f:/WebSphere/App Server/lib/swingall.jar;f:/WebSphere/AppServer/lib/console.jar;f:/WebSphere/AppServer/lib/was20cm.jar;f:/WebSphere/AppServer/lib/tasks.jar;f:/WebSphere/AppServer/lib/xml4j.jar;f:/W ebSphere/AppServer/lib/vaprt.jar;f:/WebSphere/AppServer/lib/sslight.jar;f:/WebSphere/AppServer/lib/ibmjndi.jar;f:/WebSphere/AppServer/lib/deployTool.jar;f:/WebSphere/AppServer/lib/ databeans.jar;f:/WebSphere/AppServer/classes;f:/WebSphere/AppServer/jdk/lib/tools.jar;f:/WebSphere/AppServer/lib/jsp10.jar;f:/WebSphere/AppServer/lib/dertrjrt.jar;f:/WebSphere/AppS erver/lib/derdbpw.jar;f:/WebSphere/AppServer/lib/ivjejb35.jar
com.ibm.ejs.sm.util.process.Nanny.adminServerJvmArgs=-Xmx128m -Xminf0.15 -Xmaxf0.25
com.ibm.ws.jdk.path=f:/WebSphere/AppServer/jdk
com.ibm.ejs.sm.util.process.Nanny.maxtries=3
com.ibm.ejs.sm.adminServer.traceFile=f:/WebSphere/AppServer/logs/tracefile
com.ibm.ejs.sm.util.process.Nanny.traceFile=f:/WebSphere/AppServer/logs/nanny.trace
com.ibm.ejs.sm.adminServer.logFile=f:/WebSphere/AppServer/tranlog/ntserver_tranlog1,f:/WebSphere/AppServer/tranlog/ntserver_tranlog2
com.ibm.ejs.sm.util.process.Nanny.path=f:\\WebSphere\\AppServer\\bin;F:\\PROGRA~1\\SQLLIB\\bin;F:\\PROGRA~1\\SQLLIB\\function;f:\\WebSphere\\AppServer\\jdk\\bin
com.ibm.ejs.sm.adminServer.initializer=com.ibm.ejs.security.Initializer,com.ibm.servlet.engine.ejs.ServletEngineAdminInitializer,com.ibm.servlet.config.InitialSetupInitializer
server.root=f:\\WebSphere\\AppServer
com.ibm.CORBA.ConfigURL=file:/f:/WebSphere/AppServer/properties/sas.server.props
com.ibm.ejs.sm.adminServer.dbUser=db2admin
com.ibm.ejs.sm.adminServer.dbPassword=db2admin
com.ibm.ejs.sm.adminServer.disableEPM=true
com.ibm.ejs.sm.util.process.Nanny.errtraceFile=f:/WebSphere/AppServer\\logs\\adminserver_stderr.log
install.initial.config=true
install.initial.config.file=f:/WebSphere/AppServer/properties/initial_setup.config
com.ibm.ejs.sm.adminServer.seriousEventLogSize=1000
com.ibm.ejs.sm.adminServer.qualifyHomeName=true

----end----------------
Rahul Mahindrakar
Ranch Hand

Joined: Jul 28, 2000
Posts: 1850
check out the trace file in the websphere\appserver\logs folder
This file will contain the information as to why your appserver did not start.
By the way did you set up your database and create a was database
Rahul Mahindrakar
Ranch Hand

Joined: Jul 28, 2000
Posts: 1850

do you have this file :F:/PROGRA~1/SQLLIB/java/db2java.zip
Is the data below correct
dbuser : db2admin
dbpassword :db2admin
Muthuvel Chinnachamy
Ranch Hand

Joined: Jun 13, 2001
Posts: 31
Hi Rahul,
Thanks for your reply.
I have installed DB2 on the same server and I dont know how to create WAS database. Can you throw some light on this area?
Thanks and regards
Muthuvel C.
Rahul Mahindrakar
Ranch Hand

Joined: Jul 28, 2000
Posts: 1850
which Operating system are you using. Basically i feel that it is not able to connect to the database as it is not configured. If you try a quick install things will work without a glitch. The full install may be creating a problem for you.
Try downloading the infocenter later on for documentation on WAS.
Muthuvel Chinnachamy
Ranch Hand

Joined: Jun 13, 2001
Posts: 31
Hi Rahul,
Yes, Ihave this file :F:/PROGRA~1/SQLLIB/java/db2java.zip
dbuser : db2admin
dbpassword :db2admin are correct.
Thanks and regards
Muthuvel C.
Rahul Mahindrakar
Ranch Hand

Joined: Jul 28, 2000
Posts: 1850
If you tell me your Operating system i will send you the specific documentation by mail.
Rahul
Muthuvel Chinnachamy
Ranch Hand

Joined: Jun 13, 2001
Posts: 31
Hi Rahul,
I am using WINNT 4.0. As you suggested, I will uninstall Websphere and Install it again with Quick install option.
Thanks and regards
Muthuvel C.
Rahul Mahindrakar
Ranch Hand

Joined: Jul 28, 2000
Posts: 1850
Paste your trace file data here. I have given where it is located earlier.
Rahul Mahindrakar
Ranch Hand

Joined: Jul 28, 2000
Posts: 1850
Yeah i think for starters that is the best way.
Best of Luck.
Muthuvel Chinnachamy
Ranch Hand

Joined: Jun 13, 2001
Posts: 31
Hi Rahul,
As the Trace file is large around 70K, I am attaching the part alone.
Thanks
Muthuvel C.
---Start
[00.01.14 11:16:42:287 GMT+05:30] 823aaed4 CreateNsTable W Failed to create tables COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1013N The database alias name or database name "WAS" could not be found. SQLSTATE=42705
at java.sql.SQLException.<init>(SQLException.java:45)
at COM.ibm.db2.jdbc.DB2Exception.<init>(DB2Exception.java:93)
at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(SQLExceptionGenerator.java:164)
at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.check_return_code(SQLExceptionGenerator.java:402)
at COM.ibm.db2.jdbc.app.DB2Connection.connect(DB2Connection.java:340)
at COM.ibm.db2.jdbc.app.DB2Connection.<init>(DB2Connection.java:321)
at COM.ibm.db2.jdbc.app.DB2Driver.connect(DB2Driver.java:337)
at com.ibm.ejs.cm.pool.JDBC1xConnectionFactory.createConnection(JDBC1xConnectionFactory.java:32)
at com.ibm.ejs.cm.pool.ConnectionPool.createConnection(ConnectionPool.java:637)
at com.ibm.ejs.cm.pool.ConnectionPool.createOrWaitForConnection(ConnectionPool.java:590)
at com.ibm.ejs.cm.pool.ConnectionPool.findFreeConnection(ConnectionPool.java:520)
at com.ibm.ejs.cm.pool.ConnectionPool.findConnectionForTx(ConnectionPool.java:472)
at com.ibm.ejs.cm.pool.ConnectionPool.allocateConnection(ConnectionPool.java:424)
at com.ibm.ejs.cm.pool.ConnectionPool.getConnection(ConnectionPool.java:169)
at com.ibm.ejs.cm.DataSourceImpl.getConnection(DataSourceImpl.java:113)
at com.ibm.ejs.cm.SMDataSource.getConnection(SMDataSource.java:83)
at com.ibm.ejs.ns.CosNaming.CreateNsTables.dbInit(CreateNsTables.java:135)
at com.ibm.ejs.ns.CosNaming.NameServer.init(NameServer.java:276)
at com.ibm.ejs.sm.server.ManagedServer.initializeNameService(ManagedServer.java:931)
at com.ibm.ejs.sm.server.ManagedServer.initializeRuntime(ManagedServer.java:528)
at com.ibm.ejs.sm.server.AdminServer.initializeRuntime(AdminServer.java:969)
at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:353)
[00.01.14 11:16:42:508 GMT+05:30] 823aaed4 AdminServer A Initializing WebSphere Administration server
[00.01.14 11:16:42:598 GMT+05:30] 53d02ed7 DrAdminServer A DrAdmin available on port 1,594
[00.01.14 11:16:42:678 GMT+05:30] 823aaed4 DBMgr F Failed to create a data source: COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1013N The database alias name or database name "WAS" could not be found. SQLSTATE=42705
at java.sql.SQLException.<init>(SQLException.java:45)
at COM.ibm.db2.jdbc.DB2Exception.<init>(DB2Exception.java:93)
at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(SQLExceptionGenerator.java:137)
at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.check_return_code(SQLExceptionGenerator.java:402)
at COM.ibm.db2.jdbc.app.DB2Connection.connect(DB2Connection.java:340)
at COM.ibm.db2.jdbc.app.DB2Connection.<init>(DB2Connection.java:321)
at COM.ibm.db2.jdbc.app.DB2Driver.connect(DB2Driver.java:337)
at com.ibm.ejs.cm.pool.JDBC1xConnectionFactory.createConnection(JDBC1xConnectionFactory.java:32)
at com.ibm.ejs.cm.pool.ConnectionPool.createConnection(ConnectionPool.java:637)
at com.ibm.ejs.cm.pool.ConnectionPool.createOrWaitForConnection(ConnectionPool.java:590)
at com.ibm.ejs.cm.pool.ConnectionPool.findFreeConnection(ConnectionPool.java:520)
at com.ibm.ejs.cm.pool.ConnectionPool.findConnectionForTx(ConnectionPool.java:472)
at com.ibm.ejs.cm.pool.ConnectionPool.allocateConnection(ConnectionPool.java:424)
at com.ibm.ejs.cm.pool.ConnectionPool.getConnection(ConnectionPool.java:169)
at com.ibm.ejs.cm.DataSourceImpl.getConnection(DataSourceImpl.java:113)
at com.ibm.ejs.cm.SMDataSource.getConnection(SMDataSource.java:83)
at com.ibm.ejs.sm.util.db.DBMgr.initialize(DBMgr.java:183)
at com.ibm.ejs.sm.server.AdminServer.startConnectionMgr(AdminServer.java:1193)
at com.ibm.ejs.sm.server.AdminServer.initializeRuntime(AdminServer.java:984)
at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:353)
FATAL Failed to create a data source: {0} COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1013N The database alias name or database name "WAS" could not be found. SQLSTATE=42705
at java.sql.SQLException.<init>(SQLException.java:45)
at COM.ibm.db2.jdbc.DB2Exception.<init>(DB2Exception.java:93)
at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(SQLExceptionGenerator.java:137)
at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.check_return_code(SQLExceptionGenerator.java:402)
at COM.ibm.db2.jdbc.app.DB2Connection.connect(DB2Connection.java:340)
at COM.ibm.db2.jdbc.app.DB2Connection.<init>(DB2Connection.java:321)
at COM.ibm.db2.jdbc.app.DB2Driver.connect(DB2Driver.java:337)
at com.ibm.ejs.cm.pool.JDBC1xConnectionFactory.createConnection(JDBC1xConnectionFactory.java:32)
at com.ibm.ejs.cm.pool.ConnectionPool.createConnection(ConnectionPool.java:637)
at com.ibm.ejs.cm.pool.ConnectionPool.createOrWaitForConnection(ConnectionPool.java:590)
at com.ibm.ejs.cm.pool.ConnectionPool.findFreeConnection(ConnectionPool.java:520)
at com.ibm.ejs.cm.pool.ConnectionPool.findConnectionForTx(ConnectionPool.java:472)
at com.ibm.ejs.cm.pool.ConnectionPool.allocateConnection(ConnectionPool.java:424)
at com.ibm.ejs.cm.pool.ConnectionPool.getConnection(ConnectionPool.java:169)
at com.ibm.ejs.cm.DataSourceImpl.getConnection(DataSourceImpl.java:113)
at com.ibm.ejs.cm.SMDataSource.getConnection(SMDataSource.java:83)
at com.ibm.ejs.sm.util.db.DBMgr.initialize(DBMgr.java:183)
at com.ibm.ejs.sm.server.AdminServer.startConnectionMgr(AdminServer.java:1193)
at com.ibm.ejs.sm.server.AdminServer.initializeRuntime(AdminServer.java:984)
at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:353)

---End
Rahul Mahindrakar
Ranch Hand

Joined: Jul 28, 2000
Posts: 1850
so ---Start
[00.01.14 11:16:42:287 GMT+05:30] 823aaed4 CreateNsTable W Failed to create tables COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1013N The database alias name or database name "WAS" could not be found. SQLSTATE=42705

As i stated you have not created the WAS database. If you can do this things will work
You also learnt today where to look for in case of a problem.
Look in the trace file for problems.
Rahul
Muthuvel Chinnachamy
Ranch Hand

Joined: Jun 13, 2001
Posts: 31
Hi Rahul,
Thanks for your help. I have uninstalled WAS server and reinstalled again with Quick install option. NOW THE WAS SERVICE IS STARTING WITHOUT ANY PROBLEM.
Again, Thanks for your help.
Regards
Muthuvel C.
Tony Chen
Ranch Hand

Joined: Jan 29, 2001
Posts: 286
You really don't have to un-install and re-install WAS. All you need to do is to creat the WAS DB by running the script createdb2.bat under \WebSpehre\AppServer\bin directory.
------------------
Tony Chen
SCJP, ICS & ICSD (WebSphere)


SCJP Java 2 - IBM Certified Enterprise Developer - WebSphere V4.0 & V5.0 - IBM Certified System Administrator - WebSphere Network Deployment V6.0 - Canadian Securities Course (CSC) Certification
Muthuvel Chinnachamy
Ranch Hand

Joined: Jun 13, 2001
Posts: 31
Hi Tony,
Thanks for your help.
Muthuvel C.
Rahul Mahindrakar
Ranch Hand

Joined: Jul 28, 2000
Posts: 1850
As tony says

All you need to do is to creat the WAS DB by running the script createdb2.bat under \WebSpehre\AppServer\bin directory.

However this bat file is not available under the Quick install option as idb is installed. I have a quick install and so i could not find this file and hence did not suggest it to you.

Tony Chen
Ranch Hand

Joined: Jan 29, 2001
Posts: 286
Oops, sorry about that!
------------------
Tony Chen
SCJP, ICS & ICSD (WebSphere)
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: IBM WS AdminServer fails to start