Hello:

Our company uses the Adagio Receivables program and we are on the Upgrades Plan. Yesterday I applied the latest Receivables service pack, being 090928. Our Receivables version is 9.0A. The prior service pack version was 090511.

The service pack installation completed without any error notification. I had admin rights when I ran the installation. However, now when we open up Receivables, there is a Windows error message that is displayed. The specific message is:

“Windows – Delayed Write Failed. Windows was unable to save all the data for the file \ASP\DATA\ALL\ARGLOB.ALL. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.”

We also use Adagio Payables, and a similar message appears when that program is opened (APGLOB.ALL). It seems we can still access all the data, but that error message appears.

I checked the permissions on the \ASP\DATA folder, and it appears to be fine - users have read, write, & modify permissions. I did a Data Integrity Check, and everything was fine.

Has anyone seen this error and resolved it? Is there a way to uninstall this service pack? I looked into the two log files (INSTALL.LOG and INSTALL.TXT) and there is a listing of the files which were replaced. Can I just replaced the old files back in and everything will be the way it was before the service pack installation? I can restore from backups, but I will lose a day’s work, and I want to do that as a last resort.

Thanks for any assistance at all.

--Andrew

Check out this article that sets out the 8 common ways this could occur;

http://searchwinit.techtarget.com/tip/0,289483,sid1_gci1041334,00.html

Hi Andrew

I would not recommend restoring from backup or uninstalling the service pack until you get confirmation from someone that the service pack is the culprit. You would likely be wasting your time. I have installed the service pack at least a dozen times, and nobody has complained about anything, let alone your error message.

I would work on the assumption that the problem is unrelated, and focus on Doug's suggestion.

Steve

Thank you Douglas and Steve for responding.

I did google "Delayed Write Failed" and everything I found didn't quite help. I will take Steve's advice, and not restore from backup to replace the new files. I just find it too much of a coincidence that the error message started happening right after the service pack was installed.

I eliminated opportunistic locking enabled/disabled as the problem.

Late last night, I rebooted the server that has Adagio, thinking that would fix the situation. It did not. Everything looks to be working fine with that server in all other aspects.

In any event, it seems that Adagio is still working properly, i.e employees are entering data, batches are being processed, etc. The only error message anyone gets is that "Delayed Write Failed" error.

I have a call into our dealer asking for assistance, but they have not responded back yet.

The mystery continues....

--Andrew

Hi Andrew

If your dealer is who I think it is, they might not be responding for quite awhile.

I am a half-hour away from you and I would like to meet you and see what you are doing Adagio-wise. You are obviously at an advanced level. Check out my website www.sschwartzcpa.com and give me a call or email me if you feel like it.

Steve

Hello Softrak Support:

Any suggestions here? We are still experiencing this error message. It has to be something with the service pack, since it started happening right after I applied it. Has anyone else reported problems with the Receivables 090928 service pack?

What is the method of uninstalling this service pack? Is it just a matter of substituting back the files which were replaced?

Any assistance would be appreciated. Thanks.

--Andrew

Hi, Andrew,

As Doug indicated in his post last week, this type of error is hardware and/or network related. It may be a coincidence that you didn't experience it until some time after installing the SP. Adagio may be your only truly networked software and shared data files and that is why you experienced the error while using it.

It would be a good idea to contact your hardware/network tech to help troubleshoot where the failure lies.

Well, I just spent an hour this morning uninstalling that Receivables service pack, carefully replacing back the program files that were overwritten by that service pack. Guess what?!? The error message disappeared.

We then tested and retested all our Adagio programs (they all were giving that error message), and no error message anywhere. Things are back to what they were pre-service pack.

We were also having a problem creating new batches within Payables. It kept saying that the "batch already existed". It looked like it would never increment the batch number to the next number. After I uninstalled the service pack, we were able to create a new Payables batch.

My conclusion: This error was NOT "hardware and/or network related". Something in that service pack code caused the xxGLOB.xx files to not be written/updated. This was the culprit of our trouble.

--Andrew

My firm has installed this service pack at a hundred site, no one is having any problems with it.

The AR service pack would not impact AP in any way. Did you install a service pack to this module at the same time?

Did you check to make sure that the users have full rights to the xxGLOB.xxx files? If they did not get updated then likley they are read only.

Are you confident that the opportunistic locking settings are properly set on all workstations and the server? What are you running for your server and workstation operating systems? The module installed by AR that would affect AP is \SOFTRAK\SYSTEM\ADS32.DLL. Is this one of the files you swapped?

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.