Level 2

Realm Id

Forum|Forum|1 year ago
January 9, 2025
2 replies
28 views

I have an app that I developed to automate data entry into lacerte, we have been using it since 2019 and i have the Lacerte ODBC drivers to do it. I can push numbers to any year except 2024, i get this message. "Unable to perform authorization check. The LacerteTax application must be setup and have resolved the proper realm id." Lacerte hasn't been able to help me, it has not happened in the last five years, so we are just trying to get to the bottom of it.

T

TGDonovan

Level 3

Did you install the latest driver. I haven't tested, but they released version 1.0.0.473 this week, and I believe you need that.

K

kamprich

Level 3

Hi, I was going to suggest the same things. I was using version 1.0.0.467 of the SDK and I kept on getting "Cannot find encrypt4.dll" (or something like that). I wrote an ODBC program to create a customer questionnaire based on previous year tax returns. I installed the 1.0.0.473 release this morning and all the problems went away and I was able to query thousands of clients and get their data with no problems.

Also I found that they have changed how your access Series = 1 info. The codes have changed and I only found this by using the ODBC interface with Excel. I had to change the query:

T

TGDonovan

Level 3

I would like to know more about "Also I found that they have changed how your access Series = 1 info. The codes have changed and I only found this by using the ODBC interface with Excel. I had to change the query: "

I am getting a Unhandled managed exception now that I hadn't been getting in the past when running an ODBC query against Data1-Client.

R

royd

Level 3

@FordCPA
I experienced the same issue just now. My app was able to access 2023 and 2025 but got that same error as you for 2024. Turns out that my laptop version of 2024 Lacerte was behind the one on the network. I discovered this by trying to login to Lacerte 2024 directly. Once I updated my laptop version, the error went away.

Though this reply is more than a year after your question, posting this here to help the next person who runs into this issue.

Sign up

Login with SSO

Let's get you signed in

Login with SSO