I was installing version 6.5.1 and had the same error.
Tried the suggestions in the posts on this subject but I was still getting the error.
In the end I uninstalled Business Objects and then re-installed to a different directory path (rather than the default suggested). I used a short directory path with no spaces in the name. When I configured this time it all worked without any problems.
Just to warn others on Business Objects 6.5.1 using Windows 2003 and Apache/Tomcat that I have also seen this error when using the Business Objects Configuration Tool. I have also seen a similar error ‘Error Configuring Tomcat’ with the same cause.
I discovered that Business Objects when configuring does some writing of files to your temporary directory.
If you directory is set up like the following C:\Document and Settings\Scott705\Local Settings\Temp then Tomcat will not be able to write to it and trigger the ‘Cannot Find the Orb Configuration File’ or the ‘Error Configuring Tomcat’ errors.
If you set your temp directories to be TEMP - C:\TEMP, TMP - C:\TMP in CONTROL PANEL -> SYSTEM -> ADVANCED -> ENVIRONMENT VARIABLES
then this gets around this issue and the error will disappear.
I had to set up a test Windows 2003 server last nite, and it fought me for - well, too long.
I was getting this error confi file error, tried a lot of what I found here on BOB, no luck. I could see the errors in the log, was not finding the file, and I noticed the server name in the path was changed to the filena~1 format.
I tried the enable 8.3 file name suggestions, but that did not get it. I ened up going do VERY short path names, E:\BO6, E:\TCat, etc - that got it. I guess I just bypassed the naming issue completely that way.
Just in case that helps someone,
NOTE: I just notiiced that the file name registry change I made DID reverse itself: NtfsDisable8dot3NameCreation should be set to 0, but it gets reset to 1. No IIS on this server, not sure what’s going on. MSFT, here I come.
Had this error in BO6.5, Windows 2003, Apache/Tomcat
Tried the 8.3 registry change but that didnt work.
Finally renamed the install path to D:_BO and then it worked.
Took me a long time to get it fixed.