I'm just guessing here, but maybe the DAS Config model hasn't been
regenerated with the latest SDO. There have been some significant changes
in SDO in the last couple of months, so downstream models definitely need
to be regenerated to work with the latest runtime.
Frank.
Marilene Noronha
After an offline chat with Marilene, we found that this problem was being
caused when the sure-fire tries to run the das tests and the JDK (in this
case IBM JDK) is installed in a folder with spaces on the name
(e.gC:\Program Files). Moving the JDK to a more standard folder name
(without
spaces)
