SAXParseException error when starting rtc 3.0 JTS

This is a new installation of RTC 3.0 iFix1 on Windows. Using the default derby databases and the Tomcat app server. When I start the Jazz Team Server this message is displayed on the console a few seconds after the final server startup message. Any idea what is causing this?
:1505:6: The processing instruction target matching "" is not allowed.
This was in the .log file from tomcat\work\Catalina\localhost\clmhelp\eclipse\workspace\.metadata folder.
!SESSION 2011-08-09 08:02:41.326 -----------------------------------------------
eclipse.buildId=unknown
java.fullversion=J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223ifx-20100511 (JIT enabled)
J9VM - 20100509_57823_lHdSMr
JIT - 20091016_1845ifx7_r8
GC - 20091026_AA
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US

!ENTRY org.eclipse.help.base 4 0 2011-08-09 08:02:41.326
!MESSAGE Internal error while reading TOC contents from remote server
!STACK 0
org.xml.sax.SAXParseException: The processing instruction target matching "" is not allowed.
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at org.eclipse.help.internal.dynamic.DocumentReader.read(DocumentReader.java:56)
at org.eclipse.help.internal.dynamic.DocumentReader.read(DocumentReader.java:44)
at org.eclipse.help.internal.base.remote.RemoteTocParser.parse(RemoteTocParser.java:34)
at org.eclipse.help.internal.base.remote.RemoteTocProvider.getTocContributions(RemoteTocProvider.java:102)
at org.eclipse.help.internal.toc.TocManager.getAndCacheTocContributions(TocManager.java:210)
at org.eclipse.help.internal.toc.TocManager.getTocContributionsForToc(TocManager.java:199)
at org.eclipse.help.internal.toc.TocManager.getRootTocContributions(TocManager.java:306)
at org.eclipse.help.internal.toc.TocManager.getTocs(TocManager.java:68)
at org.eclipse.help.HelpSystem.getTocs(HelpSystem.java:71)
at com.ibm.ccl.ut.help.info.nav.NavElem.getUAElement(NavElem.java:141)
at com.ibm.ccl.ut.help.info.nav.NavElem.<init>(NavElem.java:39)
at com.ibm.ccl.ut.help.info.nav.NavInfoManager.createNavElem(NavInfoManager.java:76)
at com.ibm.ccl.ut.help.info.nav.TocParser.makeElem(TocParser.java:136)
at com.ibm.ccl.ut.help.info.nav.TocParser.startElement(TocParser.java:75)
at com.ibm.ccl.ut.parser.TagParser.processChunk(TagParser.java:69)
at com.ibm.ccl.ut.parser.TagParser.parse(TagParser.java:31)
at com.ibm.ccl.ut.parser.TagAdapter.parse(TagAdapter.java:28)
at com.ibm.ccl.ut.help.info.nav.TocParser.execute(TocParser.java:57)
at com.ibm.ccl.ut.help.info.nav.NavInfoManager.index(NavInfoManager.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at com.ibm.ccl.ut.help.info.IndexThread.run(IndexThread.java:102)

I'm also seeing this error on a windows. This server was working fine but now it wont start. I'm trying to understand what changed - maybe a fixpack was applied? any ideas?

I would suggest to create a work item so that development can have a look.