When entering invoices and printing checks, into the system, my computer performed a re-boot and & subsiquent scan for not shutting down properly. In order to issue the checks I had to open another batch. Once I issued two more checks, the same thing happened. I had to have the checks so I opened another batch and entered and printed the final two checks. I could post the final batch I entered by the other two give me the critical error 1377 message. The first batch is quite large because it had checks included from previous working days that I had not yet posted. Of course my year end is March and I need to post these batches so I can retrieve them into AccPac and get on with year end.
Is there anything I can do to post these batches and is there anyway I can correct this for the future? Maybe its because I don,t have the most recent update? I am using version 6.5a 000217.

Hello Denny,

Error 1377 is not one that I have heard of before, although similar errors have been reported such as, "Critical error 1327 (or 1339) - Unknown DOS error reading file", where there has been a problem with data integrity and/or corrupt batch control files.

Here are some suggestions:

ISSUE:
When trying to open a QCWIN database: ?Critical Error 1327. Unknown DOS error reading file ?? This could be followed by ?Internal error, file has not been opened.?

PROBLEM:
QCWIN gives ?Critical Error 1339: Unknown DOS error reading file? when attempting to perform an operation or process within QCWIN.

NOTES:
This error could occur at any point, depending on what has happened prior to receiving this message. Normally, this error occurs after a system crash or failure, when the user was in the middle of entering batches, posting, or other processing tasks. The next time they go back into QCWIN to continue their task, it gives this error. This normally indicates some kind of file corruption or damage incurred due to the system failure or lockup.

SUGGESTIONS
1. Reboot the workstation that got this error before doing anything else.
2. You should perform a Data Integrity Check, and rebuild if any errors are found.
a) Open Adagio Checks
b) Go to the File menu
c) Choose the ?Data Integrity Check? option & click on ?Check?
d) If errors are found, now choose to ?Rebuild? - Adagio should fix the errors reported
e) Do another Check to ensure all errors were fixed

If you cannot even gain access to the Adagio database:
This is a good indication of data corruption, however, you could try a couple of elimination processes to see what else could be going on ?

1. Try opening the Sample Data database.
a) If you cannot gain access to the Sample Data database, then there could be a problem with one of the associated program files. Try re-installing the Adagio program:
i) Using Windows? Explorer (or the DOS prompt), rename (or remove) the Adagio program sub-directory from the X:\SOFTRAK directory (where X represents the drive where Adagio was installed.
ii) Reinstall Adagio
iii) Try your procedure again
b) If you CANNOT duplicate this in Sample data, then there is nothing wrong with the program and this just goes further to confirm corruption of the live data, and your only other options are:
i) Restore from a good backup done prior to getting the error message(s). You will have to re-enter any batches that were not yet entered at time of backup.
ii) Get a Database Repair
iii) Rename the batch control files. If you don?t have a good backup, or your batch(es) were small, you can rename the QCBCTL?*.* files. You will lose all open batches, and they will have to be re-entered, but this may be preferable to paying for data repair.) To do this:
(1) Close Adagio Checks.
(2) Using MS Explorer, (or from the DOS prompt), go to the data directory where the Adagio Checks data files are.
(3) Find the files Qcbctl?1.xxx, Qcbctl?2.xxx and Qcbctl?R.xxx.
(4) Rename them (change the 3-character data extension to .OLD or .XXX), or if you are sure that you do not need these files anymore, remove them.
(5) Open the Checks database again. You will be warned that it could not find the batch control files and that new ones will be recreated - press OK to continue to open the database.
(6) Re-enter your batch(es) and process as normal.

If you encounter similar problems after entering a new batch, you will likely need to get a database repair done, as there is something wrong in your data that keeps causing this problem to occur.

Our Database Repair Department can be reached by calling (604) 736-3741, or you can email them:
datarepair@softrak.com

Regards,
Softrak Support