IBM Support

PM30383: GENERATED SCRIPT START_SERVER.BAT CANNOT BE RUN FROM DRIVE OTHER THAN THE DRIVE WHERE <PROFILE_HOME>/BIN IS LOCATED.

Fixes are available

7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • WebSphere Application Server V6.1 and V7 on Microsoft Windows
    operating systems
    A start_server.bat script generated from the startserver.bat
    -script command can be run only from the drive where the
    profile resides.
    
    When the start_server.bat script is generated, the path provided
    is the path from which startserver.bat is being run. For
    example C:\Program
    Files\IBM\WebSphere\Appserver\profiles\profile_name\bin. When
    the generated script is run from another drive, no provision is
    made
    

Local fix

  • The only workaround is to edit the generated script to add a
    drive change as required by Windows
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V6.1 and V7.0                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: On Microsoft Windows, the script        *
    *                      generated by running startServer.bat    *
    *                      <server-name> with -script option       *
    *                      fails to start the server if it is      *
    *                      run from a drive other than the one     *
    *                      where WebShpere Application Server is   *
    *                      installed.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Since the full path to setupCmdLine.bat is not specified in
    the script generated by running startServer.bat with -script
    option, the script fails to start the server if it is run from
    a drive where WebSphere Application Server is not installed.
    This is because on Microsoft Windows the drive switch must
    occur before directory change.
    

Problem conclusion

  • By specifying the full path to setupCmdLine.bat in the
    generated script, the script can successfully start the
    specified server, even if it is run from a drive where
    WebSphere Application Server is not installed. This code
    change only affects the scripts that are newly generated after
    the fix is applied, and not the scripts that were previously
    generated by running startServer.bat with -script option.
    The fix for this APAR is currently targeted for inclusion in
    fix packs 6.1.0.39 and 7.0.0.19. 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

    PM30383

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-01-12

  • Closed date

    2011-02-24

  • Last modified date

    2011-02-24

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R61W PSY

       UP

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM30383

Modified date: 24 February 2011