Cause of frequent "broken" data files in Lacerte 2024? (Not seen before in 20 years using Lacerte)

[KTinFranklin]

We are experiencing random data corruption that causes all detail to disappear in a given client, and it's happening frequently. Usually, we can restore the client by renaming the existing .id4 file and replacing it with a prior version, although we don't always realize it's broken until it's too late to use Lacerte's 5 day running backup.  Yesterday, the partner was in the client making changes (so it was fine at that point), and when he went to view it in Forms, all the detail was gone. 

It happens in different tax type modules, so far only in the 2024 program. 

We've never had this happen in many years of using Lacerte.  We're on a network setup. Some of our staff feel sure it only happens right after a Lacerte update, and that has definitely been the case in some instances. 

I have spoken with Lacerte support several times to no avail (it's not a known issue), and our contracted IT group has tried everything they can think of over several weeks, including having Lacerte whitelisted. 

I stumbled on your group while searching the site for answers and thought your group might have the rare combination of insights needed for this problem.  I am just a user, not a developer, but perhaps someone could shoot me some ideas to share with our IT people if they go beyond the scope of my understanding.

Thank you!

Frustrated in Tennessee

[KTinFranklin]

Clarification:  This has happened to many different clients, not one client repeatedly.  

[George4Tacks]

Here is another group to join for help like this https://groups.io/g/ltug

I hope you can get a resolution.

[alecko]

Did you ever get a resolution to this problem?  We are having a similar issue with Lacerte 2024.

[KTinFranklin]

After much digging, our IT contractor found that  although our firewall & security vendor had whitelisted Lacerte, the Lacerte updates were causing it to get blocked again, i.e. not be recognized as the whitelisted entity.  His exact wording was "the updates and an update folder structure got past the whitelisting again. Changes have been made to prevent this now."

That was on July 15th, and we've not seen the issue again, where it had averaged happening at least a couple of times a week before.

Hope this is helpful. It was certainly a frustrating issue!

[KTinFranklin]

Also, the Lacerte backups of the last five days were really helpful when that happened.  You probably are aware of them, but just in case not...It was quicker and easier than having to restore files from the entire server backup, when we caught the issue in time, and MUCH better than having to reinput the data if the CPA had already input a lot!