I'm hoping someone can help with a frustrating error that I frequently get.

In Adagio AR, when I open someone's account and double click on a line item to see the transaction details, I frequently get an error message pop up: "Access violation at address 00070033. Read of address 00070033." I click "continue application" and a new pop-up comes up: "Attempting to perform operation on unopened A/R Transaction matching file." I click OK, and the same pop-up comes up again. I click OK, and the same pop-up comes up one more time. I click OK, and a slightly different pop-up comes up: "Attempting to perform operation on unopened G/L Transaction Details file." I click OK, and the same pop-up comes up again. I click OK again, and the Transaction Details window finally opens, but the section I need (with the GL codes and the amounts going to them) is empty instead of showing the data. When I click Close or the X, I get a pop-up saying "Access violation at address 0078FF32 in module 'Receivables.exe'. Read of address 00000008." I click "Continue application" or X and it goes back to the Transaction Details window. If I click Close or X, I can repeat that for as long as I like, but in the end I have to use Task Manager and End Task on Adagio Receivables to get out of it.
The really strange thing is, if after restarting AR, I try to see this exact some transaction detail again, I can often get into it no problem.

This error happens quite frequently (not all the time, but frequently), and it’ll happen regardless if I did a Data Integrity Check on all modules that morning or not.

Does anyone know what’s causing this error, and how to fix it?

Hello,

There could be numerous things in your Windows/Network environment that are causing this issue. Anti-virus, folder rights, network card going to sleep etc. From what you describe, it could be an issue in Windows where a setting is causing Windows to "Replace" the drive mapping when it's idle for a period of time. Then when you attempt to access a grid in Adagio, it will get errors like the ones you mentioned above because "the cord was cut" to the mapped drive in the background. That's why logging back in will help because it reconnects to the database. The solution is for your IT person to make sure the Windows group policy preference is not set to "replace" drive mappings.

Other than that, without knowing your environment (Windows OS, network configuration, security settings, AV software), it's almost impossible to troubleshoot over the forum. So you'd want to get your consultant involved since they should know what to look for. If they don't they contact me offline for help.

Thank you for your help! I will bring this information to our IT guy.

I had a typo in my post that I just updated. It should've said "The solution is for your IT person to make sure the Windows group policy preference is not set to "replace" drive mappings.

I passed along the update, thanks again.