Jump to content

Search the Community

Showing results for tags 'Error'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Plastic SCM
    • General
    • Installation and configuration
    • Unity 3D
    • Plastic SCM on Mac
    • Plastic SCM on Linux
    • Gluon
    • Git interop
    • Integrations
    • Community Edition
    • Branching and merging
    • Announcements
  • Plastic SCM 4.0 Beta (Closed)
  • Plastic Cloud
    • General
    • Configuration
  • SemanticMerge
    • General
    • License
    • SCM's configuration
    • Share your experience!
    • External Parsers
  • GitJungle
  • Method History for Subversion

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 4 results

  1. Hi everyone! I have been using plastic for 2 weeks without any problem. But, the last time I tried to verify some changes in a project, an error message appeared and the operation was canceled. I have tried all kinds of things, but I have no results. Any help will be appreciated! Greetings, Juan.
  2. Hi, I wanted to recreate a repo using fast-import which I got as a handover from another company. Therefore I installed Plastic locally, run the server and created a repo so I can fast-import the repo we got (via fast-export). I use the command cm fast-import myrepo@localhost:8087 d:\myrepo-export.repo After executing it, it starts to process the changesets but while processing the 39th changeset I get the following error: Processing changeset 39. Processed 36 csets. Elapsed 00:00:01.2660000 Error processing changeset mark 143. Parent cset mark: 89. Parent cset: 20 The changeset '143' could not be imported. Error: There has been an unexpected error "Object reference not set to an instance of an object.". For more information check the server log. Please contact with the support team. author abc <abc> 1509614064 +0300 committer abc <abc> 1509614064 +0300 data 46 from :89 merge :135 And the matching server log: 2019-03-08 11:45:49,021 ERROR Checkin - Checkin changes cannot be processed. Error:Object reference not set to an instance of an object. at Codice.CM.Server.Checkin.CheckinTreeWalker.a(TreeChangedNode A_0) at Codice.CM.Server.Checkin.CheckinTreeWalker.b(TreeChangedNode A_0) at Codice.CM.Server.Checkin.CheckinTreeWalker.a(TreeChangedNode A_0, Int64 A_1) at Codice.CM.Server.Checkin.CheckinTreeWalker.d(TreeNode A_0, TreeChangedNode A_1) at Codice.CM.Server.Checkin.CheckinTreeWalker.b(TreeChangedNode A_0, TreeNode A_1) at Codice.CM.Server.Checkin.CheckinTreeWalker.a(b A_0, py A_1, Queue`1 A_2) at Codice.CM.Server.Checkin.CheckinTreeWalker.b(TreeChangedNode A_0, TreeNode A_1, TreeNode A_2) at Codice.CM.Server.Checkin.CheckinTreeWalker.ProcessChanges(TreeChangedNode changedTree, TreeNode serverTree) at gh.a(TreeChangedNode A_0, TreeNode A_1) at gh.a(TreeChangedNode A_0, TreeNode A_1, Int64& A_2) 2019-03-08 11:45:49,035 ERROR Operations - OnError catching exception [Object reference not set to an instance of an object.] - Plastic server version: 8.0.16.3046 2019-03-08 11:45:49,036 ERROR PlasticProto.ConnectionFromClient - conn 13. Error in ProcessMethodCall for method CheckInChangedTree. There has been an unexpected error "Object reference not set to an instance of an object.". For more information check the server log. I need the data stored in the repo and do not have access to the original one. It looks like, there is an issue with the Plastic software. Is there a chance you can provide a fix for this? Thanks, Lukas
  3. Hi, I'm hoping I can receive some fairly urgent help with this one. I'm having problems syncing to my git repository (where I have paying customers waiting for updates). When I tried to sync this afternoon I received the following error "An error occurred processing your request" but no other information as to what that error might be. I can sync up other plastic repositories to their git equivalents ok. I've taken a look at the plastic log and the only thing that look suspicious is the last line which reads: 2016-06-06 17:41:09,850 (null) NT AUTHORITY\SYSTEM at (null) INFO Channel - Connection 2 from 127.0.0.1 closed I've attached the full log for you to take a look at though. Let me know if you need anything else from me. Thanks, Tom plastic.server.log.txt
  4. I just got the same message as described in this thread: http://www.plasticsc...-wierd-problem/ Here is so more information from what I see on my side: The first issue I encountered was that one of the branches I was pulling in during a sync operation did not "go away" when the sync was done. instead it remained there "available for sync". Details for the sync showed that no change sets / items / anything was actually imported... ( zero on all item types). After a short while I started getting the following message in the sync view pane: "Error: there has been an unexpected error "An item with the same key has already been added". For more information check the server log." when I activated the log on my local server I get the following: 2012-05-21 08:50:29,227 116ef32b-7469-4e50-a216-d2fd871de543 Server:EPELEG7 INFO Transaction - Transaction timeout -> 120000ms 2012-05-21 08:50:43,567 00000000-0000-0000-0000-000000000000 EPELEG7 INFO Operations - Get repository info 1 2012-05-21 08:50:43,626 00000000-0000-0000-0000-000000000000 EPELEG7 INFO Security - ACLReader reading all acls for repository 1. 0 ms 2012-05-21 08:50:43,683 00000000-0000-0000-0000-000000000000 EPELEG7 INFO Security - ACLReader reading all acl entries for repository 1. 63 ms 2012-05-21 08:50:43,724 00000000-0000-0000-0000-000000000000 EPELEG7 INFO Security - ACLReader reading all acl inheritance entries for repository 1. 31 ms 2012-05-21 08:50:43,732 00000000-0000-0000-0000-000000000000 EPELEG7 INFO Security - ACLReader updating ACL cache for repository 1. 15 ms 2012-05-21 08:50:44,390 00000000-0000-0000-0000-000000000000 EPELEG7 ERROR Operations - OnError catching exception An item with the same key has already been added. at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add) at Codice.CM.Server.Replication.ReplicationSynchronizer.b(IList A_0) at Codice.CM.Server.Replication.ReplicationSynchronizer.a(BranchesFilter A_0) at Codice.CM.Server.Replication.ReplicationSynchronizer.GetSynchronizationStatus(BranchesFilter filter) at Codice.CM.Server.ReplicationHandler.GetReplicationSyncStatus(RepositoryInfo repInfo, RepositoryInfo remoteRepInfo, Credentials remoteAuth, BranchesFilter filter) at Codice.CM.Server.SecuredReplicationHandler.GetReplicationSyncStatus(RepositoryInfo repInfo, RepositoryInfo remoteRepInfo, Credentials remoteAuth, BranchesFilter filter) at Codice.CM.Server.TransactionInterceptor.GetReplicationSyncStatus(RepositoryInfo repInfo, RepositoryInfo remoteRepInfo, Credentials remoteAuth, BranchesFilter filter) 2012-05-21 08:50:44,411 ERROR Codice.CM.Server.ExceptionTracerSink - Dumping in-transit exception:There has been an unexpected error "An item with the same key has already been added.". For more information check the server log. at Codice.CM.Server.TransactionInterceptor.GetReplicationSyncStatus(RepositoryInfo repInfo, RepositoryInfo remoteRepInfo, Credentials remoteAuth, BranchesFilter filter) at Codice.CM.Server.TriggerInterceptor.GetReplicationSyncStatus(RepositoryInfo repInfo, RepositoryInfo remoteRepInfo, Credentials remoteAuth, BranchesFilter filter) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext) 2012-05-21 08:51:15,578 INFO Channel - The exception was caught during PlasticTcpClientConnection.ProcessMessages: System.Runtime.Remoting.RemotingException, Tcp transport error., ThId: 14 I also created a replication package of the "problematic" branch mentioned above and imported it into my own server. so now it does show in my branch explorer. S currently I can not sync (nor can my other developer). we have each a local [windows] plastic server we use and we sync to a central [linux] plastic server. The said problematic branch was initially pushed by the other developer to the central server and the above described sync issues started when I tried to pull it to my server. and the "same key" error first showed up at my other developer's machine and then on mine as well. We are using plastic 4.0.237.1 on the linux server and 4.0.237.0 on the windows machines. Any help Is most welcome and required.
×
×
  • Create New...