"Z Assembly" Errors After Upgrade

[Aaron A.]

We recently upgraded from Plastic 5.0.44.581 to Plastic 9.0.16.4164 running on Ubuntu, and now get errors when we try to check-in, look at shelved items, double click on a changeset, ...   We are running 10.3.22-MariaDB, which was needed for Plastic 5 to work on Ubuntu 19.04.  Attached is an image of the error received and below is the log from the server.

From plastic.server.log (cleansed slightly to remove usernames and computer names) an attempt to check-in:

2020-04-23 01:50:44,901 00000000-0000-0000-0000-000000000000 root at DESKTOP INFO  Operations - Get info for branch /main/iteration_4 at repository ID 2
2020-04-23 01:50:44,908  root at  INFO  ChannelCall - conn:   177 protocol:plasticproto sec:ssl  recb:     154|rect:   0|sentb:     181|sendt:   0|queuedt:       0|prt:       7|th:   80|dest:   0|mt:       6|sert:   0|zip:   0|cpu:       0|  134.228.27.177|user:xxxxxxxxxxxxxxxx|GetBranchInfoByName
2020-04-23 01:50:44,985  root at  INFO  ChannelCall - conn:   177 protocol:plasticproto sec:ssl  recb:      74|rect:   0|sentb:      37|sendt:   0|queuedt:       0|prt:       1|th:   76|dest:   0|mt:       0|sert:   0|zip:   0|cpu:       0|  134.228.27.177|user:xxxxxxxxxxxxxxxx|GetTriggerList
2020-04-23 01:50:45,076 01e60a66-32f6-40ac-bfd8-dab8543411ff root at Server:server INFO  Transaction - Commit transaction 01e60a66-32f6-40ac-bfd8-dab8543411ff. Transaction time 0 ms
2020-04-23 01:50:45,081 00000000-0000-0000-0000-000000000000 root at DESKTOP ERROR Operations - OnError catching exception [z assembly:<unknown assembly> type:<unknown type> member:(null)] - Plastic server version: 9.0.16.4164
2020-04-23 01:50:45,084  root at  ERROR PlasticProto.ConnectionFromClient - conn  177. Error in ProcessMethodCall for method TryCheckIn. There has been an unexpected error "z assembly:<unknown assembly> type:<unknown type> member:(null)". For more information check the server log.

 

Any help on what might be the cause of this would be greatly appreciated.

[calbzam]

Hi,

- If you are paying customer, could you send us the full server debug log to "support@codicesoftware.com"?

- What is the package you used to upgrade your server? It seems there is a missing library.

- We have already migrated most of our customers to Jet (our file based database). We recommend you to do it as well (even when I'm not sure your error related to your database backend).

https://www.plasticscm.com/documentation/administration/plastic-scm-version-control-administrator-guide#Chapter8:Repositorystorageconfiguration

Regards,

Carlos.