Validation aborted, 0 messages were generated, 0 checks were performed

a ARLIX

on December 9, 2015

I have downloaded the "Pinnacle 21 Community 2.1.0" for Windows and used "Validator" for SDTM datasets with XPT files.

Previoulsy I used "Open CDISC Community 2.0.2" without any problems.

That said "validation complete, 0 messages were generated, 0 checks were performed".

In the report excel file, Reason for Un processed Souces is "Validation Aborted".

Can somebody help me to troubleshoot the problem or provide the steps to resolve this issue?

Find attached the logs and report file.

Thanks in advance.

Forums: Troubleshooting and Problems

k Kentaro

on December 11, 2015

Hi, SophieAr

I am troubled with the same error, too.

As far as I searched, probably the error is caused when TS domain is included.

Regards,

Ken

a ARLIX

on December 11, 2015

Hi Ken, Thanks for your

Hi Ken,

Thanks for your comment.

After testing on my side, effectively when TS is not included, there is no error. It is very strange.

I hope this bug will be fix asap.

Regards,

Sophie

m Michael

on December 11, 2015

Logs and data requested to diagnose the issue

Can you both send me your data zipped up so i can try to reproduce it ? A third person reported this and i was not able to reproduce it. Also, please send me your 2 log files found in <pinnacle21 community>/components/logs.

I can respond this afternoon if i get the data soon.

t Tim

on December 18, 2015

Hi Did you discover the

Did you discover the reason for this?

The same is happening to me. The log file includes:

2015-12-18 14:19:30,628 |ERROR |ConfigurationManager.java : 386 |Rule creation failed for an instance of SD1215 in domain TS

(which concerns AGEMAX). There is then a stack overflow in Java and the validation is aborted.

I can remove TS but it would be good to know why this is happening. The value of TSVAL is P18Y

Thanks

m Michael

on December 18, 2015

SD1215,SD1217,SD1219 TS rules

We are aware of this issue and are looking into fixing it. It seems to only occur mostly for Windows 32 bit machines with can only allow at max of 1.5 GB of memory to the Validator java process. It may also occur on 64 bit matchines if you provide too little memory to the validator. Try increasing your memory to see if it resolve the issue.

For a quick and guarunteed solution, simply disable these rules by going to components/config/SDTM<version>.xml, search for these and change Yes to No. Rerun and everything will work.

<val:ValidationRuleRef RuleID="SD1215" Active="Yes"/>

<val:ValidationRuleRef RuleID="SD1217" Active="Yes"/>

<val:ValidationRuleRef RuleID="SD1219" Active="Yes"/>

a ARLIX

on December 18, 2015