Author Topic: Getting "INVALID: The specified client configuration could not be found."message  (Read 757 times)

firebird123

  • Newbie
  • *
  • Posts: 3
  • Karma: +0/-0
The Sert controller GUI is showing the "INVALID: The specified client configuration (AMD_xxx_Lin_OJDK11_2) could not be found in the client configuration file." message.  The controller has client configuration up to date. The specified client configuration is the default one detected by the software. Have any one seen this issue before?

GregDarnell

  • Moderator
  • Newbie
  • *****
  • Posts: 16
  • Karma: +0/-0
Hi firebird,

Sorry you are having problems.

I am going to assume the _xxx_ doesn't really say _xxx_ since there is no such configuration.

Are you running a regular "Full Test Suite" run or a "Range Discovery" run?
Are you using what the GUI calls a "local file" rather than the default client-configurations-2.0.xml?
What do the "xi:include" lines in config-all.xml, starting around line 11, say?
Example:
   <suite>
      <definitions>
         <run-id>All SERT worklets combined</run-id>
         
         <xi:include href="client-configurations-2.0.xml"/>
         <xi:include href="custom-configurations.xml"/>
         

firebird123

  • Newbie
  • *
  • Posts: 3
  • Karma: +0/-0
Hi Greg,

Thanks for the understanding

I'm running a "Full Test Suite", but this issue appear in "Range Discovery" run as well

not sure what you mean by local file, basically I downloaded the latest client configuration by using "Download latest with browser"button, saved it as "client-configurations-2_4.xml" on my local desktop and then loaded it one using "load local file" (see image attached)

Below is what in "xi:inlude" info in config-all.xml
         <xi:include href="C:\Users\Administrator\Desktop\Sert2 data\client-configurations-2_4.xml"/>
               <xi:include href="custom-configurations.xml"/>

GregDarnell

  • Moderator
  • Newbie
  • *****
  • Posts: 16
  • Karma: +0/-0
I'm not quite sure what's happening.  It could be a file permissions issue but that's just a wild guess. 

I'd recommend submitting a SERT support ticket at  https://www.spec.org/sert/feedback/issuereport.html
Make sure you attach the output of the collectlogfiles script from the controller system to the ticket; that gives us a large amount of debug information that should help to resolve the issue.

Greg

firebird123

  • Newbie
  • *
  • Posts: 3
  • Karma: +0/-0
Hi Greg,

I figured out that by saving the new client configurations file to the original location as the default one solves the problem. Thanks for the help.

from
  <xi:include href="C:\Users\Administrator\Desktop\Sert2 data\client-configurations-2_4.xml"/>
to
  <xi:include href="C:\Users\Administrator\SERT-2.0.2\client-configurations-2_4.xml"/>