Troubleshooting and Problems

Description

When things just don't seem to work

June 10, 2020

Hi all,

I saw in that we can run CLI without having Java 8 installed (https://www.pinnacle21.com/projects/validator/community-cli):

"If you don't have Java installed on your Windows PC, you can use Java 8 that comes pre-packaged with Community. Add the following path to your PATH system variable: C:\Users\{username}\AppData\Local\Programs\pinnacle21-community\resources\app.asar.unpacked\components\java64\bin"

Read More
June 8, 2020

Dear all, 

It seems there is quite a different xml structure when comparing controlled terminology files from the Pinnacle 21 community folder (C:\Users\user_name\Documents\Pinnacle 21 Community\configs\data\CDISC) versus those released by CDISC (available at https://www.cancer.gov/research/resources/terminology/cdisc).

Is Pinnacle doing modifications to get the community software to handle the files?

Why aren't the original CT files used? 

Kind regards,
Jeroen 

Read More
May 19, 2020

Hello,

When will the latest controlled terminology, from 8-May-2020, be added to P21 community (this was an interim release to incorporate new COVID-19 terminology)?  One of the features of the latest community version is that controlled terminology is auto-updated.  From what I could find on your site this should happen within 5 days of the release.

Thanks,

Melinda

Read More
May 18, 2020

Dear P21,

we observed, that P21 reports generated from P21 Community 3.0.2 and 2.2.0 seem to have a limit, to the rows displayed, of 1000 within the details view for a given category of the issue summary.

I have attached two sceenshots to illustrate the problem.

e.g. according to the issue summary, we would expect to find 36657 rows for source=EG and and Pinnacle21 ID = SD1117, however only 1000 rows match the respective filter criteria within the details tab.

Is this a know limitiation of P21 Community ?

Many thanks,
Stefan

 

Read More
May 1, 2020

Hello,

Normally CT packages are located in the P21 Community directory installed in the user's Documents folder.

For the newest CT package (2020-03-27) this does not appear to be the case.

Could you please let me know where this new package has been installed for P21 3.0.2?

We have a user for whom P21 simply refuses to update itself, and we'd like to provide them with the new CT package manually.

Thank you!

-Rhona

Read More
April 23, 2020

When validating using the engine 1903.1 on controlled terminology older than 2019-12-20 I get the "Incompatible engine used" error.  When using the last two releases of the controlled terminology I am getting no such error.  Can you please help resolve this for me.  Is it a IT issue blocking something, or a corrupt controlled terminology file?  I am using Pinnacle v3.0.2 on a windows PC that appears to have automatically updated the controlled terminology.

 

Read More
April 23, 2020

Dear Pinnacle21,

due to some internal network configuration, Pinnacle21 version 3 has no internet access in order to authenticate the user. Is there any option to start the application and use it without any user login .
 

Many thanks in advance!

Read More
April 6, 2020

Hi,

"UTF-8" is an appropriate encoding for five MedDRA dictionary files - pt.asc, soc.asc, llt.asc, hlt.asc and hlgt.asc to install into Pinnacle Community?

I cannot find this information in below.

https://www.pinnacle21.com/projects/validator/configuring-meddra

Kind regards,

Read More
April 2, 2020

I have produced the Define Spec from my XPT files.

In my XPT files the variable VISIT is a length of $40 in all files and all my XPT files are empty shells so there is no data to impact the length.

However when the Define Spec is generate using the CLI the length is changed to 45, why is this ?

Read More
Subscribe to Troubleshooting and Problems

Want a demo?

Let’s Talk.

We're eager to share and ready to listen.

Cookie Policy

Pinnacle 21 uses cookies to make our site easier for you to use. By continuing to use this website, you agree to our use of cookies. For more info visit our Privacy Policy.