RE: FYI: ARERR 91 RPC: Can't decode result - on 9.1.00; - "solved" with workaround; BMC Bug raised; fix ~ 9.5

2018-01-31 Thread Ben Chernys
igned and investigated, times may change. Cheers Ben From: ARSList [mailto:arslist-boun...@arslist.org <mailto:arslist-boun...@arslist.org> ] On Behalf Of LJ LongWing Sent: January-31-18 8:08 AM To: ARSList mailto:arslist@arslist.org> > Subject: Re: FYI: ARERR 91 RPC: Can't decode

Re: FYI: ARERR 91 RPC: Can't decode result - on 9.1.00; - "solved" with workaround; BMC Bug raised; fix ~ 9.5

2018-01-31 Thread LJ LongWing
be fixed in > that release. Once it is assigned and investigated, times may change. > > > > Cheers > > Ben > > > > *From:* ARSList [mailto:arslist-boun...@arslist.org] *On Behalf Of *LJ > LongWing > *Sent:* January-31-18 8:08 AM > *To:* ARSList > *Subject:*

RE: FYI: ARERR 91 RPC: Can't decode result - on 9.1.00; - "solved" with workaround; BMC Bug raised; fix ~ 9.5

2018-01-31 Thread Ben Chernys
assigned and investigated, times may change. Cheers Ben From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of LJ LongWing Sent: January-31-18 8:08 AM To: ARSList Subject: Re: FYI: ARERR 91 RPC: Can't decode result - on 9.1.00; - "solved" with workaround; BMC

Re: FYI: ARERR 91 RPC: Can't decode result - on 9.1.00; - "solved" with workaround; BMC Bug raised; fix ~ 9.5

2018-01-31 Thread LJ LongWing
Ben, Your statement regarding being fixed around '9.5' doesn't make any sense to medid whoever you talked to SAY 9.5 or did they say 'next release', or more likely 'future version'? On Wed, Jan 31, 2018 at 7:59 AM, Ben Chernys < ben.cher...@softwaretoolhouse.com> wrote: > FYI > > > > BMC has