DTU startup fails after Gen 8.6 PTF custom install package

Products

Gen Gen - Workstation Toolset

Issue/Introduction

After recently installing the Gen 8.6 software with a custom installer package that also includes PTFs i.e. Gen 8.6.3 Consolidation PTF WKS86300 and some later PTFs, some users are not able to start the Diagram Trace Utility.
On machines where the Gen 8.5 was not previously installed, the DTU starts OK
However, where Gen8.5 was previously installed it gives this error:
An error has occurred. See the log file C:\Users\userid\AppData\Local\CA\Gen 8.6\cfg\DiagramTrace\workspace\.metadata\.log

The Knowledge Article Gen DTU fails start (Could not resolve org.eclipse.ant.core) describes this error.
There are many older Eclipse jar files in the directory "%Gen86%\Gen\dt\plugins".
Have tried to remove all the older 2016 files to make it match only the files present in a working machine but the application does not start and, now, no error is displayed.
The current .log file from above message shows this latest message sequence:
===
!ENTRY org.eclipse.e4.ui.workbench 4 0 2023-07-27 13:47:57.666
!MESSAGE Unable to create class 'org.eclipse.e4.ui.internal.workbench.addons.CommandProcessingAddon' from bundle '95'
!STACK 0
org.eclipse.e4.core.di.InjectionException: Unable to process "CommandProcessingAddon.broker": no actual value was found for the argument "IEventBroker".
...
!ENTRY org.eclipse.ui 4 0 2023-07-27 13:47:57.799
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.NullPointerException
at org.eclipse.ui.internal.services.EvaluationService$1.changed(EvaluationService.java:84)
...
!ENTRY org.eclipse.ui 4 0 2023-07-27 13:47:57.800
!MESSAGE Error occurred during status handling
!STACK 0
java.lang.NullPointerException
at org.eclipse.ui.internal.statushandlers.StatusHandlerRegistry.<init>(StatusHandlerRegistry.java:74)
===

Environment

Release : 8.63

Resolution

1. The Gen 8.6.3 Consolidation PTF WKS86300/LU06327 makes 2 updates for the DTU under directory "%Gen86%\Gen\dt" during its post-processing steps using file "DTU-8.6.3-post-procedure.bat":
a. For the Eclipse 3.2 to 4.9 build update, it completely moves/backs up the directory "%Gen86%\Gen\dt" and replaces it with the contents of a file DiagramTrace.zip (part of the PTF). That zip file contains files dated October 2019 and because of the complete directory move, no files dated 2016 should remain. (That change was originally provided in PTF RTN86203/SS10543)
b. A later security update originally provided in PTF RTN86214/LU00601 replaces 2 jar files in the directory "%Gen86%\Gen\dt\plugins":
com.ca.gen.diagramtrace.core_8.6.0.jar
com.ca.gen.diagramtrace.ui_8.6.0.jar
Those files are dated April 2021

2. Gen Support suggested these steps to workaround the problem on the non-working machines:
a. Rename/backup the directory "%Gen86%\Gen\dt" and replace it with the same directory from a working machine.
b. Rename directory "C:\Users\USERID\AppData\Local\CA\Gen 8.6\cfg\DiagramTrace" to remove the existing DTU "cache".
c. Retest the DTU.

The above manual workaround was successful.
After some further testing, it was found that the custom Gen 8.6 installer package is not completing the post-processing DTU update step of WKS86300 correctly. Because of the PTF’s size, the installer is using deliverables unpacked prior to installation.
How to fix the custom installer will be investigated separately.

Additional Information

Another customer with a DTU startup problem who was also using a custom PTF install package resulting in old 2016 dated files being left due to a problem with the running of the WKS86300 file "DTU-8.6.3-post-procedure.bat", was receiving these slightly different type of exception messages in the DTU .log file:

===
!SESSION 2023-09-19 17:08:51.298 -----------------------------------------------eclipse.buildId=unknownjava.version=1.8.0_345java.vendor=TemurinBootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_USCommand-line arguments: -os win32 -ws win32 -arch x86
!ENTRY org.eclipse.ant.core 4 0 2023-09-19 17:08:52.331
!MESSAGE FrameworkEvent ERROR
!STACK 0org.osgi.framework.BundleException: Could not resolve module: org.eclipse.ant.core [49] Another singleton bundle selected: osgi.identity; type="osgi.bundle"; version:Version="3.5.200.v20180822-0553"; osgi.identity="org.eclipse.ant.core"; singleton:="true" at org.eclipse.osgi.container.Module.start(Module.java:447) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1685) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1664) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1627) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1558) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:233) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:343)
!ENTRY org.eclipse.core.contenttype 4 0 2023-09-19 17:08:52.333
!MESSAGE FrameworkEvent ERROR
!STACK 0org.osgi.framework.BundleException: Could not resolve module: org.eclipse.core.contenttype [54] Another singleton bundle selected: osgi.identity; type="osgi.bundle"; version:Version="3.7.100.v20180817-1401"; osgi.identity="org.eclipse.core.contenttype"; singleton:="true" at org.eclipse.osgi.container.Module.start(Module.java:447) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1685) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1664) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1627) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1558) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:233) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:343)
!ENTRY org.eclipse.core.expressions 4 0 2023-09-19 17:08:52.333
!MESSAGE FrameworkEvent ERROR
!STACK 0org.osgi.framework.BundleException: Could not resolve module: org.eclipse.core.expressions [60] Another singleton bundle selected: osgi.identity; type="osgi.bundle"; version:Version="3.6.200.v20180817-1401"; osgi.identity="org.eclipse.core.expressions"; singleton:="true" at org.eclipse.osgi.container.Module.start(Module.java:447) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1685) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1664) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1627) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1558) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:233) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:343)
...
===