PMDA Legacy (1511.6) via CLI fails

Philipp

on February 13, 2020

P21

Hi Jeroen,  Validation…

Hi Jeroen, 

Validation command itself seems fine. 

Could you please specify what error did you receive? Does it happen with any other engine version? Are you using CLI when connected to the Internet? 

Thanks, 

Philipp

PMDA Legacy (1511.6) via CLI fails

Hi Philipp, 

I just get a pop-up window in windows saying the report (in the provided report location) cannot be found. I guess this is upon trying to open the (non-existing) file. 

In the log, the first ERROR is: [MAIN] ERROR N.B.API.MONITOR.SEGMENT.SEGMENTS - SEGMENTS FAILED

Any idea?

I don't get this with the other engines.  

Kind regards,
Jeroen 

Philipp

on February 18, 2020

P21

Hi Jeroen, The "Segments…

Hi Jeroen,

The "Segments failed" error is non-critical. It is most likely related to some self-signed certificate being rejected. This issue shouldn't hugely affect user experience and block the validation. 

It seems that the actual problem is that you are using define.xml that refers to some standard version not supported by PMDA 1511.6 engine. This engine checks your define.xml MetaDataVersion. It should have correct and supported standard name and version, for example def:StandardName="SDTM-IG" and def: StandardVersion="3.2". SDTM 3.1.1 and older versions aren't supported there.

Thanks,

Philipp

Legacy engine doesn't work via GUI when including a define.xml

Apparently no report is generated either when running the Legacy engine and including a define.xml file via GUI. 

Error code: 56 message: Failed core process.

•  Failed local validation process
•  Could not determine standard for define.xml

So indeed it seems related to define.xml standard. To which define.xml standard are the different engines referring?

Since it's also a problem in GUI, it is probably a more general issue and not quite related to the run via CLI? Can this get corrected by Pinnacle 21? 

Thanks

PMDA legacy engine 1511.6

After some additional testing and reading your reply again: so the PMDA engine 1511.6 is actively checking in the define.xml which MetaDataVersion is indicated there to start validating only if a correct version is used (1.0)? Does it mean this engine is actually doing more that the other engines (1810.3 and 1903.1)?

In fact when trying the legacy engine with a define.xml file included with adjusted MetaDataVersion (1.0) then a report does get generated (both via GUI and CLI).

Still, I'm wondering why the CLI then doesn't run when no define.xml file is included.... any idea?

Thanks, Jeroen

Philipp

on February 19, 2020

P21

Could you please specify…

Could you please specify what are def:StandardName and def:StandardVersion in the define.xml that you use?

Thanks,

Philipp

Philipp

on February 19, 2020

P21

Regarding your question why…

Regarding your question why the CLI doesn't produce the report when no define.xml file is included - if you have define.xml at the same directory provided in --source.sdtm or --source.adam - it will be included in the validation automatically. Therefore it might fail the validation too in this case.

Thanks,

Philipp