r Rhona
on

 

Hello,

When validating SEND datasets or define files using P21 Community (3.0.0) and CT package 2019-03-29, some of our users get an error on the Validation Summary tab stating 'Incompatible engine used'.  This is wrong, as the engine our software is using has been confirmed as FDA 1903.1, which is what the validator is set for.  Furthermore, switching to an older CT package (such as 2018-12-21) and validating the exact same dataset yields no such error.

What could be causing P21 to be erroneously flagging the engine as incompatible, but only when using the new CT package?

Thanks,

-Rhona

Forums: Troubleshooting and Problems

Philipp
on July 1, 2019

Hi Rhona,

This error usually fires when the user is running a validation with some CT that cannot be found in our server. SEND CT 2019-03-29 should be available for all users logged in with Pinnacle ID. This error might fire if CT is added manually and app is offline (or blocked by firewall) and cannot check the server.

I would ask for some more information to better understand your issue. Could you please tell, are these users logged in with Pinnacle IDs?

Are there any known restrictions for your Internet connection that could prevent the app from getting updates?

Did these users manually add this CT file to config folder or was it downloaded automatically? The correct path for storing SEND CT 2019-03-29 would be following:

C:\Users\{UserName}\Documents\Pinnacle 21 Community\configs\data\CDISC\SEND\2019-03-29

 

Thanks,

Philipp

r Rhona
on July 3, 2019

Hi Phillip,

We are indeed behind a very unforgiving firewall and the CT package was installed manually, although the path you provided is the one we used.

We will attempt to work with our IT department to see if we can allow P21 through.

Thank you!

-Rhona

 

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.