Book a Demo

Author Topic: PCS 4.2 to 5.1.128 upgrade issues  (Read 16767 times)

nilspc

  • EA User
  • **
  • Posts: 29
  • Karma: +1/-0
    • View Profile
PCS 4.2 to 5.1.128 upgrade issues
« on: February 02, 2024, 05:42:02 pm »
Hi,

We use PCS as floating licens server and to get access to the repository. We are running the 32bit version

We are doing a second attempt to upgrade to PCS 5.1.128 and are experience several problems
Day 1 after upgrade everything seemed to work
Day 2 Sparx client loose connection to database end we get the message "No available key for Architect could be found. Enter a key or connect to e new keystore". After trying several times you eventually get a key. There are plenty of empty keys available
Restart of the server late day 2
Day 3 everything seemed to work fine
Day 4 everything seemed to work fine except for one user loosing connection to the database 
Day 5 (today) I again get the message "No key........"

There are no messages in any logs and I'm running the PCS log with trace without seeing anything that can explain the problem

Has anyone seen and solved this ?
We need to roll back to 4.2 (again if we don't solve this soon) and difficult to open a support case without anymore information but will do that to see it there are any explanation to this



/Nils
« Last Edit: February 02, 2024, 06:28:04 pm by nilspc »

nilspc

  • EA User
  • **
  • Posts: 29
  • Karma: +1/-0
    • View Profile
Re: PCS 4.2 to 5.1.128 upgrade issues
« Reply #1 on: February 02, 2024, 06:28:56 pm »
Hi

Had to roll back to 4.2 again
Are there anyone that successfully run PCS 5.1.128 as floating licens server and access to the repository?

/Nils

BobM

  • EA User
  • **
  • Posts: 144
  • Karma: +9/-0
    • View Profile
Re: PCS 4.2 to 5.1.128 upgrade issues
« Reply #2 on: February 05, 2024, 06:56:09 pm »
Are there anyone that successfully run PCS 5.1.128 as floating license server and access to the repository?
Yes, and everything works fine.
From 4.x to 5.x I suggest to do a re-implementation (not an upgrade) following all official Sparx PCS guidelines.
Your database stays the same (although check database drivers: https://sparxsystems.com/enterprise_architect_user_guide/16.0/the_model_repository/pcs-64bit-migration.html)

Please do check if your database schema is up to date as well (there might be an issue there)