Jump to content

Aaron A.

Members
  • Posts

    2
  • Joined

  • Last visited

Posts posted by Aaron A.

  1. I'm trying to migrate my existing repositories from my own server to the cloud, but I'm running into a problem.  On one branch, I get the following error, "The revision 13478 is loaded twice on changeset 430, at '(name_conflict)_HSC.ico' and 'HSC.ico'. Please contact with support." when I try to sync the repositories.  It seems to be a somewhat common problem related to merging with an evil twin or such, but there doesn't seem to be a public solution.  This check-in occurred probably with Plastic 4 and we are using Plastic 9 currently.  I don't really care about this file as it is easily replaced and hasn't ever really changed.  This is also an old changeset, and we'll never go back here again.  I just need the branch to sync for the later changesets.  I've tried to find a workaround, but have thus far been unsuccessful.  Is there a way to fix this changeset so the sync can continue?  Thanks!

  2. 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.

    Z assembly error.png

×
×
  • Create New...