Process flows pulling up incorrectly after update – Adeptia Help

Situation:

All I see on the process flow is a green start event and red end event. There is an error. This is the message box that pops up:

and here is the details about the exception:

com.adeptia.indigo.transaction.IndigoTransaction; local class incompatible: stream classdesc serialVersionUID = 873405335548448526, local class serialVersionUID = -40496751949340404
java.io.ObjectStreamClass.initNonProxy(Unknown Source)
java.io.ObjectStreamClass.initNonProxy(Unknown Source)
java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
java.io.ObjectInputStream.readClassDesc(Unknown Source)
java.io.ObjectInputStream.readClassDesc(Unknown Source)
java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)....

We can run the flows, it appears. However, when looking into the repository, this is the error received:

Here are the details:

java.lang.NoClassDefFoundError: com/adeptia/indigo/repository/FsRepository
                at org.apache.jsp.transactionrepository$jsp._jspService(transactionrepository$jsp.java:186)
                at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
                at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
                at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:565)
                at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:479)
                at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
                at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:499)
                at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
                at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1031)....

Cause: The Adeptia services may have not been stopped completely before the upgrade was initiated.

Solution:

1) Stop the Adeptia Services
2) Identifying any running java services associated with Adeptia

- In Linux, you can use the command

ps aux | grep java

- In Windows, you can go to the Task Manager > Processes tab.

3) Killing those processes
4) Start the Adeptia Services