Weblogic-IIS Troubleshooting

Project Details:

Project code: PGPASIMS

Project Type: Troubleshooting/Maintenance
Software: Win 2k/2K3 Servers, Weblogic 7.X/8.X, IIS 5.0/6.0
Hardware: Regular P2/P3/Zeon machines, ~8 GB RAM, ~50 GB
HDD.

Introduction

The document gives an approach to troubleshoot basic Weblogic-

IIS setup, Weblogic running on Windows. The document has been
written keeping in mind a simple setup containing one admin and
2-3 managed servers. The error messages and possible solutions
have been generalized as much as possible, but it’s still possible
that they do not hold good for an odd scenario.

S No. Issue Error message Possible Meaning Resolution

1. WL admin console not ISAPI Plug-in error Admin server not Check admin server’s log file and
reachable running restart it.
2. Managed server not coming up … NodeManagerException… The admin server is Check whether node manager is
Ensure that the NodeManager on unable to contact properly configured properly to
host 'localhost' is configured to managed server run on the same machine and
listen on port '6666' and that it is through node port number as in this error
actively listening manager (NM) message.
…

3. Managed server not coming up The status is There should be Restart NM and try starting the
Failed_NOT_Restartable some problem with server again.
the Node Manager.

4. Managed server not coming up The status is Failed_Restarting There should be Restart NM and try again.
some problem with
the Node Manager.

5. Managed server not coming up …Trying to start in independent
mode…Config-msi.xml file
missing…Failed starting…
Managed server is Restart Node Manager and try. If
not able to see the possible, restart admin server
admin server and try once more. If it still
running. doesn’t work, look for errors in
admin server’s log file

6. Application URL not working The page cannot be displayed The application may Check the status of WL servers. If
not be reaching WL ok, check status of IIS servers.
servers at all You may want to check IIS logs
for details about the failing
request as to where exactly is it
failing.

7. Application URL not working Oblix Netpoint Operation Error Oblix License issue Check in case Oblix license has
expired.
8. Application URL not working Directory Listing Denied The website is Verify that the virtual directory
configured to use has been setup properly
virtual directory(s)
and there is some
issue with it.

9. Querying not working for an LD There should be Check LD server’s log file to see
javax.ejb.CreateException:
server. some problem in the the exact problem.
Server Error (Management) 1-4-
LD Server, due to
1-301: Query server is not
which Query server is
available.
not working.

10. Liquid Data( LD) console not This indicates a Try and find out the problem with
No link to go to LD console can
available for a newly setup LD problem with the LDS the deployment logged
be seen on the WL console
domain. deployment. somewhere. If nothing else
works, you can consider re-
deploying LDS.