I had marked this unread until I could dig in. A few months ago ARInside started crashing when trying to run it. There were a handful of suspect objects so we just added them to a packing list and set that as the BlackList to get by until we could investigate. With the verbose logging on I was able to look at the last object documented and went into Dev Studio to find the object after that. Sure enough there was an AL that was partially corrupt.
After reselecting the values show above I remove the BlackList from the .ini file and the whole server was documented without error. I suspect this happened around the time we A) renamed the Primary Form to remove the leading '+' from the name and B) converted the forms and AL to Custom. This AL had never been a problem until around that time. Jason On Sun, Nov 16, 2014 at 3:55 PM, Luthgers, John <jl...@gmx.net> wrote: > ** > Hello Rick, > > This is mostly because of incompatibility issues between server- and > client-api-version. The current version of ARInside uses version 8.1 of the > ARAPI. The API failed to loaded the mentioned field from the server, > because the received data is invalid. It would be helpful to know some > version-/database-details of your environment. > > I’ve seen this: > - if you connect to a rather old ARServer version > - or there is some invalid or corrupted meta data in the database > > I can’t guarantee we can find a workaround. What you should do: > > 1) Like John Kenny suggested, try open it in DevStudio/AdminTool. > (Normally you use the same version of DevStudio/AdminTool identical to your > server version and it should work without an error). If this error does > show up as well, it’s probably a meta-data corruption. It’s a little hard > to track down which field property is causing this. > 2) If the error doesn’t show up in DevStudio/AdminTool, there is a chance > to get it working if ARInside is compiled using the same API version of > your server. But I can’t offer this option in case the server-version is > below version 7.0. > > As a final conclusion: this kind of error isn’t fixable easily. But aside > from the field mentioned in the error message, ARInside should generate a > valid documentation for all the other workflow. > > In case option 2) is a viable option and it’s very important for you to > have this field documented correctly, please contact me off-list so I can > try to provide a special build. > > -John- > *From:* Rick Phillips <r...@netfirst.com> > *Sent:* Saturday, November 15, 2014 12:04 AM > *Newsgroups:* gmane.comp.crm.arsystem.general > *To:* arslist@ARSLIST.ORG > *Subject:* ARInside error > > ** Has anyone seen this error with ARInside ARInside-3.1.2.662-win32? I'm > running it for the first time. > > *Schema: OBO:PeopleUserOuterJoin -- Failed to load field 1000000949: > [ARERR 91] RPC call failed* > > > * RPC: Can't decode result* > Thanks, > > Rick > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
