IBM Support

WebSphere v8.0 server profile created as a Windows service could not be started or published to in RAD and how to remove the service?

Technote (troubleshooting)


An IBM WebSphere Application Server (WAS) v8.0.0.x server profile created to be run as a Microsoft Windows service could not be started on Windows 7 32-bit in IBM Rational Application Developer (RAD) v8.x. Both are installed in C:\Program Files using an administrator group ID. Security was not enabled on the server.


Could not start the WAS v8 server profile or publish an EAR/application to it in Rational Application Developer.

In another related user scenario, when running trying to run an application in a WAS server (and start the server) using Run on Server the following error occurred:

... failed while trying to start windows service associated with server. Problem is executing was service. exc: starting service:machine name node 01 service failed to start. Return code =-1.


RAD was not started using "Run As Administrator" and the WAS server profile was created to be run as a Windows service.


Windows v7 Professional 32-bit or 64-bit

Diagnosing the problem

1. Is RAD on Windows 7 (or Vista) installed under C:\Program Files or C:\Program Files (x86)?
2. Is the WebSphere server profile listed in Windows under
Windows Start > Control Panel > Administrative Tools > Services?

Resolving the problem

This is a two part problem. However, the major issue is that the WAS server profile was created to be run as a Windows service.

    1. In the case of Windows 7 (or Vista), with both RAD and WAS installed in the C:\Program Files directory, you must start RAD using Run As Administrator, especially in order to run WAS in IBM Rational Software Architect (RSA) or RAD.

      Note: In Windows 7 you can set up an application to be Run As Administrator by default.
      Right-click on the RAD icon on the desktop (or under Start > Programs)
      > Properties : Compatibility tab .
      There is a checkbox you can check to "Run As Administrator".

      After restarting RAD using Run As Administrator, it is now possible to start/stop the server in RAD but the console view does not show anything and publishing to the server is not successful.
      This leads to the primary issue next.
    2. Primary issue: You should never create an WAS server profile as a service as it can lead to problems in RAD Server Tools and is not supported in RAD v6+ for any WAS v6+ server.

      For example, this RAD document 1263551: Creating a new WebSphere Application Server v6.1 profile stresses to use the Advanced profile creation option and to uncheck the "Run the application as a Windows service" checkbox when creating a profile. It also applies to any WAS 6x/7x/8x server profile created for use in any RAD v7x/8x. In RAD v8x use the Advanced creation selection in the WAS Profile Management Tool (PMT) under:
      Windows > Preferences > Server > WebSphere Application Server

      If you have created a WAS server profile as a Windows service, there is a WAS command to undo this. In the Windows command prompt:

      > [WAS_HOME]\bin\WASService.exe -remove [WAS_SERVICE_NAME]

      For any WAS v6x/7x installed as part of RAD:
      [WAS_HOME] == [RAD install dir]\SDP\runtimes\base_v<n>
      Any WAS v8x server provided with RAD is installed as a standalone server, in a location apart from RAD.


      The Windows service name for a WAS server profile can be determined using either of these options:
      • Take a look at the [WAS_HOME]\profiles\AppSrv0<n>\logs folder. There would be <service name> service.log file if it is a service. The file typically looks like:
        The service name is <somename>-<host>Node<0n>
      • In Windows you can find a list of services under
        Windows Start > Control Panel > Administrative tools > Services

        Open the tool and find the service starting with:
        IBM WebSphere Application Server v<N.x> - <somename>-<host>Node<0n>
        The later part of the name after the dash with spaces around it:
        , is the service name required by the WASService.exe command.
        Right-click on WebSphere Application Server v<N.x> ... > Properties: General [Tab] will also show it.

      This non-IBM reference has helpful screen shots: Removing WAS Service . It is provided " as is" and is not an officially supported document. Similarly, these non-IBM references explain the WASService.exe command and how to specify the service name for this command, which is not the same as the full Windows service name:
      - Using the WASService.exe Command
      - How to delete a profile from a WebSphere 6.1 application server

      For example, in Windows the WAS85 Services name has a "dash" with spaces around it:
      "IBMWAS85Service - SRV-9MINE1Node01"
      , before SRV-9MINE1Node01 .
      You must use the service name after the dash with spaces around it:
      > WASService .exe -remove "SRV-9MINE1Node01"

      Alternately, create a new profile that is not to be run as a service, and use it.

References :

The following RAD Information Center (KC) item stresses not to create a WAS server profile as a service in RAD.
- RAD v8.5 IC item:
Creating a profile on a local WebSphere Application Server V8.5, V8.0, or V7.0

    5. Configure your profile by following instructions in the Profile Management Tool. For more information on configuring a profile using the Profile Management tool, see the Using the Profile to create an application server topic.

    Tip: (On Windows)
    1. In the case you select the Advanced profile creation option, in the Windows Service Definition page of the Profile Management Tool, clear the Run the Application Server process as a Windows service check box. Window services are global settings on an operating system. Clearing this check box avoids conflict of service requests between different profiles. For example, if you configure an application server as a Windows service and issue the startServer command, the wasservice command attempts to start the defined service. As a result, you can lose track of which profile issued the startServer command, as any profile can start this globally defined Window service.

More information on Windows services and WASService.exe -remove.

Changing a WAS or any Windows service to start "manually" from "automatically" in the Windows Services tool is NOT THE SAME as  removing the Windows service using the WebSphere
  > WASService.exe -remove service_name

WASService "remove" deletes the service.
Changing to "manual" in Windows Services will keep the service on Windows
but allow you to start the service manually.
If you do not want the WAS profile to be a service, then remove it.
RAD requires removing the service

A "Windows" and WAS service FYI:

If you want to keep the WAS profile as a service  (assuming its not used by RAD), and don't want the startServer or startNode or startManager commands to use the Windows service on startup then change it to "disabled" instead of "manual" in Windows.

Windows services have four startup types:

- Automatic:  it is started by the Windows O/S at system bootup.

- Automatic (delayed start) "NEW":   it is started by the Windows O/S at system bootup with a delay.
A service marked as Automatic (Delayed Start) will start shortly after all other services designated as Automatic have been started.This will ensure that the critical services get the most resources early and become available sooner, while the non-critical services
start a bit later. The default delay of 120 seconds, which can be overridden by the AutoStartDelay value in HKLM\SYSTEM\CurrentControlSet\Control.

- Manual: not started at bootup.
The service will start only when Windows or another service needs it, or if you invoke something to start the service. You can use the command:  net start < servicename> , from the command line to enable a manual service. refer to: Start, stop, pause, resume, or restart a service. When you reboot, the service will again be off until you restart it.

- Disabled: not started at bootup
The service will stay off, regardless of whether you try to start it or not. Other services or applications which depend on the disabled service may fail.

Consult the Microsoft documentation for accurate and latest details on services

Related information

WASv7: WASService command

Document information

More support for: Rational Application Developer for WebSphere Software
Server Tooling

Software version:, 6.0.1,,, 7.0,,,,,,,,,,, 7.5, 7.5.1, 7.5.2, 7.5.3, 7.5.4, 7.5.5,,,,,, 8.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4,,, 8.5, 8.5.1

Operating system(s): Linux, Windows

Reference #: 1618376

Modified date: 16 January 2017

Translate this page: