Douglas, thanks for helping in figuring this out.



No, I did not install a Payables service pack at the same time. From my records, the last AP service pack was applied August 26, 2008.



Yes, I checked, double checked and triple checked the rights on the GLOB files, other files within the folder and the folders itself. All the rights were the same after I installed the service pack as previous. They were not read only. After un-installation, the rights were still the same. In fact, I did not touch the data files when I uninstalled the service pack, just the program files.

--Andrew

Hi Andrew,

I believe that the Receivables hot fix installs an updated version of the database interface file, which is common among all appliations. This file is named ADS32.DLL and can be found in the \softrak\system directory. When you restored program files for Receivables, did you restore this file as well? It may be that it was this file (or perhaps another common system file) rather than the Receivables program files that caused this issue, in conjunction with the state of your Payables data.

If you go to the \softrak\system directory and look for this file, what is the date and version (check the file Properties)?

Hi Andrew: (nice name )



Yes, there has been no change. We have this feature enabled. Back in April 2006, our company switched billing programs (separate from Adagio and used by more people than have Adagio) and I discovered a conflict between Adagio and this new billing program, on the workstations that had Adagio. We had to enable opportunistic locking, and have had it enabled ever since with no consequences. After every previous Adagio service pack, we get the screen about this when the workstation setup is done and we always answer No to disabling the feature. I always do this myself, and after this recent install, I answered No as usual.

I checked the registry of the workstations and the server, and there was no change in this regard.



The server is running Windows Server 2008 and all the workstations are Windows XP.

Yes, ADS32.DLL was one of the files that I replaced back. The old file has file version 1.12.54.2551 and the service pack file has file version 1.12.54.2599.

Hopes this helps in some way.

--Andrew

The old file date is 5/11/2009 and version 1.12.54.2551. The service pack file date is 10/1/2009 and version 1.12.54.2599.

--Andrew

If you were interested in pursuing this further, there is a 'System Updater' that is available for download and installation. It is a recent fix to just the common system files such as ADS32.DLL and others to address an issue with exporting information to Excel.

The version of ADS32.DLL installed is 1.12.54.2609, which is even more recent than the one installed by the Receivables hot fix. If you were to install this system file update and the Payables problem re-occured, that would absolve the Receivables program updates as the reason and point more focus to the common system files.

Is it possible you're running SMB2 on the server? This would have happened if someone plugged a Vista machine into your network. If this is possible, then run \SOFTRAK\SYSTEM\SetServerForAdagio.EXE which should have been installed with the recent upgrades.

Are multiple people entering batches in AP at the same time? I assumed the answer was "yes", but it's possible the AP issue is unrelated.

Hi Andrew,

The change to SMB1 will only solve the problem if it was the Adagio workstation that was running Vista.

After you restart your server, it would be useful if you would install the System Updater without installing the AR Service Pack to see whether the problem re-appears in Payables.

If you know that all the invoice, and check batches have been posted in Payables, then there should be no files APIddddi.DAT/APIddddH.dat/APIddddD.dat (for invoices) or APCddddI.dat/APCddddH.dat/APCddddD.dat (for checks) in the Adagio data subdirectory.

The recently posted System Updater appears to solve this problem.

Not that I think this is related to your specific problem but it is related to getting a “Windows – Delayed Write Failed. Windows was unable to save all the data for the file... bla bla bla.” type error.

On upgrading a client, who uses AVG Internet Security, to OE 8.1B we started getting the above type message during OE Day Ends and this caused some severe problems in the accounting data. After much back and forth I found that the AV Exception List on this workstation (trust it to be the one that does OE Day Ends) did not include the Adagio folders. Once they were added the problem went away.