Re: [libRETS-users] librets-users Digest Thu, 08 Aug 2019
Abid Shaik
 | Abid Shaik Sr. Software Engineer, BrightDoor     Schedule Your BrightDoor Demo! We're here to help. |
librets-users Digest Thu, 08 Aug 2019
Table of contents:
* 1 - Re: [libRETS-users] librets.libretsPINVOKE threw an exception. - KCZ
<kcz...@gmail.com>
----------------------------------------------------------------------
Message-ID: <1>
Date: Tue, 6 Aug 2019 11:09:37 -0600
From: KCZ <kcz...@gmail.com>
Subject: Re: [libRETS-users] librets.libretsPINVOKE threw an exception.
Abid,
Im not sure, but I think, you will need to use librets 64bits (no much
details in your email)
was your application running in a different server (32bits)?
your app never ran on your server windows 2016?
On Mon, Aug 5, 2019 at 11:26 AM Abid Shaik <ash...@brightdoor.com> wrote:
> Hello there,
>
> We have been using LibRets .NET library for MLS integration for almost 7-8
> years. Recently we are getting below error pretty frequently. Nothing
> changed in our Implementation. We have not changed business logic related
> to RetsSession in years. We are getting this error on Windows Server 2016.
> Any suggestions or help on this error is greatly appreciated.
>
> Thanks in advance.
>
> The type initializer for 'librets.libretsPINVOKE' threw an exception.
>
> at librets.libretsPINVOKE.new_RetsSession(String jarg1)
> at librets.RetsSession..ctor(String loginUrl)
> at *RetsSession session = new RetsSession(RETSURL);*
>
> The type initializer for 'SWIGExceptionHelper' threw an exception.
>
> at librets.libretsPINVOKE.SWIGExceptionHelper..ctor()
> at librets.libretsPINVOKE..cctor()---
>
>
> [image: BrightDoor] <http://www.brightdoor.com/>
> Abid Shaik
> Sr. Software Engineer, BrightDoor
> p: (800) 894-5982 x731 <800-894-5982> m: (919) 327-7843 <919-327-7843> a:
> 1919 Evans Rd, Cary, NC 27513
> s: www.brightdoor.com e: ash...@brightdoor.com
> [image: Facebook] <https://www.facebook.com/brightdoor> [image: Twitter]
> <https://twitter.com/brightdoor> [image: LinkedIn]
> <https://www.linkedin.com/company/brightdoor-systems-inc-> [image:
> LinkedIn] <https://www.instagram.com/brightdoorsells/> [image: LinkedIn]
> <http://youtube.com/brightdoorsys>
> Schedule Your BrightDoor Demo!
> <sa...@brightdoor.com?subject=BrightDoor%20Demo%20Inquiry&body=Please
%20contact%20me%20to%20schedule%20a%20no-hassle%20demo%20and%20learn%20how
%20BrightDoor%20can%20make%20a%20positive%20impact%20in%20our%20sales
%20%26%20marketing%20efforts.%0A%0AMy%20best%20day%2Ftime%20is%3A%20%0A
%0ARegards%2C%0A%0A> We're
> here to help.
>
>
>
------------------------------
*********************************************
End of librets-users Digest Thu, 08 Aug 2019
Lynn Lahman
I have been sitting on the sidelines reading this email chain since it began but was reluctant in today’s social media environment to voice my thoughts. I had very similar symptoms in a Windows 10/64-bit system more than a year ago. I had discussions with one of the past (and no longer involved) LibRETS developers/maintainers and I even helped support LibRETS maintenance for some time by donating a Visual Studio license for use by the developer. We eventually agreed that a native .Net download mechanism was probably needed for me to get back to reliable operation (since I am strictly a .Net developer). I did that using .Net and an HTTPWebRequest architecture and it has served me well now for over a year.
LibRETS is a remarkable tool and has been for a long time, but I fear that (in the Windows/.Net world) it is reaching the end of life. Please, I’m not saying this as criticism to NAR, the past (or current) developers, current users, etc. and I’m definitely not saying it so I end up having tens or hundreds of people sending me unfriendly emails – please. I’ve just had no reliability issues since moving away from it to a native .Net solution.
I wish you the best and do hope you find a solution.
Lynn Lahman