PQ96461; 5.0.2.8: Error 100 when trying to start
service through service GUI
Downloadable files
Abstract
Error 100 occurs when trying to start WebSphere®
Application Server as a service through the Windows® service user
interface.
Download Description
PQ96461 resolves the following problem:
Problem Summary:
An error occurs while starting WebSphere Application service dmgr. The
error is "Error 100: Cannot create another system semaphore".
WebSphere Application Server starts correctly, but service status is not
changed.
Local fix:
none
Problem Conclusion:
For services that were created with no "LogRoot" parameter specified, it
is possible in some environments that the service will be unable to start.
For example, this fails with a Japanese locale.
For configurations prior to 5.0.2.6 (cumulative fix 6), this may be due to
problems parsing the server's pid from the stdout logs. On post 5.0.2.6
systems, there were problems with how the LogRoot path was defaulted and
built for services that had no LogRoot explicitly set.
This fix takes care of both classes of problem. Many different things can
cause the "Error 100" symptom, so here is a quick way to tell if this
problem is the cause of an Error 100. After verifying no
LogRoot parameter was set when the service was created, re-create the
service with a LogRoot specified. If the service starts after this is
done, then PQ96461 should resolve the problem.
Note: For above test, the LogRoot should be set to the log directory for
the server. The log directory will be
install_root\logs\server_name.
Prerequisites
Please download the UpdateInstaller below to install this fix.