Troubleshooting and Problems

I notice that you no longer select the MedDRA version from the GUI, so it must be using the define.  I was checking my SDTM datasets and my define together.  I had forgotten that I needed to provide the .asc files for it to check against.  So I got notices like "...\opencdisc-validator\config/data/MedDRA/12.1/pt.asc is missing or lacks necessary variables and cannot be used for this cross-dataset validation", that correctly identify the version of MedDRA.  I created the 12.1 directory and put the .asc files there.  Now I get notices like "...\opencdisc-validator\con

I'm running OpenCDISC via a BAT file on our compute cluster (OpenCDISC version 1.3, validating define.xml).  One of the nodes on the cluster shows the following java -version output:

java version "1.5.0_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode, sharing)

Another node shows:

Hi,

I am getting a message that a serious error has occurred when running the validator. The technical information is as follows. Any feedback would be appreciated.

Thanks,

Bob

--------- System Information ---------
 Version: 1.4
     JRE: 1.6.0_17
      OS: Windows 7 6.1 x86
--------------------------------------

Hi,

There appears to be a blank space (between a '-' and Original) in label for PCORNRLO/PCORNRHI in the configuration file (config-sdtm-3.1.3.xml), opencdsic v1.4.1

def:Label="Normal Range Upper Limit- Original Units"

Wheareas in SDTM Model v1.3 there is no space

--ORNRLO: Normal Range Lower Limit-Original Units

--ORNRHI: Normal Range Upper Limit-Original Units

Check fired

PC Domain: SD0063A   SDTM/dataset variable label mismatch.

Thank you.

 

 

When running OpenCDISC on a network shared drive I get the SKIP_SD0008 error even though the pt.asc is available in the specified location and I get the SKIP_CT0018 error even though the SDTM Terminology.txt file is in the specified location. When I run OpenCDISC on my hard drive I do not get these errors.  The messages accompanying these errors is as follows:

Hi,

 

Hi,

I am getting the label mismatch error for variable "PARCAT1N", for label="Parameter Category 1 (N)" for ADLB. The variable PARCAT1 is also properly created with the right label (Parameter Category 1).  Can you please explain?

Thanks,

Zsuzsa 

I've recently installed the OpenCDISC Validator tool (v1.4.1) on a Red Hat Linux server.   The Linux server has Java 1.7.0_25 installed.  Using Exceed, I was able to start the GUI user interface with the command "java -Xms256m -Xmx1024m -jar lib/validator-gui-1.4.1.jar".  I executed a job and generated the report.  I didn't see any messages in the UI.  However, I noticed in the terminal window. where I launched the java command above, 3 warning messages:

I've recently installed the OpenCDISC Validator tool (v1.4.1) on a Linux server.   The Linux server has Java 1.7.0_25 installed.  Using Exceed, I was able to start the user interface with the command "java -Xms256m -Xmx1024m -jar lib/validator-gui-1.4.1.jar".  In the UI, I entered the prompts and started the job.  The job completed, generating the Excel report.  No indications of any errors or problems. 

Why do some .xpt files get flagged as "unrecognized domain"? They were created the same way other ADaM datasets I made and they process OK. For instance: ADSL (subject level .xpt file) processes ok in the validator. but ADAE (adverse event .xpt file) openCDISC validator returns 'unrecognized domain'. Anyone know how to manage this problem?