Great to see that Life Cycle Manager is now bundled with the SAP BI 4 platform.
I have been trying to configure the tool via the Administration Options based on the settings I know have worked in several Life Cycle Manager installations I have done on XI 3.1.
Has anything changed with the XI 4 configuration because no matter what I try I keep receiving the following error when I try to launch the Version Management System?
com.businessobjects.vms.VMSException: com.businessobjects.vms.VMSException: com.businessobjects.vms.VMSException: com.businessobjects.vms.VMSException: java.io.IOException: Cannot run program "E:\BOXI4\SAP": CreateProcess error=2, The system cannot find the file specified
I have looked at the Life Cycle Manager 4 manual and nothing seems to have changed configuration wise there either?
Can anyone explain why this may not be working? Any pointers?
Thanks - Gary
You can try this :
1645887 - How-to configure LifeCycle Manager (LCM) with
subversion (svn) using http
1632394 - Version management error when logging
1543777 - Error while logging into Version Management of Life
1415280 - How to install Subversion
How to configure the Subversion repository
This wasn't my exact problem but your notes/guidance above helped guide me along the right lines in solving the problem.
My subversion directory needed to be pointed to the E: drive where the SAP BI 4 installation was and the directory of course needed to be specified with forward slashes rather than back slashes in the Version Management settings/configuration setting.
e.g. for example - E:/BOXI4/SAP BusinessObjects Enterprise XI 4.0/subversion.
All working now. So many thanks.
After re-testing/re-checking I conclude that you are indeed correct.
So the real problem after further investigation was because Subversion didn't install properly and/or because (possibly) it was not installed to the Business Objects default installation path e.g. (C:\Program Files (x86)\SAP Business Objects .......) the Version Management settings were not implemented correctly as I noticed on our test server we do not have the same problem and the Version Management settings have picked up the installation path correctly.
As soon as I have put in the path I have mentioned above Life Cycle Manager has started working.
I am using BOXI 4 SP2 Patch 12.