Is it a Sage macro (with an extension of .avb) or is it a macro built into Excel or Access?  Where do the source transactions come from?

This is happening when running Sage macro's that create AP invoices in this particular instance.  However, I have gotten this same error when running a similar Sage macro that builds AR records.  It doesn't seem to matter what type of transaction we are running.

What is the source of the data that the macro is pulling from?  An external database?  You might have to contact the person who wrote the macros.

The source is an external database.  Myself and one of my co-workers wrote the macros in question, but we did not have any problems with these macros before the upgrade.  They have been running for several years.  Of course I can't recreate the problem, either, or I would step through the code.  

I'd be tempted to have you put in some error trapping code so you can see if the macro is having a problem connecting to the source of the data or if the problem is running the macro, perhaps outside of the Sage desktop, is having a problem initiating a connection to the Sage database.

I can do that, thank you so much for the suggestion.  We do have some logging in the program but not enough.  I appreciate your help!  Let's see what we can find out with additional logging.

So I have added a bunch of code to my program to see where I am getting the error I described last month.  It is when the program is trying to open a session.  I put code in the macro to retry 5 times when it gets that error but it doesn't seem to help.  However, if we start the program over using the same data, it connects no problem.  I think it might have something to do with a file that is temporarily locked in the SITE directory.  I just don't know how to handle it in the program correctly.  Do you know how the session works exactly?  This is the code where it is dying:

    session.Open "ADMIN", "ADMIN", destdbID, Date, 0, ""

So when I do my retry I am only retrying the open session.  I may not be doing enough in my retry.  

Thank you for any guidance that you might have.

What does your session.Init line look like?

Figured it out!  I just added the set new session, the init, and the open to my retry code.  This is working.  When two sessions are hit simultaneously and it throws the error, it just retries and gets right in.