Adagio Ledger - Print detail listing error...

Good day to you all!

I hope this posting finds everyone enjoying the opening days of summer <grin>!

We are trying to print a detailed listing report in Ledger and are receiving (but only under certain profiles) the following error message:

"Unable to open data file master accounts net change @LD90DBUK, (123)"

Going to a different windows profile seems to solve the problem.

Perhaps this is an ACL problem?

Any idea on where to look?

Thank you and,

Cheers, JK

Hi JohnK,

Sounds like a rights issue, especially if other profiles/users do not have the same problem. Perhaps try the problem User Profiles and testing print/preview of the Detail Listing report on sample data (\softrak\ledger\samdata) to determine if the data directory/files are related.

If the report previews successfully n sample data for that user, this would indicate that the user(s) don't have the required rights to either the data directory or the specific data files associated with the account changes file, or that another user has 'locked' those files on the network server - due to a problem or anti-virus software or similar.

The error message you are getting indicates the name of the Adagio dictionary (@L90DBUK) that reads the Account Net Changes data file.

Hi support,

Thank you - this is very helpful.

I will reset the ACL in the noted folder and revert once completed.

Again, thank you and,

Cheers, JK

Well, that was not what I expected...

There is no @L90DBUK file in the ..\softrak\dict folder...

There are @L90DI.ssi & @L90DR.ssi but that is it!

Hi, John,

@L90DBUK is a table within the @L90D*.ssi dictionary.

Thank you!

I have reset the ACL to the entire Softrak folder - still the same problem <argh>...

I ran the test on the Ledger\Samdata and the report ran w/o a problem using the problematic profile.

Since the ACL is correct, the reports works on the Samdata I then believe that this might be a hung file open operation or some kind of lock like you refer to.

I will reboot the server tonight and post back up once I know the results..

Again / always - thank you for your support!

Cheers, JK

Good morning y'all!

I hope this posting finds you all well and planning a great long weekend!

I rebooted the server (ie: dealt with a possible file open issue) with no change.

I added the domain admins group to the problematic profile and it runs all the reports w/o a problem.

If this is an ACL issue then the problem accessing the dictionary would occur across all datasets but the report prints on most databases - the error only happens on one dataset so far but for several users...

So the question becomes - what could cause varied behavior when accessing this dictionary

Very strange indeed...

Any ideas anyone?

Thank you and,

Cheers, JK

Hi John:

The dictionary @LD90DBUK points to the version 9.0C files GLNUMB'R and the indexes GLNUMB'x (where x = 1 to 5).

Those are the files that you need to look at regarding rights.

Hi Tony,

Many thanks...

Somehow the ACLs on those files did not include the user group for that database.

Not too sure how this happened but I am certain there is a good reason - aka tightening security means files created before a certain date may only carry the higher level acl (sounds like a mea culpa!)..

I have reset the ACLs and the problem has disappeared..

Thank you Tony!!!!