I ran DIC on the back up data (backed up before we started the month end). When I run an Integrity Check in DIC it reports "no errors". When I run an integrity check in AR, it reports,

"orphan gl detail have been found"
"checking transactions gl details... 4 errors found"
"Application integrity phase... 4 errors found"

This is what I rebuilt the last time, but it didn't help the statement problem.

I'm getting the same error (statments stop printing after the first one) even when printing to file (.pdf) and when using a sample spec.

Something noteworthy is that when I use the sample data (using our spec) and select 10 customers and print to screen, it sucessfully shows 1 of 10 pages and you can scroll through them. When I do the same thing with our data, it shows only 1 of 1 page. Same thing when I print to the printer, it says 1 of 10 pages using the sample data, but only 1 of 1 when using our data, even though I've selected 10 to print.

I got it!!!!!! Not sure why it worked, but I changed it to print to screen, then clicked "Preview" and it previewed correctly, 192 statements. So, I clicked print from there.

The bad news is, when I tried it again, it no longer works. Glad I printed while I had the opportunity, but I have no idea how to work around this next time.

Another problem is that even though I somehow miraculously got the statements to print, it did not ask me if everything printed okay and do I want to update the billing cycles and customer printed dates. Can I force it to do this somehow manually? Please advise.

Can I run the period end without updating the billing cycles? I'm not really sure what updating the billing cycles actually does, but I do need the transactions with zero balance to move to history.

Good morning.. I managed to print the statements again (to Adagio .pdf) so that I was able to get the message about updating the billing cycles and then I completed the period end. Unfortunately, however, I still have not been able to correct the problem. Since I don't want to go through this every month end, I would appreciate some direction on how I can get this resolved.

Hi, Susan,

Let's back up please. You were receiving an Access Violation error and you had integrity errors.

Access violation errors can be very difficult to duplicate and, as you found, you weren't able to in sample data. Did you check the ARWINERR.dat file to see the results of the last DIC?

In Adagio, you will never receive a prompt to clear when you print from the Preview screen.

Problems such as yours are very difficult to resolve on a forum soch as this. Perhaps, now is the time to contact your Adagio consultant.

Hi Softrak Support,

We were receiving an Access Violation error and we had integrity errors, however, the integrity errors showed up ONLY when running integrity check from within AR. When running integrity check using DataCare on the same data, it does not report any integrity errors. The integrity errors reported within AR are as follows:

"orphan gl detail have been found"
"checking transactions gl details... 4 errors found"
"Application integrity phase... 4 errors found"

Since these errors are only being reported in AR, I can only rebuild from AR. After rebuilding in AR and running integrity check from within AR again, it reports no errors.

The Access Violation errors are unchanged whether using the data with the AR errors or using the data after the rebuild that contains no errors.

One more note - I opened our data from a March 31 back up and it also has the same 4 errors reported in AR integrity check. We never noticed the errors were there because we do our integrity checks in DataCare, not AR. The errors have been there for months, maybe years, but we have not had any problems printing statements until this month. I can no longer print statements using my March data. ARWINERR.DAT has nothing in it except what is pasted below:

Checking Terms... OK
Checking Account Set... OK
Checking Billing Cycle... OK
Checking Transactions... OK
Checking Customers... OK
Checking Ship To/Contacts ... OK
Checking Cash batch 393 ... OK
Customer Filters ... Checked OK
Checking Customer Alerts ... OK
Checking Customer Alert Details ... OK
Checking Contact Alerts ... OK
Checking Contact Alert Details ... OK

The errors being reported in the DIC are related to the file that displays the GL distribution of a transaction. This won't impact statement printing.

I agree. On July 30, we did not experience any problems printing statements. The only thing we changed between July 30 and Aug 31 is that we installed the following:

Lanpak Upgrade: 9.0D (2011.06.30)
Ledger Upgrade: 9.0D (2011.06.29)
Receivables Service Pack: 9.0B (2011.07.27)
Payables Service Pack: 8.1C (2011.07.29)

Since these updates above, we noticed a glitch in Ledger. I used to print the batches to file (.doc) and overwrite the existing file, however this stopped working. It actually deletes the .doc file and leaves the status of the batches as open instead of printed. So, as a workaround, I tried printing them to an excel file and overwriting and this works fine. I didn't bother to report it since it's insignificant and I have a simple workaround. The only reason I mention it is that it is another strange printer behaviour that started after the above updates.