PM51952: STARTSERVER FAILS BECAUSE OF PERMISSION ERRORS

8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• The startServer command will fail if a userProfile
  without *ALLOBJ authority had started the server priviously
  and a second userProfile without *ALLOBJ authority
  subsequently attempts to start the same server.  This is due
  to the runConfigActions script being called from the
  startServer code, and it creates directories and files that
  are owned by the first userProfile which the second
  userProfile does not have authority to access.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.0 on IBM i systems.               *
  ****************************************************************
  * PROBLEM DESCRIPTION: The startServer command fails with      *
  *                      authority issues, when the server had   *
  *                      been previously started with a          *
  *                      different userProfile.                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The startServer command will fail if a userProfile without
  *ALLOBJ authority had started the server priviously and a
  second userProfile without *ALLOBJ authority subsequently
  attempts to start the same server.  This is due to the
  runConfigActions script being called from the startServer
  code, and it creates directories and files that are owned by
  the first userProfile which the second userProfile does not
  have authority to access.
  

Problem conclusion

• This problem was fixed by swapping to use the IBM provided
  userProflile QEJBSVR prior to calling the runConfigActions
  function. This ensures that all user's that call startServer
  will run the config actions using the common userProfile and
  avoid authority issues.
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.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 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

• R800 PSY

     UP