IBM Support

XDMS 7.0 build date causes WAS UPDI Installer to fail

Technote (troubleshooting)


IBM WebSphere XML Document Management Server (XDMS) 7.0, 7.0 ifix 4 and 7.0 ifix 5 contain build dates with an invalid format. The bad build date causes newer versions of the IBM WebSphere Application Server (WAS) Update Installer (UPDI) to fail and prevent updates from being installed.


When using the WAS UPDI to install an ifix or fixpack, the following error can be seen in the updatetrace.log.

2012.05.02 16:59:18.522 GMT W -1 Unparseable date: "2011-07-14.16:30"
2012.05.02 16:59:18.522 GMT java.text.ParseException: Unparseable date: "2011-07-14.16:30"
at java.text.DateFormat.parse(
at com.installshield.wizard.StandardWizardListener.execute(
at com.installshield.wizard.StandardWizardListener.currentBeanChanged(
at com.installshield.wizard.Wizard$


The bad build date format contained in the XDMS.product and XDMS.component files causes the WAS UPDI to fail and exit. With WAS UPDI and older versions, this error was ignored and the installer would proceed with the updates. The behavior was changed between WAS UPDI and resulting in a failure.

Resolving the problem

To resolve the issue, find the XDMS.product and XDMS.component files. They should be located in <was_home>/properties/version directory. Once the files have been located do the following.

1. Backup both XDMS.product and XDMS.component files

2. Edit each file and find the build date Ex: build-date="2011-07-14.16:30"

3. Change the build-date to "07/14/11"

4. Save and exit the file

5. Retry installation of the update

Product Alias/Synonym


Document information

More support for: WebSphere XML Document Management Server

Software version: 7.0

Operating system(s): AIX, Linux

Reference #: 1596296

Modified date: 29 May 2012

Translate this page: