Troubleshooting and Problems

Using OpenCDISC 1.4 and config-sdtm-3.1.3, there is a typo in the variable label for MHPRESP.  It is "Medical History Event Pre- Specified" but it should be "Medical History Event Pre-Specified".

Hi , We have opencdisc on a shared computer (win xp) and i am able to access and run it without any issues. But one of my colleague recieved this error msg. Ofcourse validator-gui-1.4.jar file is present in the lib folder. Anyway we can resolve it.

Using OpenCDISC 1.4 and config-sdtm-3.1.3, the order of the variables for the TA domain is not as indicated in the SDTMIG:

The order in OpenCDISC is DOMAIN, STUDYID, ARMCD, ARM, ELEMENT, ETCD, EPOCH, TAETORD, TABRANCH, and TATRANS

The order in the SDTMIG 3.1.3 is STUDYID, DOMAIN, ARMCD, ARM, TAETORD, ETCD, ELEMENT, TABRANCH, TATRANS, AND EPOCH

Using OpenCDISC 1.4 and config-sdtm-3.1.3, there is a typo in the variable label for ACTARM.  It is "Description of Actual Ar", but it should be "Description of Actual Arm".

Hi,

I was trying to open cdisc validator on several analysis datasets and I am getting following error. Could anyone please help me? 

To help us debug this exception, please provide the data below

--------- System Information ---------

 Version: 1.4

     JRE: 1.5.0_06

      OS: Windows 2003 5.2 x86

--------------------------------------

java.lang.UnsupportedClassVersionError: Bad version number in .class file

Using OpenCDISC 1.4, config-sdtm-3.1.3, and CDISC CT 2013-04-12, the following error is generated when the following timing variables are added to the SDTM DM domain:

Using OpenCDISC 1.4, config-sdtm-3.1.3, and CDISC CT 2013-04-12, the following CT errors are generated when the value  “MULTIPLE” exists as a value for the following non-result qualifier variables:

Using OpenCDISC 1.4, config-sdtm-3.1.3, and CDISC CT 2013-04-12, the following CT errors are generated when the value “<domain prefix>ALL” exist as a value of --TESTCD:

Using OpenCDISC 1.4, config-sdtm-3.1.3, and CDISC CT 2013-04-12, the following 2 errors are generated when system organ classes in the data are in sentence case as they exist in the MedDRA dictionary:

Hi there,

Just installed v1.4 on our UNIX Solaris box and I'm runnig into some issues - see below.

This happened when validating SDTM Data regardless of the Configuration version used.

I've confirmed that this issue is not encountered within version 1.3.

Any help/guidance to resolve this would be greatly appreciated.

Stephane

==================================================

To help us debug this exception, please provide the data below