Lately when I bring up a report in financial reporter and print, whether it's to a printer or a .pdf, FR crashes. It gives me the option to restart or close and I get recovered files (last saved versions) for whatever reports I had open when FR re-opens.

However interestingly enough, if I use statement group print, it all works fine. But sometimes I don't want to print a whole set or setup statement group print for every report I might run one at a time

I am using v9.3A (170625) and going into financial reporter both times, not printing from the ledger menu.

Hi Barb,

We've had a couple of sites report similar behaviour, interestingly starting around the time that this month's Microsoft Windows Updates were installed.

One of these sites sent us the Windows Event Manager log, and the particular error message was connected to this Microsoft link that R&D gave to tech support.

This is all I know about this particular situation. We're keeping our eyes on this error but we currently don't know if the problem is within our control to address it.

Excel Direct also worked for this site, if you need to print a one-off statement (from Excel).

We are having the same issue on our 2012R2 TS. I don't even print. I hit the print button and then cancel the print window and the Financial Reporter crashes and we can only close the program.

This is not new but I haven't had the time to investigate it before and it has not been reported by any of our clients. It happens with GL 9.2B or GL 9.3A. I haven't checked earlier versions.

The link you posted may not apply as our Office works fine and it is from 2010. However, we noticed it in October but we didn't do any Windows updates in October. Our previous Windows update was a the beginning of September. We installed DocStore preview at the end of September.

We just had a site report this to us as well. I haven't been able to collect all the details but they reported exactly the same thing as the original poster and also run the June release GL 9.3A via RDP on server 2012R2.

On a Terminal Server, Adagio is installed as Administrator. If I login as Administrator, it doesn't crash. I think, a more current install may have changed the registry or the location of temp files.

I tested with another profile and it worked properly. Therefore, I thought it was my own registry. Deleted the Financial Reporter entry and it works fine now.
The other user may have never used the Ledger before. Something got corrupted in one of the updates.

Edited:

The other user works. Mine still doesn't. We are both on the same Terminal Server.

I can also confirm that different windows users in same server 2012r2 RDP environment have different outcomes using the same financial statements. Can't say what the key difference is between windows user accounts, but that must be part of the problem.

Not sure why using the statement group print seems to get around the issue but I have confirmed that is a workaround for my client as well.

I too have a client with the same issue. Her profile crashes on print from the Financial Reporter and others do not. 2012r2 RDP environment as well. GL 9.2B (20170320)

Has anyone got any further on this?

I do have the solution if you want to call me. I did a number of changes and I am not sure which one was the one that solved it.
We can try one at the time and know for sure.

Was anyone ever able to isolate what setting(s) were the cause? There seems to be more than infrequent reports of this, and if the solution is a setting in Windows for the workstation or the server, I'm sure the community would benefit from the answer.

In our case, it happened on a RDP server. Deleting the iconcache and the temp files for the user solved our issue. This needs to be done while the user is logged off.

This issue happened for another user in an Windows 8.1 workstation under one user profile, if login with another user, it didn't happen.
The user profile needed to be recreated and the issue was solved.

I have fixed the problem, or should I say an update fixed it. I was also getting an ODBC error when running chksys. I was also unable to install the recent update for DocStore from my computer. It reported the program/a file as in use. I didn't get the details. So I ran the update from another workstation that wasn't having these problems. And after that my ODBC error was gone and I could print from financial reporter again.

This is the error I had before:
========== Crystal Reports System Status ==========
WARNING: Adagio ODBC Component is Version [] but Version [2.1.8.189] is needed by [Adagio DocStore] !
--- ODBC Version MAY cause printing issues!

Has anybody been able to solve this issue without recreating the Windows profile? I don't want to have to tell the client that they need to recreate the Windows profile for another user.