This is a Sage 500 ERP generated message.  When the application runs, it needs to figure out all the places where stuff should be.  The value of your environment variable looks ok for most cases for user "wth".  Please start a command window (from the Windows start menu or use the Windows key + R) and issue the following command:

set LOCALAPPDATA

The casing for LOCALAPPDATA is important.  This the is actual Windows environment variable that Sage 500 ERP is trying to access.

If you wanted to see all the Windows environment variables, you would just type "set" in the command window.

Then using the Windows Explorer, navigate to that directory.  You may or may not see it depending upon your Windows Explorer view options.  I think you need to have the option to display hidden files and folders on.  If you cannot navigate there, then something is likely wrong. 

Eventually, the application will be looking to use "C:\Users\WTH\AppData\Local\Aatrix Software\Aatrix Forms\Sage500", so if it cannot locate "C:\Users\WTH\AppData\Local" then that is a problem.  

I have yet to see this particular issue over the years.  Are you working inside of a virtual environment?  

Thank you.  I know that Appdata\Local exists, and when I run that command it is C:\Users\WTH\AppData\Local\. This is a physical machine.  That path to Aatrix exists.  

Would you happen to know the Sage 500 version that it is running on?  I would suspect version 2021 prior by you description of the menu task name you described.  Also, has the 1099 processing been run during  TY 2023 or prior or is this the first year for Sage 500 ERP 1099 processing?  Is this years 1099 processing being run on the same client machine as previous years?

Also, would you know the Windows version (10/11) involved, including any possible version indicators?

2021 update 3, this machine has been the one running all the 1099's previously, so I believe yes 2023 was run.  This user is on Windows 11 24H2.  

HI, turns out it's a bug running on 24H2 so support is working with the developer.  Thank you!

We have found success with this issue so far with the latest release on the customer portal posted about 7am PST.  We discovered that Windows 11 24H2 seems to act unpredictably.  We have found that two machines with the same version of W11 24H2 have reacted differently running the same code.  If you are still trying to get this out, try today's client application available on the customer portal.

We have found success with this issue so far with the latest release on the customer portal posted about 7am PST.  We discovered that Windows 11 24H2 seems to act unpredictably.  We have found that two machines with the same version of W11 24H2 have reacted differently running the same code.  If you are still trying to get this out, try today's client application available on the customer portal.