Branch Explorer not working - Unexpected Error

[ironbelly]

• Client / Server Version = 6.0.16.866
• DB = Jet
   

Anytime I try to access the branch explorer I see an error box saying " There has been an unexpected error " The method or operation is not implemented". For more information check the server log.

I can create top level and child branches in the Branch section of the client without any issue but as soon as I go into the Branch Explorer that when that error comes up and I cannot see nor do anything.  

Here are the server logs:

***DEBUG LOG***

Quote

 

2017-04-10 17:35:55,722 A-6584    DEBUG Channel-SocketCallback - conn 1914. awaked. total 1862
2017-04-10 17:35:55,722 A-6584    DEBUG WorkerThreadPool - Enqueued new work. Enqueued: 1 Worker threads: 8 (8 free)
2017-04-10 17:35:55,722 A-6584    DEBUG WorkerThreadPool - There are 8 free threads - not starting a new one. Enqueued: 1
2017-04-10 17:35:55,723 W-6338    DEBUG WorkerThreadPool - WorkItem attended in 00:00:00.0002700. Queued 0. Id: 6338
2017-04-10 17:35:55,723 W-6338    DEBUG WorkerThread - WorkerThread.Run: Work retrieved. Id: 6338. 459647 ms
2017-04-10 17:35:55,723 NetworkThread-19    DEBUG Channel-SocketCallback - conn 1914. BeginReceive - setting callback
2017-04-10 17:35:55,723 NetworkThread-19    DEBUG Channel-SocketCallback - conn 1914. BeginReceive - callback set
2017-04-10 17:35:55,723 W-6338 00000000-0000-0000-0000-000000000000 IB_Ryanw IRONBEAST INFO  Operations - Get ReleaseDiagram information for repository 4
2017-04-10 17:35:55,724 W-6338 00000000-0000-0000-0000-000000000000 IB_Ryanw IRONBEAST ERROR Operations - OnError catching exception [The method or operation is not implemented.] - Plastic server version: 6.0.16.866
2017-04-10 17:35:55,724 W-6338 00000000-0000-0000-0000-000000000000 IB_Ryanw IRONBEAST DEBUG Operations - OnError catching exception The method or operation is not implemented.
  at DatalayerFs.DataQuery.Codice.CM.Data.IDataQuery.GetReleaseDiagramInfo (Codice.CM.Common.RepId repId, System.DateTime start, System.DateTime end, System.Int32 stage) [0x00000] in <a4713a7378d04e7782a4b19d0da82221>:0
  at Codice.CM.Server.ItemHandler.GetReleaseDiagramInfo (Codice.CM.Common.RepId repId, System.Int64 utcStartTicks, System.Int64 utcEndTicks, System.Int32 stage) [0x00014] in <9258ea2c68d448da87851ce855e8e624>:0
  at Codice.CM.Server.SecuredItemHandler.GetReleaseDiagramInfo (Codice.CM.Common.RepId repId, System.Int64 utcStartTicks, System.Int64 utcEndTicks, System.Int32 stage) [0x0000a] in <9258ea2c68d448da87851ce855e8e624>:0
  at Codice.CM.Server.TransactionInterceptor.GetReleaseDiagramInfo (Codice.CM.Common.RepId repId, System.Int64 utcStartTicks, System.Int64 utcEndTicks, System.Int32 stage) [0x00032] in <30595ea2c4274709b6f295d0101a779c>:0

2017-04-10 17:35:55,725 W-6338    ERROR ExceptionTracerSink - Dumping in-transit exception:There has been an unexpected error "The method or operation is not implemented.". For more information check the server log.

2017-04-10 17:35:55,725 W-6338    DEBUG ExceptionTracerSink - Dumping in-transit exception:There has been an unexpected error "The method or operation is not implemented.". For more information check the server log.
  at Codice.CM.Server.TransactionInterceptor.GetReleaseDiagramInfo (Codice.CM.Common.RepId repId, System.Int64 utcStartTicks, System.Int64 utcEndTicks, System.Int32 stage) [0x00056] in <30595ea2c4274709b6f295d0101a779c>:0
  at Codice.CM.Server.TriggerInterceptor.GetReleaseDiagramInfo (Codice.CM.Common.RepId repId, System.Int64 utcStartTicks, System.Int64 utcEndTicks, System.Int32 stage) [0x00000] in <b1f7272537604643abcf37098243e6b1>:0
  at (wrapper managed-to-native) System.Runtime.Remoting.RemotingServices:InternalExecute (System.Reflection.MethodBase,object,object[],object[]&)
  at System.Runtime.Remoting.RemotingServices.InternalExecuteMessage (System.MarshalByRefObject target, System.Runtime.Remoting.Messaging.IMethodCallMessage reqMsg) [0x000ca] in <8f2c484307284b51944a1a13a14c0266>:0

2017-04-10 17:35:55,726 W-6338    INFO  ChannelCall - protocol:remoting recb:   794|rect:  0|sentb:  2869|sendt:  0|queuedt:       1|prt:       3|th: 6338|dest:   0|mt:       2|sert:   1|zip:   0|cpu:       0|    70.30.215.67|user::IB_Ryanw|GetReleaseDiagramInfo
2017-04-10 17:35:55,726 W-6338    DEBUG WorkerThread - WorkerThread.Run: Going to GetWork. Id: 6338

 

***ERROR LOG***

Quote

2017-04-10 17:38:06,501 IB_Ryanw IRONBEAST ERROR Operations - OnError catching exception [The method or operation is not implemented.] - Plastic server version: 6.0.16.866
2017-04-10 17:38:06,502   ERROR ExceptionTracerSink - Dumping in-transit exception:There has been an unexpected error "The method or operation is not implemented.". For more information check the server log.

 

[psantosl]

Hi,

 

Looks like you are running a server using Jet, correct?? :-)

 

If so, you need to activate the new network protocol on the client, because Jet uses some optimized queries not compatible with the old ones.

 

Easy:

 

* Create a file plasticpipeprotocol.conf on your client => it can be your client config directory, or where the binaries are (both will do).

* The content will be:

defaultprotocol plasticprotocol

 

And you are done.

 

Now: this will be over as soon as we make the new protocol *official* because auto-detection will do it for you. But... right now you need configuration.

 

Thanks,

 

pablo