Troubleshooting and Problems

With version 2.2.0 I was able to unzip the folders in a directory of my choosing.  For many years I have kept all of these files together in one place.  Now, the files always go to:

C:\Users\me\aplace\Documents\Pinnacle 21 Community <=bad place

but I really want it to go to:

C:\Users\me\aplace\Documents\_CDISC\Validators\Pinnacle 21 Community  <=good place

Whenever I launch Pinnacle 21 and start a validation, it recreates the Pinnacle 21 Community folder in the bad place instead of my preferred good place.

How can I change the path?

Hi,

I am seeing something very strange when opening P21 from a shared network drive. Pinnacle 21 Community 3.0.0 has been installed on a shared network drive.

        \\<server name>\<folder name>\Pinnacle 21

Now imagine the server is called "ABC01" and the folder is called "MyFolder"

        \\ABC01\MyFolder\Pinnacle 21

Of course we assign a "drive letter" to this shared network drive, e.g. "Q".

        Q:\Pinnacle 21

Hi Pinnacle 21 team,

Thank you for releasing the new version, it looks amazing.

One issue I faced while creating an account. When I tried to use my gmail account (x.x.x@gmail.com)  I got the following message: "Invalid email address, please use another."

Does it mean that gmail addresses cannot be used to create Pinnacle IDs?

Thank you.

Hi,

We have recently implemented Pinnacle21 community edition version 3.0.0, and from the looks of it the way external dictionaries are handled has changed, previous for the Controlled Terminology documents and MedDRA dictionaries are handled a user would manually add the files to the folders. For example in 2.2.0 the following paths would update the drop down-lists within the application, e.g.

...\components\config\data\CDISC\SDTM
...\components\config\data\CDISC\SEND
...\components\config\data\CDISC\ADaM
...\components\config\data\MedDRA

Hello,

During testing, it was determined that the p21 (Community 2.20) does not produce FDAN340 or FDAN341 warnings when non-CT terms are used for controlled TSPARM values. Could someone please confirm that this is the correct system functionality and not a result of a local config error?

Thanks in advance,

Brian

Edit - should mention this was SEND validation only

When will the Sept 28 2018 CT files be made available for download on the pinnacle site.  There seems to be a slight difference between the Pinnacle posted CT files and those available on the NCI website here.  

https://evs.nci.nih.gov/ftp1/CDISC/SEND/Archive/

Thank you very much.

Dear, Pinnacle 21 staff

We use Pinnacle 21 community v2.1.3.

Pinnacle 21’s start-up time have varied depending on the day since our company’s security policy changed this spring.

Hi,

I was validating some SDTM domains, and noticed some QSTESTCDs that were used, but do NOT belong to the codelist.  In this case, the QSCAT = "C-SSRS SCREENING" and the QSTESTCD = "CSS0901B"...which is not correct.  I was confused since Pinnacle did not raise an error here, based on CT = 2017-12-22.

As a test, I ran these data against the 2015-09-25 CT (when the QS-FT was a separate file), and Pinnacle did give me the CT2004 error.  

I'm using P21 Version 2.2.0 on Windows version 10 and created my Define Specification in Excel 2013.

I select the options to generate my DEFINE.XML and everything seems to work fine, I see the option to open the Define appear but then before I get a chance to open or save my Define, the Window 'Oh uh a serious error has occurred appears'.

I attempted this about 10 times and the error occurred at the same time.

Interestingly a fellow worker successfully generated a Define using the same software and the same input Excel spreadsheet.

I'm trying to build Pinnacle21 from the source code available at:  https://bitbucket.org/opencdisc/

I'm not having any success.  I've tried following the directions available in the README.md file in the desktop folder but I'm still having problems.  The build process is failing in a couple places but the parts that I'm not sure how to resolve are:

In the data-converter pom.xml: