Good Morning,

I updated over the weekend and now cannot create any report at all within ledger... I receive the following error message:

"The table 'ALZ92_Temp_posted_Trans' could not be found.
Error in File Allistc_v2 {951F7807-8CD3-4809-99FA-9200B5B38501}.rpt:
The table could not be found"

Please advise how I can correct this issue

Did you encounter any messages during the install? What version of Windows are you running?

I did not encounter any message during install, it seemed to go well until I tried to print a report.... I am running windows 7 professional

Can you review this thread and see whether the advice helps.

Hey Andrew, I looked through this thread and tried the suggestions... and still nothing seems to work

I did a Ledger 9.2A update at a client earlier today, and I kept getting into some kind of problem.
We finally got it working nicely, by logging onto the workstation as the Admin user.
This was necessary, even though the user that I was logged in the first time supposedly had Admin privileges.
Did you do your install as the Administrator, with full privileges?

Good Morning,

I have all the user rights, but the system administrator also tried and they also cannot get the reports. I did try again with their login just in case

Hello Christine,

The suggestion is that someone with Administrator rights do the install, not run the program. You can right mouse click on the setup.exe and choose "Run as Administrator".

The ODBC connection to Adagio required to run the reports in Ledger 9.2A has not installed properly. This is usually a rights issue.

OK, this morning I tried again and ran it as administrator... the setup seemed to go ahead without any issues but the problem still remains. I am concerned that this is a month end and year end period and I am being asked for reports that I can not produce. Would someone be able to give me a call and assist me in correcting this issue? 705-465-5075 is my direct line. Thank you.

Hi Christine:

I know that Softrak's office is closed today and re-opening Monday Jan. 5th. You could contact your local Adagio consultant for a faster response. Given your immediate need to be able to print reports, you might consider rolling back to the previous version of Ledger.

Hi, Christine,

I've encountered this one other time. In that instance, the site's Adagio installation wasn't correctly set up. This could also be a rights issue. As Bruce suggests, the problem you're experiencing is one that would be best handled by your dealer as it is very difficult to fully diagnose over the forum.

Hello Christine,

This is usually caused by a corrupt download of the Crystal Support files. To get a new download, empty the Folder: where "x" is the drive letter your Adagio modules are installed on.

Then re-do the Ledger install. It will go out to the internet to get replacements of the deleted files.

To close this thread:

It turned out that some Adagio modules were installed to N:\ and some more recent ones to N:\Softrak. After Christine uninstalled all Adagio modules and reinstalled everything to N:\Softrak, Ledger printing is now working and even some smaller issues have been resolved.

Hi, Bruce,

Thank you for the follow up information and confirmation. The messed up install was what I expected at your site.

As well, one of Carol's sites that was receiving these same errors when trying to print in GL9.2A was found to have a defective w/s and the site is now replacing it.

With respect to Carol's site that was experiencing the issue with the CRRuntime ... msi file, they'd found that they had some network security that was blocking the file. While their issue isn't completely resolved yet that I know of, I do expect it to be shortly.

The CRRuntime... msi file issue - I ended up using the zipped file from Leigh to replace it and all is fine.

Hi, Carol,

Actually, that was what resolved the problem for this post: http://softrak.com/ubbthreads/ubbthreads.php/topics/44139#Post44139.

Bruce's problem and another's were resolved by cleaning up a very messy install. Your other site's problem is resolved by replacing the workstation as it was the only one exhibiting the problem and wouldn't even work for their network Administrator.

Thank you for trying to closing your problem posts.