Asadmin start-appserv fails after install

Question

I have just installed SunOne app server 7 on an E220R running Solaris 9.
After installation asadmin start-appserv fails with:
bash-2.05# ./asadmin start-appserv
Nov 1 15:01:24 w1 appservd-wdog[3240]: server initialization failed (Interrupted system call)
Could not start the instance: domain1:admin-server
server failed to start: abnormal subprocess termination
Nov 1 15:01:31 w1 appservd-wdog[3254]: server initialization failed (Interrupted system call)
Could not start the instance: domain1:server1
server failed to start: abnormal subprocess termination
Could not start one or more instances in the domain : domain1
Could not start one or more domains
/etc/opt/SUNWappserver7/asenv.conf has the correct AS_INSTALL directory and pkginfo looks like this:
bash-2.05# pkginfo -l SUNWascmo
PKGINST: SUNWascmo
NAME: Sun ONE Application Server unbundled (common)
CATEGORY: system
ARCH: sparc
VERSION: 7.0,REV=2002.10.08.16.47
BASEDIR: /raid0/local/SUNWappserver7
VENDOR: Sun Microsystems, Inc.
DESC: Application Server common components
PSTAMP: korea20021008164747
INSTDATE: Nov 01 2002 14:55
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES: 4 installed pathnames
2 shared pathnames
2 directories
16493 blocks used (approx)
bash-2.05# pkginfo -l SUNWasaco
PKGINST: SUNWasaco
NAME: Sun ONE Application Server Admin Client, unbundled
CATEGORY: system
ARCH: sparc
VERSION: 7.0,REV=2002.10.08.16.47
BASEDIR: /raid0/local/SUNWappserver7
VENDOR: Sun Microsystems, Inc.
DESC: Application Server Admin Client
PSTAMP: korea20021008165101
INSTDATE: Nov 01 2002 14:55
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES: 6 installed pathnames
3 shared pathnames
3 directories
2 executables
1713 blocks used (approx)
An example of the log errors is:
[01/Nov/2002:15:01:20] INFO ( 3241): CORE1116: Sun ONE Application Server 7.0
[01/Nov/2002:15:01:20] INFO ( 3242): CORE3016: daemon is running as super-user
[01/Nov/2002:15:01:22] SEVERE ( 3242): exception initializing server side logger com.iplanet.ias.config.ConfigException: Error refreshing ConfigContext
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
null
com.iplanet.ias.config.ConfigException: Error refreshing ConfigContext
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
null
     at com.iplanet.ias.config.ConfigContextImpl.refresh(ConfigContextImpl.java:277)
<extended stack trace redacted>
/2002:15:01:23] SEVERE ( 3242): exception initializing server side logger com.iplanet.ias.config.ConfigException: Error refreshing ConfigContext
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
null
com.iplanet.ias.config.ConfigException: Error refreshing ConfigContext
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
null
     at com.iplanet.ias.config.ConfigContextImpl.refresh(ConfigContextImpl.java:277)
<snip>
[01/Nov/2002:15:01:23] FINE ( 3242): reinitializeLogger: javax.enterprise.system.core com.sun.logging.enterprise.system.core.LogStrings FINEST
[01/Nov/2002:15:01:23] SEVERE ( 3242): exception initializing server side logger com.iplanet.ias.config.ConfigException: Error refreshing ConfigContext
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
null
com.iplanet.ias.config.ConfigException: Error refreshing ConfigContext
cause: Failed to create the XML-DOM Document. Check your XML to make sure it is correct.
null
     at com.iplanet.ias.config.ConfigContextImpl.refresh(ConfigContextImpl.java:277)
<snip>
<etc>
Can you give me an idea of what might be the problem?

Answer 1

Could you please check <install_dir>/install.log file for any possible warnings. Also, are there any characters
other than alphanumeric, dash, underscore in any of the parameters provided to the installation program?
Based on the startup log entry, server configuration files seems to be corrupted.