I use Adagio Ledger V9.0A, Payables V8.1A, and other modules. I retrieved a batch of entries from payables into ledger and had to make some changes/corrections to some of the entries. For example entries were posted to the wrong account numbers in payables, but were discovered after printing the retrieved payables batch in ledger.

I edited the batch of payables entries and then hit the close button afterwards. The following messages came up "Deleting batch details, Saving batch details", then the following error message: "Access violation at address 00700E9E in module "Ledger.exe" Read of address 00000014. OK"

On clicking "OK" I noticed that most of the entries in the batch are no longer there which means the batch is corrupted and I will have to restore my data.

I need help URGENTLY.

Ruth

Hello Ruth,

First, make a backup of your data. Then run a data integrity check and see if there are any errors that can be fixed.

Hi Andrew

I ran the data integrity check. Only 1 error showed up in the "Application Integrity Phase". The error read "Batch 80 entry line 1 account/department is invalid" I checked batch 80 entry line 1 and there is no problem with the account number or the department number. Batch 80 was retrieved from Adagio Receivables version 8.1A.

Ruth

Hi Ruth,

While I do not believe that this is your problem, it's always useful to know exactly what release of a specific version is being used. A complete version/release would be 9.0A (080122) where the numbers in the brackets represent a release date. What release of 9.0A are you using ? Select Help | About for the version info.

Regarding the DI error, is the department defined in Edit | Departments ?

Pete

Hi Peter
My Ledger version/release is 9.0A (080122).

Regarding the DI error, I do have one department defined in Edit departments for my expense accounts, but this particular account number is a balance sheet item so there is no department number.

Ruth

Hi Ruth,

I called around and can find no occurances of either of the problems that you experienced (are experiencing) at any of my 9.0A (080122) clients. Neither can I re-create it at my office, other than if a department is not defined, then I get the DI error you mentioned.

I'm pretty sure that most users have seen "Access violation..." errors at one time or another, but these are often one off instances where network access has been interupted for reasons known only to the man above and called "random glitches" by computer gurus. If this happens while saving a batch, the result is usually disaster - for the batch at least - and in such cases, deleting the batch and re-entering the data or restoring a "good & very recent" backup is usually the way to go.

Have you edited any batches successfully since or has the error been recurring ?

Pete

Hi Peter,
I have had this problem twice and both times it is which batches retrieved for AP. After restoring my GL data I made the corrections in the AP batch with no problem.

I will see what happens at the end of March after retrieving my AP batch in GL.

Ruth

Hi Ruth,

Why are you only retrieving your batch once a month? If you did it weekly (or better yet daily), there would be fewer transactions lost if there is a problem.

Hi Andrew,

We prefer to retrieve at monthend. But I still need a solution to this problem because it may happen even if I am retrieving every day.

Ruth

Hi Ruth,

Given that the problem is intermittent and not repeatable, it may be very difficult to isolate what's causing it. A bad network connection might cause this for example.

If you insist in retrieving all your transactions at the end of the month, then I'd just recommend that you be religous in your backups. Disk space is cheap. Perhaps at some point you'll be able to identify a sequence of steps that you take to re-create the problem.

I know this isn't very helpful, but until the problem is completely repeatable with a set of data, there's very little we can do.

I'm having a similar problem in Adagio Ledger (the newest upgrade version). I get the same message (see below), always while entering or editing a batch. I can't get the error message to close and my ONLY option is to end GL using Task Manager. Needless to say, the batch entries disappear and I have to start again.

access violation at address 005CA09D in module ledger.exe read of address 00000014

Carol

Hello Chacamaty,

Can you record these a few times and see if the "at address.." or "read address..." values are changing? Also, does this happen at a consistent point in adding/editing a batch (entering or exiting a specific field on the entry?

Thanks

Actually, I've written down the "at address" and it's always the same. I haven't noticed if it's "triggered" by a specific field or action. It is always when I'm entering a batch, ie cash receipts and not editing an existing batch.

Thanks for the info.

Now, can you record a couple of times which field you were in when the error occurs? Also, do you have any other forms open in Ledger when you are entering the batch?

Hi all - I have a client who is reporting an access violation error after installing the Ledger 9.0 upgrade and recent service pack. It only happens when she attempts to print the Source Journals. Everything else works fine. Any suggestions?

Lars

Hi Lars,

Yes, printing source journals broke somewhere along the way. We've fixed this for a service pack, which is either now available to download (for business partners) or will be in the next day or two. I do not know when the upgrade notices will go out to clients.

Hi Lars,

We only recently had the Source Journal problem pointed out. You'll see a service pack to fix the problem out tomorrow or Friday.

Sorry for the inconvenience.

I was posting a batch into the GL when I got an error message-which was something to the effect that there was someone else using the system, then it shut down, did not have time to record exactly what it said. I am the only one that uses the system and did not have any other windows up when I was processing the data. Now I can not log back into the GL - get the message Incomplete posting, only Integrity Check will be available, did a check and it shows that the accounts that I was posting to are out of balance. Any suggestions?

Hello shutch,

What is sometimes unclear is that you can be the "someone else" using the Ledger, by having some other function (such as View accounts) open in another window.

The fastest way to get back up and running would be to restore the backup you made just prior to posting (you did make a backup - File | Backup - didn't you?). If no backup is available, contact our office to arrange a data repair.

There is a Service Pack expected for Ledger 9.0A expected sometime today or tomorrow that will improve the error handling in the posting process.

Yes, I realize that I could be the someone else and I know I did not have any functions open. For some reason my backup did not work the first time, restore again I can now log in. Did a backup and integrity check everything seems ok. Thanks

I am also having the Source Journal access violation problem that Lars is describing.
When will the service pack be available to END users (and not just business partners)?

Hello Sonia,

Service Packs are released to End Users and business partners at the same time. Only Upgrades are pre-released to Partners (while we wait for the CD to be duplicated), so that they may become familiar with the new features before their users start askin questions. Service Packs rarely add new features (although sometimes the fixing of a deficiency can seem like a new feature).

I'll post a link to the announcement page when the Service Pack is available.

Thanks for your patience.