SAP Knowledge Base Article - Preview

1638408 - SBOP Enterprise XI 3.1 - Services do not start following re-install under a different path

Symptom

  • CreateProcess error in the Event Viewer
  • An error is displayed in red in the properties of the Business Objects Enterprise (BOE) services: go to Central Management Console (CMC) > Servers > Right-click on a stopped server > Properties

The executable could not be launched. Possible reasons are insufficient RAM or disk space, or an invalid filepath or working directory. Actual reason: CreateProcess: "C:\BusinessObjects\BusinessObjects Enterprise 12.0\win32_x86\ConnectionServer.exe" -loggingPath "C:/BusinessObjects/BusinessObjects Enterprise 12.0/logging/" -fg -restart -name %HOSTNAME%.ConnectionServer -pidfile "C:\Program Files (x86)\Business Objects\BusinessObjects Enterprise 12.0\serverpids\%HOSTNAME%_%HOSTNAME%.ConnectionServer.pid" -ns %HOSTNAME%:6400 error=267


Read more...

Environment

  • BUSINESSOBJECTS ENTERPRISE (BOE) XI 3.1
  • MICROSOFT WINDOWS SERVER

Product

SAP BusinessObjects Enterprise XI 3.1

Keywords

xi31, xir3, xi3, xir31, erase, absolute, stopped, fail , KBA , BI-BIP-DEP , Webapp Deployment, Networking, Vulnerabilities, Webservices , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.