Symptom
- Servers in stopped state throwing error message below in Central management console.
- The executable could not be launched. Possible reasons are insufficient RAM or disk space, or an invalid filepath or working directory. Actual reason: Could not start '"<install directory>\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\<servername>.exe" -loggingPath "<install directory>/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/logging/" -documentType CrystalEnterprise.Report -fg -restart -name <servername> -pidfile "D:/Program Files (x86)/SAP BusinessObjects/SAP BusinessObjects Enterprise XI 4.0/serverpids/<servername>.pid" -fips -ns <hostname> in path '<install directory>\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64'. Details: CreateProcess error=2, The system cannot find the file specified.
Read more...
Environment
- SAP Business Objects Business Intelligence Platform 4.2
- SAP Business Objects Business Intelligence Platform 4.3
Keywords
Server, BI, CMC, 4.2, 4.3, Stopped, Disabled, RAM, diskspace, , KBA , BI-BIP-ADM , BI Servers, security, Crystal Reports in Launchpad , BI-BIP-BIW , BI Workspaces (Dashboard Builder) , BI-BIP-SRV , CMS / Auditing issues (excl. 3rd Party Authentication) , 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.