Error install BF v8.0.0.2
We are installing a brand new v8 on a new Windows 2012 server, following this post, but got this error, any idea?
https://jazz.net/forum/questions/175930/how-to-migrate-buildforge-from-v713-to-the-latest-v8002
|
2 answers
It will be helpful if you can copy the error message out of the tiny screenshot for other to see it clearly and completely. I believe you are seeing the same error as reported in this post.
https://jazz.net/forum/questions/119855/unable-to-upgrade-build-forge-to-80-from-7134-1-0010 (The issue went away after a few months without Jérôme knowing exactly what changes on the system made it work). I could also see a couple of more cases reported and the cause did not get identified in either cases. Some possible solutions were suggested though. 1. Add below path to the system environment variable "Path". <Build Forge installation folder>\IBM\Build Forge\Apache\bin Add below path to the system environment variable "OPENSSL_CONF". <Build Forge installation folder>\IBM\Build Forge\Apache\conf\openssl.cnf 2. Modify the openssl.cnf by doing the following 1) Replace all slash(/) with double backslashes (\\). 2) Assign an exact path to the variable "dir" - for example, "dir = C:\\myCA" Comments We are using WAS 8, is it still the same path? \Apache? BTW, we've encountered the DB2 tablespace error in the link and resolved it.
Donald Nong
commented Aug 31 '15, 6:09 a.m.
I think it's the same path. It's where you can find the "openssl" command. It can be
|
You may want to attempt to manually run the openssl command listed in the output to test if the command can complete without issues.
The openssl command should be available under the %BF_HOME%\Manager\install.log file, though the password will be hidden as required. A similar reported issue with this error was resolved by modifying the password to following password rules. You may need to modify your password to use alternate set of characters. Comments
Jirong Hu
commented Sep 02 '15, 8:42 p.m.
Thanks for the info. Looks like for encryption we have to use strong password with Capital, and special keys. We figured it out after multiple attempts. <o:p> </o:p> |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments