Hi, since the new install of GL 9.0B I can no longer print a TB to screen or print. I request to print as usual but nothing is happening and yes all other reports are printing in all the modules.

Thanks
Christine

Do any other Ledger reports not print?

Yes, everthing is printing.

It sounds like that report (or one of its necessary tables) was not properly updated when the new version was installed. This happens if the previous version was installed from the server (rather than from a workstation) due to a Microsoft bug.

Your Adagio consultant can help you fix this up.

Hi Chrisine

I had this exact same problem with a client. I am the Adagio consultant so I had to help myself

I ended up renaming the \Softrak\Ledger folder, as well as the QRTAL?90.QRW files from the \QRASP folder and the @L90*.ssi files from the \Softrak\Dict folder, and then re-installing Ledger from scratch (then copying the old Ledger.INI to the new Ledger folder so that certain user settings were preserved). It worked.

But now that you report the same error, it really makes me think there is a problem with the install somewhere.

Steve

Steve,

This could be that file date scenario on Windows 2003/2008 servers and installing directly on the server for a previous installation. If Windows mucked up the files, there is only so much we can do...

That being said, if everyone is getting the same installation situation then this would be something we'd want to know about.

"Everyone" isn't.

I had the same problem with not being able to print a trial balance without it erroring out on me. I uninstalled and re-installed Ledger, the updates and the hot fixes, and it did not fix the problem.

I followed Steve's instructions and it did fix the Trial Balance problem. What it does NOT fix is that Financial Reporter encounters an error and shuts down every time I try to create a Statement Group. Any suggestions on how to fix that?

Have you installed the latest Ledger hot fix?

The statement group information is stored in the file GLRPTGRP.dat which may be damaged. Renaming the file will cause a new (empty) one to be created.

Yes, I have the latest hotfix install. After deleting GLRPTGRP.dat from the dataset I get the same error.
BTW, it did not create a new GLRPTGRP file, it just crashed upon attempting to create a new statement group item.

I tested this with other computers in our office. The computer that did not have the latest hotfix install did not crash upon creating a new statement group.

Was that test on the same company data?

If things work on a different workstation and the same data, there may be something goofy in the Financial Reporter settings stored in the Windows Registry for that workstation. You may need to edit the registry and remove the Financial Reporter settings and let the program re-create them.

What version of Windows is on that workstation? It should be at least XP and not an earlier version.

It does not seem to matter what data we are working with. The computers with the July hotfix work. The ones that have a more recent hotfix crash as soon as you try to create a new item under a new statement group.

Hi Lyndon,

We were able to duplicate a problem specifically when adding a new statement to an existing Statement Group, using Ledger 90B and the Nov 2009 hot fix. We'll take a look at what is happening here.

Creating new statement groups works OK, as does editing existing groups and existing statements within groups.

Having the same issue with Trial Balance printing.
No server involved. Windows XP pro. All other reports seem ok.
No problems on data integrity check.

Hi, David,

You'll want to do a complete reinstall of GL9. You'll want to uninstall, rename the residual: (a) Ledger folder, (b) Ledger files in the Dict folder and (c) Ledger files in the QRASP folder. Then, reinstall the module.

Something either didn't update properly when a Ledger update was installed or has become corrupt.

Please call if you have a question.

I have a similar problem, did Steve's fix and all was fine (thanks Steve!)

Client rebooted PC (stand alone) and the issue has returned!

We have tried re-installing twice from scratch, and once using Steve's rename method.

Report with issue is batch listings, posting journal, batch status.

Any ideas?

Derek D. Dougherty, CGA
------------------------
KPMG LLP

Hi, Derek,

Something has changed on the client PC. Is there more than one install of Ledger on this workstation? More than one QRASP folder? What are the dates of the QRTALZ80.QRW and QRTALZ90.QRW files? Did they get a new printer?

What version(release date) of GL are they using? Does a Company Profile report print? Any reports? If you use sample data, do the same reports not print?

Most of our reports create temp files in the users Temp folder. When you look in their Temp folder, do you see any folders beginning with GLBL#### or GLPJ#### (where '####' is a 4-digit number)? Do you see any ~DF*.tmp files with a recent date? It could be these temp files are not being deleted by the system as they should be and this is causing the problem.

Sorry, Derek, we need more information to troubleshoot this with you. If you'd like to give us a call in the morning, please do so.

Softrak support,

We had a very similar problem at a client's site recently where the majority of reports were printing fine but the Trial Balance would not (no preview, no print to pdf, no print to paper).

Steve Wilson provided us with a new version of the ALWIN.EXE file that had a revised print function, and this solved our client's problem.

Perhaps this might solve the problem at some of these sites as well?

Do you mean LEDGER.EXE?

Yes, thanks.

I believe that some code in the ledger module was identified as being slightly different from the other modules. Once this was changed, the issue disappeared for our client.

Can I get my hands on this for testing at this particular client site?

Steve? Andrew?

There are two things involved with this. The first is when there is a mismatch between the reports and the tables in QRASP. This can be resolved by renaming the report and appropriate QRT files and reinstalling the product.

The second is rare but has occurred. Usually, the problem appears on most if not all reports. The new code should resolve this one; however, if the problem is really that some files have not been updated properly, unless they are this time, it will not.

I'll email you a file and instructions for testing.

Same problem. Cannot print Trial Balance. Batch Status Report prints okay.
QRTALW90.QRW is 5/13/09 both in \softrak\system\qrasp\al and in \qrasp & QRTALZ90.QRW is 7/7/09 in both places.
Installed System updater - no change.

Will try Steve's solution.

The problem was with the dictionary files @L90AI.ssi & @L90AR.ssi.
Before re-install, both had date of 3/6/2008.
After re-install, both had date of 7/7/09.