Troubleshooting server tools after a typical installation on Windows

Edit online
After a typical installation by a nonadministrative user on Windows7, server tools such as the Quick Start console, startServer command, or the Profile Management Tool will not successfully access the server unless you elevate your user permissions by using Run as administrator.

If you ran the typical installation as an administrator, the deployment environment created during the typical installation process must be administered by a user ID with likewise elevated permissions. If you are now administering the deployment environment with a nonadministrative user ID, you must elevate your permissions to Administrator to do operations such as starting and stopping servers, deployment managers, and nodes, or running the Quick Start console or the Profile Management Tool. Running these operations with a non-elevated ID will result in error messages.

Affected server tools include:
  • BPMQuickStart command and the Quick Start console
  • firststeps command and the First steps console
  • manageprofiles command and the Profile Management Tool
  • startServer command
  • stopServer command
  • startManager command
  • stopManager command
  • startNode command
  • stopNode command
To elevate your permissions to Administrator when starting one of these tools from a shortcut, right-click it and click Run as administrator. When running a command, run it in a Command Prompt window that you have opened by right-clicking the Command Prompt shortcut and clicking Run as administrator.

If you cannot elevate your user ID authority to Administrator, install IBM® Business Automation Workflow using a custom installation path and configure the deployment environment with a nonadministrative user ID.