Skip to main content
Level 2
January 4, 2023
Solved

Calculation Engine Error

  • January 4, 2023
  • 2 replies
  • 7 views

Is the Lacerte calculation engine down right now for everybody? 

 

The following message is received when trying to open a client:

 

Error while getting Calculation Data from engine  [Client Number]

This topic has been closed for replies.
Best answer by cbs01

We ran the repair overnight and it seems to have addressed this issue...FYI

2 replies

George4Tacks
Level 15
January 5, 2023

First I would simple restart Windows and Lacerte. If still happens and happens for more than one client then go whole hog with https://proconnect.intuit.com/support/en-us/help-article/federal-taxes/error-getting-calculation-data-engine-lacerte/L8FpL8qHn_US_en_US?uid=lcie5fd4

??? is this 2021 and did it happen after this latest update that I have not yet installed???

Answers are easy. Questions are hard!
TomKatAuthor
Level 2
January 5, 2023

It’s 2022 and started after the early December update. 

George4Tacks
Level 15
January 5, 2023

From past experience, I do not do proforma until as late as possible. It is always full of bugs in the beginning. That may be the source of your problems. 

Try the new Lacerte Tool Hub https://proconnect.intuit.com/community/help-articles/help/fix-common-problems-and-errors-with-the-lacerte-tools-hub/00/71892?src=lctoolhub51420

Answers are easy. Questions are hard!
Level 2
January 5, 2023

Same issue here, however only within S-Corp.  KB article suggests repairing the database.  Not sure...

https://proconnect.intuit.com/support/en-us/help-article/federal-taxes/error-getting-calculation-data-engine-lacerte/L8FpL8qHn_US_en_US?uid=lcjmpe2l

 

George4Tacks
Level 15
January 5, 2023

If this is 2022, I would consider deleting all clients and doing the proforma from 2021 again. Backup any 2022 that you have "real" work in, but toss the others. 

I have not yet done proforma, just because of fears like this. 

Answers are easy. Questions are hard!
cbs01Answer
Level 2
January 6, 2023

We ran the repair overnight and it seems to have addressed this issue...FYI