The upgrade of the Filenet Content Engine Server component for IBM Connections CR2 on Windows machines failed for two customers now. The command 'update-ce.bat "D:\IBM\WebSphere\AppServer\profiles\Dmgr01" -was.admin.user wasadmin -was.admin.password password -ce.fp.installer.location "D:\INSTALL\CCMFIXCR2\5.2.1-P8CPE-WIN.EXE"' failed always with the message "Error: Please read the log for detail of the problem, it is D:\IBM\Connections\ccm\ccm\ccm\scripts\fn-ce-update.log".

If you look into the mentioned log you see that the deployment of the FileNetEngine application was successful. There is no hint why the procedure failed in the end.

I just ignored the error and went on with the next steps. I did not notice any problems and you will re-deploy a newer version manually as the last step anyway ... On Linux I never noticed that problem, so it seems to be something Windows specific.

By the way: A detailed instruction for upgrading COnnections 5.0 to CR2 can be found here. If you install on Windows make sure that you use a blank as separator instead of "=" (equal sign) for the Filenet upgrade procedures (e.g. use "-was.admin.user wasadmin" instead of "-was.admin.user=wasadmin")


IBM Connections 5.0 CR2: Upgrade of Filenet Content Engine Server fails
Tagged on:

4 thoughts on “IBM Connections 5.0 CR2: Upgrade of Filenet Content Engine Server fails

  • 07.07.2015 at 13:04

    In our case the problem was within the script encoding, if you have password that has certain characters (in our example ! ) it will fail. The problem is that the script password encoding doesn't accept same characters in password as WAS in general and it somehow defaulted using wasadmin account in one part of the script (we were using LDAP account). Sooo, few bugs in the script.

  • 19.10.2015 at 16:40

    This TechNote could show the solution, I have not been able to try it out, yet, though:

  • 27.01.2016 at 14:03

    I can confirm that solves the problem. Just verified.

    Important: After changing /properties/version/installed.xml you have to restart Deployment Manager _before_ you start to run update-ce.


Leave a Reply

Your email address will not be published. Required fields are marked *