catastrophic failure
LacerteWhen I try to print the 2011 return, error message about catastrophic failure. I can print a specific form but not the whole return.
When I try to print the 2011 return, error message about catastrophic failure. I can print a specific form but not the whole return.


Is it a really, really big return? We've got one that takes about 2 minutes to calculate, and is iffy to print - same catastrophic failure message.
Turning off antivirus / antispyware helps. Unmarking the return as an e-file return helps. (Disabling e-file error checking might help; I haven't tried it.) Printing from the client list, not from forms, helps.

Lacerte does state minimum requirements for the memory on printers to use with the programs. If your printer is close to that "minimum", perhaps that is an issue. Just info for possible future printer purchases....
For our return with this problem, it doesn't get as far as spooling to the printer, and you get the same error printing to PDF. Tech support showed us how to increase the allocated virtual memory (because one of the long string of errors had to do with insufficient virtual memory), but that doesn't resolve the problem.
Big return breaks a lot of things. :)
Knock on wood - I haven't had the problem, yet. My biggest return (in terms of paper generated) is yet to come. But I'll call you when/if I do :-)
I am curious about your machine & printer. The one computer that seems to be having this issue suddenly (not earlier this year) is a 64 bit Win7. We use HP printers. Can print to local one or one of the network printers and still erroring.

There are various help topics if you enter MANapier's error in the Ask Lacerte bos in the program; Click here
I looked through these topics and none seem to answer what to do for this error. Repair the client database may do something, but other computers in office are not having any problems. We all access the same files.
We also experienced the same problem. I've been suporting Lacerte for over 15 years. The following fix works for us whenever Lacrete has a catastrophic error:
On the machine with the problem: