Good day to you all,

We are having problems with ledger.ini.



I have verified the ACL and "everyone" can read/write to this file.

This error is forcing all of our users to manually locate the books they want to use..

Any ideas?

Thank you and,

Cheers, JK

John:

Assuming that the file has not become corrupted this always means what what is says. Can the user edit the INI file with Notepad?

Hi Doug,

Sorry but I failed to check the dead obvious before posting.

After checking around a bit I noticed that one of our users left Ledger open and the selection process and the file was not editable.

So, the question transforms into: since all users seem to share this one ini file albeit in different sections how do we handle the situation when more than one person is attempting to access it?

Thanks and,

Cheers, JK

Adagio Ledger handles that. Failing to write the INI when logging in is not that big a deal, nothing terribly important will get lost (just the last accessed database I think). The alternative would be to prevent anyone from getting into Ledger at all.

Would that have been preferable to you?

Hi Andrew,

Indeed exactly correct - users can still access the books by using the directory selection process rather than the shortcut.

The problem is that our users see an error message which is followed up by an email and questions why things are not working as they should.

Is their a way to disable the quick access method in it's entirety.

That way I could close the issue off by issuing a new procedure...

Cheers, JK

Hi John,

We cannot figure out how your user managed to lock the INI file against modification by another user. These files are open and closed in (micro) seconds.

What was the user doing? Did you reboot their workstation?

Hi Andrew,

It is a problem that users are running into in the morning and yes, we have rebooted the machines - all of them - cold boot that is.

The odd thing is that the problem started on one machine so, we rebooted it and the problem went away but appeared later on another computer - too weird...

The cavalry rolls in at about 0830 and three or four of them go into Ledger at the same time (more or less) and all it takes (what I am thinking) is for one user to leave the quick access selection window open and I believe the file stays open - my hunch...

You state otherwise - ie: the file is opened and closed in micro seconds so the only issue could be some sort of network issue or just a real lot of bad luck...

If you could please take a moment to check with dev regarding the file handling I would be most appreciative as we are not suffering any network issues - we have a managed switch running a gigabit network and we watch it and going the next step is going to take a bit - network sniffing etc...

Thanks in advance and,

Cheers, JK

Was you user sitting on the "Previously opened" list when the error occurs?

Why not create an Icon for each database your users want to access? If your users are always accessing a single database, then you should specify the Folder (/dx:\adagio\data) and Extension (/edat) on the command line for the module. Also, why not have Windows remember the UserID?

It's definitely not Adagio. We open/read/close or open/write/close this file each time it's accessed.

Hi Andrew,

I believe that might be the issue - they are sitting on the "Previously opened" list - that is why I asked you to check with dev regarding the file handling as the solution would therefore be very simple - tell them not to do that!

Adding shortcuts to each set of books is a good idea but most users deal with between 3 to 5 sets of books across the different modules so it quickly becomes icon mania...

Thank you and,

Cheers, JK

That file is not open when the users are sitting on the screen. It's never opened for more than a single line of code.

You can confirm that the mere act of sitting on that screen is not the problem easily at your site. It's something else external to Adagio. Backups? Virus checking?

It's not us.