Fixes are available
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
Client attempted to install multiple WebSphere 8.5 products: - IBM WebSphere Application Server 8.5.0.2 - IBM HTTP Server for WebSphere Application Server 8.5.0.2 - Web Server Plug-ins for IBM WebSphere Application Server 8.5.0.2 - WebSphere Customization Toolbox 8.5.0.2 Installation Manager 1.7.1 was used. Operating system is Windows 2008 When setting up IHS port (80), the user who is used to run the Windows Service selected is NOT a local user, the user is a Domain user. When installing WebSphere 8.5.0 the install program prompts to enter an user account. If this is entered with a domain prefix, it fails to validate. Removing the domain prefix allows the install to continue but then it fails to create the service properly at the end of the install (post-installation). The installation is successful if the target Windows Server is also a Domain Controller. If the Windows server is ONLY a member of a Domain and NOT a Domain Controller, it fails. The log file contains the following error: com.ibm.ws.exec.command.Exec Command: C:\IHS-WAS\HTTPServer\properties\install\script\sc.bat config IBMHTTPServerV8.5 type= own start= auto error= normal binpath= "C:\IHS-WAS\HTTPServer\bin\httpd.exe -k runservice" obj= displayname= "IBM HTTP Server V8.5" password= Description : Config HTTP server service for specific user account Return code : 1057 StdOut : [SC] ChangeServiceConfig FAILED 1057: The account name is invalid or does not exist, or the password is invalid for the account name specified. StdErr : Custom operation Config HTTP server service for specific user account in unit ihs.create.server.service.for.specific.user.win completed 401 INFO 02:59.00 Process error - line: AcceptSecurityContext failed with 8009030C 402 INFO 03:47.62 Process error - line: InitializeSecurityContext failed with 80090304 403 INFO 03:58.50 Process error - line: InitializeSecurityContext failed with 80090304 404 INFO 04:04.50 Process error - line: AcceptSecurityContext failed with 8009030C 405 INFO 04:08.98 Process error - line: AcceptSecurityContext failed with 8009030C AND WARNING 06:28.89 com.ibm.ws.exec.command.Exec Command: C:\Program Files (x86)\IBM\HTTPServer\properties\install\script\sc.bat config IBMHTTPServerV8.5 type= own start= auto error= normal binpath= "C:\Program Files (x86)\IBM\HTTPServer\bin\httpd.exe -k runservice" obj= displayname= "IBM HTTP Server V8.5" password= Description : Config HTTP server service for specific user account Return code : 1057 StdOut : [SC] ChangeServiceConfig account FAILED 1057: The account name is invalid or does not exist, or the password is invalid for the account name specified. The domain user fails to authenticate during the post installation and configuration, when a domain prefix is present. The domain user does have the correct rights and privileges.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: Users can not install IBM HTTP Server * * on Windows domain member server when * * select log on as a specified domain * * name account. * **************************************************************** * RECOMMENDATION: * **************************************************************** The Windows validator fails validate the domain user name and its password on Windows domain member. And the installation can not continue to call post install script sc.bat to install IHS even thought sc.bat does accept the domain user name and password and can install IBM HTTP Server correctly.
Problem conclusion
The fix is to set a skip property key so that the installation skips Windows validator and continues IHS installation. The Windows validator will be also skipped if the user is a domain user but it fails to be validated so that IHS installation continues. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.3. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI15397
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-04-07
Closed date
2014-04-30
Last modified date
2014-07-21
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
28 April 2022