Overview | Releases | Download | Docs | Links | Help | RecentChanges

ApplicationParametersInvalid

When you get ApplicationParametersInvalid or Application Parameters Invalid or Applications Parameter Invalid

this does NOT mean that you have a problem with any of the Applications or any of their parameters!

What it means is that EITHER the one so-called "Tag" that tells the online software which verstion (i.e. CMTCONFIG) is not saying something like "i686-rh73-gcc32-opt" OR you just messed up your config files somewhere else ... but it is hard to say and could be anywhere.

Usually it is the former.

The typical solution is as follows.

Look in

  config/databases/DaqSoftware.data.xml

look for the Tag line buried in the following:

 <obj class="SW_Repository" id="SctDaq">
  <attr name="Name" type="string">"SctDaq"</attr>
  <attr name="InstallationPath" type="string">"${SCT_DAQ_ROOT}/installed"</attr>
  <rel name="SW_Objects" num="9">
   "Binary" "CalibrationController"
   "Binary" "AnalysisService"
   "Binary" "FittingService"
   "Binary" "SctApiServer"
   "Binary" "config_server"
   "Binary" "ArchivingService"
   "Binary" "DSctApiServer"
   "Binary" "SctTest"
   "Binary" "SctHighLevelTest"
  </rel>
  <rel name="Tags" num="1">
   "Tag" "i686-rh73-gcc32-dbg"
  </rel>
  <rel name="Uses" num="0"></rel>
 </obj>

and MAKE SURE THAT the tag specified (in the above example it is "i686-rh73-gcc32-dbg") matches what you have in your $CMTCONFIG variable.

Unfortunately you cannot actually make it "$CMTCONFIG" so far as we know.

For good measure, go to $SCT_DAQ_ROOT/installed/ and delete any directories corresponding to CMTCONFIG values you don't think you are using!

Chris