Error 9/013 Saving Elliott Spooled Reports in Temp Folder

Error 9/013 Saving Elliott Spooled Reports in Temp Folder

Release Date: 03/11/2025
Version: 8.x & Up

Q - On the Elliott PSQL database server, I also run defer processing.  I try to manually perform a COP Posting and receive the following message:
Error 9/013 saving
C:\USERS\ADMINI~1\APPDATA\LOCAL\TEMP\2\CP0305.20250117.122623.SUPERVISOR.COP_Sales_Journal..1.Txt

This is repeatedly happening. I look at the C:\USERS\ADMINI~1\APPDATA\LOCAL\TEMP\2 folder, and I don't see any files with similar name.  On the other hand, I look at C:\USERS\ADMINI~1\APPDATA\LOCAL\TEMP folder, and I see a similar file CP0305'20250117'122623.SUPERVISOR'^'~.TXT. See sample screen below:

If I stop my defer processing from running in the background and exit all Elliott sessions in my console session, then I start up Elliott, this problem is fixed.  Do you know what has happened to cause this error?

A - To be short, this is a bug and the problem has been fixed on 03/04/2025 for Elliott 8.6.  If you run Elliott V8.6 version released after this date, then the problem should be fixed.

To give a little bit more details about the nature of this problem, this issue is related to the “Temp” folder in the users profile.  In Elliott legacy report printing (i.e., Non Report Desk Reports,) Elliott uses the user profile temp folder to create a temporary TXT file. The file name would be similar to the following:
      CP0305'20250117'122623.SUPERVISOR'^'~.TXT
When
  1. CP0305 - This is the printing task name.
  2. 20250117 - This is the date stamp in the format of YYYYMMDD.
  3. 122623 - This is the military time stamp in the format of HHMMSS.
  4. SUPERVISOR - This is the user who printed the report.
Note while this file name is similar to the Elliott spooled report file name format, it is not identical. For example, when we create this temporary file, we don't know how many pages this report will have.  Upon the completion of this report, the system will rename this file to the final format.  Let's say this report has 1 page, then the final file name will become:
      CP0305.20250117.122623.SUPERVISOR.COP_Sales_Journal..1.Txt
It is when the system tries to rename the temporary file name to the final file name that it encounters the error 9/013.  Why do we encounter the error?  When we first start to create the spooled report, we inquiry the system for the temp folder and get the value:
      C:\USERS\ADMINI~1\APPDATA\LOCAL\TEMP
But when we try to rename the file, we get the value:
      C:\USERS\ADMINI~1\APPDATA\LOCAL\TEMP\2
Because the system assumes the temp file should be in the same folder, we get the renaming error.  Windows OS changes the temp folder periodically for maintenance purposes. When Elliott first starts up, we see the temp folder value as C:\USERS\ADMINI~1\APPDATA\LOCAL\TEMP.  This value stays static throughout the lifetime of the Elliott session.  Since you normally keep defer processing running for a long time without exiting, this temp folder may be an old path while the current Windows OS temp folder has changed, which it used when it tries to rename.

To fix this problem, before we spool the report to the temp folder, we no longer rely on the temp folder at the Elliott start up time.  Instead we will use the latest temp folder from Windows.  By doing this, we will most likely reduce the occurrence of this error message.  In addition, we now keep track of any spooled report file renaming error in RenError.Log in the corresponding company log folder.

Note: you can get the current Windows OS temp folder by going to the command prompt and typing "%temp%"



Modified Programs: LOG2FILE.MAC, TEMPPATH.PL, PRINTNSI.PL, NWSMDFRP, PRINT30.CBL, PRINT240.CBL, SMASYNC.CBL

EMK

    • Related Articles

    • Why Can't User Access Certain Spooled Reports?

      Released Date: 03/13/2025 Version: 8.0 & Up Q - I am having trouble giving another user access to a certain spooled report. I am sure I am missing a flag somewhere. There is a deferred processing task set up to run Credit Card Log Reports each night ...

    • Change - LOG Files in EDI Export Processes Are Now Redirected to LOG Folder

      Release Date: 05/05/2021 Version: 8.5 & Up Currently, Elliott EDI Export Processing may utilize LOG files to store error information. For example, the CPSHPEDI.LOG file is used by "Shipped Data Export" (ASN/856 Export). This file currently resides in ...

    • Change - Move GLFSPASS.DAT (GL Financial Passing) File to LOG Folder

      Release Date: 05/05/2021 Version: 8.5 The General Ledger Financial Passing File (GLFSPASS.DAT) resides in the Elliott DATA folder and is an ASCII file, and therefore is subject to NTFS security issues. During the setup of NTFS security, all *.DAT ...

    • Btrieve Error 46 on S/M Activity Log File

      Last Update: 06/20/2024 Q - I receive the following error message when I start up Elliott and launch a session: Btrieve Error 046 on S/M Activity Log File But this only happens to company 1. When I access another company, I do not receive this ...

    • Avalara - Log Files

      Release Date: 4/28/23 Version: 8.6 & Above Log files can be very important when investigating why taxes may not be calculated as expected. In particular, the AvalaraAPICalls.xml file is important when you speak with Avalara reps for support. This ...