Building Connections this week and troubleshooting some errors reminded me to share the process I have adopted when dealing with IBM error messages – which is to treat them as hints that can set you on the right path but also send you badly down the wrong one.
Installing Connections itself via Installation Manager. One of steps during the install requires you to specify the DB2 server, the database names and credentials to connect to them. I click validate and it fails with error CLFRP0030E and launch error!. That points to this technote which says I left a space after the hostname for the DB2 server.
I absolutely didn’t leave a space and didn’t copy/paste. Just in case (and working on the assumption that it’s always me and not the product) I cleared it all and typed carefully again. I confirmed the hostname was correct and could be reached. I also relaunched Installation Manager and started from the beginning. No luck.
It’s at this point I have to accept the error is referring to something else and that’s all the information I’m going to get from Installation Manager. So now I move to asking myself “what if I saw no error but it just failed to connect”. Well the first answer to that is to check if the connection details, hostname, credentials etc actually work at all. Having confirmed the hostname and ports (there were no firewalls turned on or virus software), I logged into the DB2 server and checked the LCUSER account. Locked out. I unlocked the account and the install then completed.
The test server in this environment is one box with everything DB2, TDI and all the applications on it. My base WebSphere install was WAS 8.5.5 FP10 since Connections System Requirements for WebSphere 8.5.5 says FP8 and higher and I wanted to test that out. Everything installed fine right up to when I went to install Connections Surveys. That’s when I hit a 2 day brick wall. Installation Manager couldn’t connect to the Deployment manager despite it being on the same server.
Well that’s odd. Deployment manager is running. The hostname resolves. The port is listening. I try to find out what the system requirements are for Connections Surveys but for 2 days last week and through the weekend the IBM system requirements pages for Survey were down. I’m stubborn so I won’t let it go. Even the Forms Experience Builder requirements for earlier versions were down. So eventually I had to leave it and move onto the production build. The work needs completing and I was suspicious that the issue might have been installing everything on one server.
I build production across 4 servers and this time I stick with WebSphere 8.5.5 FP8 just in case. When I get to the Surveys install it goes without a hitch. So back to the test server I go. Roll back Websphere to 184.108.40.206 and then forwards to FP8 (thank you Installation Manager!). Surprise surprise Surveys installed perfectly.
So. Not an issue connecting to deployment manager or port or the server running but instead “Connections Surveys cannot install onto WebSphere 220.127.116.11 at all.