Hi Jarl. Worked like a charm. Now to debug...
You have certainly helped me out a few times - I'll buy you a beer or two if we meet some day. Have a nice weekend. with regards, Jonas Stumph Stevnsvig Remedy Developer BEC Phone (+45) 46 38 20 08 Mobile (+45) 61 56 20 08 [email protected] [email protected] -----Oprindelig meddelelse----- Fra: Jarl Grøneng [mailto:[email protected]] Sendt: 23. februar 2010 09:27 Emne: Re: ARERR 91 HI, Rename the arsys_sample.xml file to arsys_api.xml. The file is located here: (depending on your installation) C:\Program Files\BMC Software\ARSystem\DeveloperStudio\plugins\com.bmc.arsys.studio.api_7.5.0 Edit the file like his: <javaapi_config> <catalogFile>arcatalog</catalogFile> <maxProxiesPerServer>10</maxProxiesPerServer> <connectionMaxRetries>0</connectionMaxRetries> <timeLagBetweenRetriesMillSec>1000</timeLagBetweenRetriesMillSec> <toStringStyle>com.bmc.arsys.api.NoPrefixToStringStyle.NO_PREFIX_STYLE</toStringStyle> <stringizeFieldAssignments>false</stringizeFieldAssignments> <stringizeSetIfQualification>false</stringizeSetIfQualification> <apiRecording>24</apiRecording> <jniLoadMode>1</jniLoadMode> </javaapi_config> *Note the <apiRecording>24</apiRecording> section. Restart developer studio. The logfiles gets created here: C:\Program Files\BMC Software\ARSystem\DeveloperStudio Regards, Jarl 2010/2/23 Jonas Stumph Stevnsvig <[email protected]>: > ** > Hi listers. > > I have an ARDBC plugin (java based) which is working fine on most of > our vendor forms. Except one. I have One form, on which I cannot add > extra fields; when I right click and choose Add fileds from > <tablename> I don't get the list of fields, but the following error: > > ERROR (91): RPC call failed; RPC: can't decode result (ARERR 91) > > The AR Error message guide reccomends API logging. But I am getting > the error in the developer studio - not in the User tool. > > I have been able to circumvent the error by duplicating an existing > field, and correcting its data to suit my purposes. > > Have any of you experienced similar errors?` > > > > with regards, > > Jonas Stumph Stevnsvig > Remedy Developer > BEC > Phone (+45) 46 38 20 08 > Mobile (+45) 61 56 20 08 > [email protected] > [email protected] > > > > quote from the AR error message guide: > > 91 > > Error > > RPC call failed. > > AR System clients use the RPC layer to connect to the AR System > server's TCP port. This error > > occurs when an RPC call fails for some reason. Some possible causes of > this error include but are > > not limited to: > > An invalid RPC packet was detected > > ... > > If this is a recurring error, and increasing the file descriptors or > file handles available to the > > AR System server does not resolve the problem, turn on ARAPILOGGING > for the client that > > receives the error to isolate the API call that is failing with ARERR 91. > For information about how > > to configure and use client-side API logging, see the Optimizing and > Troubleshooting Guide. > > A less common cause of this error is running an API program that is > incompatible with the AR > > System server. In this case, recompiling the API program with the same > API version used by the > > AR System server might resolve the error. > > _Platinum Sponsor: [email protected] ARSlist: "Where the > Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
