ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Installation >> Updating to 2017.2
http://www.istechforum.com/YaBB.pl?num=1492191871

Message started by cmsk on 04/14/17 at 10:44:31

Title: Updating to 2017.2
Post by cmsk on 04/14/17 at 10:44:31

Forgot how long these updates take -- 5 hours and counting.  FINALLY past the restructuring stage and now it seems like it's hung on 'Comparing' file WCTRSLOD.b.  It's been around 45 min. already.  How long should this take?

Title: Re: Updating to 2017.2
Post by Lynn_Pantic on 04/14/17 at 13:28:58

I am not sure exactly what it is doing in the background at that point but I know it can take a long time.  Be patient.  I had one take 17 hours once.

Title: Re: Updating to 2017.2
Post by cmsk on 04/14/17 at 14:27:40

It finally passed...

Getting the following during the JDBC Setup

Test Settings Attempt -- Fri Apr 14 17:23:57 EDT 2017
----------------------------------------------------------
company = B
serial  = 670179
db host = BFIPDC1
db port = 1583
db name = EVODEFAULT
----------------------------------------------------------
[05:23:57 pm] java.util.concurrent.ExecutionException: java.lang.UnsatisfiedLinkError: com.pervasive.jdbc.common.Utils.getTerminalSessionId()I -- java.lang.UnsatisfiedLinkError: com.pervasive.jdbc.common.Utils.getTerminalSessionId()I
java.util.concurrent.ExecutionException: java.lang.UnsatisfiedLinkError: com.pervasive.jdbc.common.Utils.getTerminalSessionId()I
     at java.util.concurrent.FutureTask.report(Unknown Source)
     at java.util.concurrent.FutureTask.get(Unknown Source)
     at javax.swing.SwingWorker.get(Unknown Source)
     at ui.ProgressFrame$1.done(ProgressFrame.java:103)
     at javax.swing.SwingWorker$5.run(Unknown Source)
     at javax.swing.SwingWorker$DoSubmitAccumulativeRunnable.run(Unknown Source)
     at sun.swing.AccumulativeRunnable.run(Unknown Source)
     at javax.swing.SwingWorker$DoSubmitAccumulativeRunnable.actionPerformed(Unknown Source)
     at javax.swing.Timer.fireActionPerformed(Unknown Source)
     at javax.swing.Timer$DoPostEvent.run(Unknown Source)
     at java.awt.event.InvocationEvent.dispatch(Unknown Source)
     at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
     at java.awt.EventQueue.access$500(Unknown Source)
     at java.awt.EventQueue$3.run(Unknown Source)
     at java.awt.EventQueue$3.run(Unknown Source)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: java.lang.UnsatisfiedLinkError: com.pervasive.jdbc.common.Utils.getTerminalSessionId()I
     at com.pervasive.jdbc.common.Utils.getTerminalSessionId(Native Method)
     at com.pervasive.jdbc.common.Utils.getTerminalSessionId1(Utils.java:8)
     at com.pervasive.jdbc.v2.Connection.appendSessionId(Connection.java:338)
     at com.pervasive.jdbc.v2.Connection.getConnectString(Connection.java:259)
     at com.pervasive.jdbc.v2.Connection.<init>(Connection.java:133)
     at com.pervasive.jdbc.v2.Driver.connect(Driver.java:57)
     at java.sql.DriverManager.getConnection(Unknown Source)
     at java.sql.DriverManager.getConnection(Unknown Source)
     at ui.ProgressFrame$1.doInBackground(ProgressFrame.java:76)
     at javax.swing.SwingWorker$1.call(Unknown Source)
     at java.util.concurrent.FutureTask.run(Unknown Source)
     at javax.swing.SwingWorker.run(Unknown Source)
     at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)
[05:23:57 pm] java.lang.UnsatisfiedLinkError: com.pervasive.jdbc.common.Utils.getTerminalSessionId()I -- com.pervasive.jdbc.common.Utils.getTerminalSessionId()I
java.lang.UnsatisfiedLinkError: com.pervasive.jdbc.common.Utils.getTerminalSessionId()I
     at com.pervasive.jdbc.common.Utils.getTerminalSessionId(Native Method)
     at com.pervasive.jdbc.common.Utils.getTerminalSessionId1(Utils.java:8)
     at com.pervasive.jdbc.v2.Connection.appendSessionId(Connection.java:338)
     at com.pervasive.jdbc.v2.Connection.getConnectString(Connection.java:259)
     at com.pervasive.jdbc.v2.Connection.<init>(Connection.java:133)
     at com.pervasive.jdbc.v2.Driver.connect(Driver.java:57)
     at java.sql.DriverManager.getConnection(Unknown Source)
     at java.sql.DriverManager.getConnection(Unknown Source)
     at ui.ProgressFrame$1.doInBackground(ProgressFrame.java:76)
     at javax.swing.SwingWorker$1.call(Unknown Source)
     at java.util.concurrent.FutureTask.run(Unknown Source)
     at javax.swing.SwingWorker.run(Unknown Source)
     at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)

Title: Re: Updating to 2017.2
Post by Lynn_Pantic on 04/14/17 at 17:12:57

What Pervasive version are you on?  The files listed below in the DBAMFG\LIB folder need to match your Pervasive version.  You can get them from the PVSW\BIN folder.  The error message indicates the file versions do not match.

JPSCS.JAR
PVJDBC2.JAR
PVJDBC2X.JAR

Title: Re: Updating to 2017.2
Post by cmsk on 04/15/17 at 08:42:07

Did that and double checked it.  Copied them over again, same result.

On Pervasive 9.5.

Title: Re: Updating to 2017.2
Post by cmsk on 04/15/17 at 08:44:21

Wait, am I supposed to be taking these files from the PVSW local folder or from the folder on the server?



Never-mind, they seem to be the same version regardless.

Title: Re: Updating to 2017.2
Post by cmsk on 04/15/17 at 09:11:20

I'm guessing that no one can use the system until we rectify this?  Although data seems to be in place.  Hopefully everything is good.  The only issue I seemed to have were btreive errors seemingly tied to the non existent 07 company.

Title: Re: Updating to 2017.2
Post by Lynn_Pantic on 04/15/17 at 13:24:46

The JDBC setup only affects a handful of Evo programs.  Everything else will work fine in both DBA & Evo.

Title: Re: Updating to 2017.2
Post by cmsk on 04/17/17 at 04:23:23

Okay, We'll see how this morning goes.

I assume we should still work to iron out the JDBC setup either way?  I tried going trough the entire setup again -- same results.

Title: Re: Updating to 2017.2
Post by cmsk on 04/17/17 at 07:02:54

Lynn,

Got your reply on the other thread.  Maybe I should just keep it on this thread and I'll remove the other one.  I guess we need to get this JDBC resolved.

I also sent in a request for gold support.  Will need it on this update and also with a major inventory issue we've been having.

ISTech Support Forum » Powered by YaBB 2.1!
YaBB © 2000-2005. All Rights Reserved.