TMP files not deleting automatically, disrupting reports.

SUGGESTED

Hello everyone, I'm the IT admin for a small company that uses Sage 100 2017 Advanced.  We upgraded to a new server in October and installed the new release on the server and workstations.  I'm not very familiar with Sage itself, so pardon me if my question is rudimentary.

In the Sage2017Adv/MAS90/Home/TextOut directory, when users are running reports, sometimes the tmp files created stay open in the Sage process on the server, causing hang ups and leading to my users being unable to proceed.  I have to have everyone log out so I can restart the Sage process on the server and manually remove the tmp files that area deleting because they're showing as still in use by "System".

We've got a workaround right now which entails my users remotely logging into the server itself and doing their work and reports, and everything works perfectly that way.  However, if they try to do the work on their workstations the problem starts up again.  I've checked and re-checked permissions, antivirus and everything else I can think of and have come up empty.  We utilize a UNC path to the server, unlike the previous install where all the work was done and saved on the workstation and then uploaded to the server.  I don't know if something is causing communication errors or what, and I'm honestly stumped.  Any help would be much appreciated.

Parents
  • 0

    A TMP file in the textout directory?   Usually files get created there when doing file exports or printing to files.  I do see some files in my textout directory relating to miscellaneous things like rebuild key files.   Not aware of other situations where files get created regularly. And to keep others things from happening is very mysterious to me.

    What are the names of the files that are being created which cause problems?  Do you know what function is creating them?

    There are temporary files that can be created in the data folders such as (GLxxx,  ARxxx) that will have wrk included within the file name and a string of numbers but not in the textout directory.   These are created during printing of reports and forms and sometimes do not get deleted if the user crashes out of printing.   On some of my clients this is very common, on other I rarely see it.  Not clear as to why some clients and not others.  Normally these do not cause any problems unless you are printing to paperless office.  Crashing out then can leave entries in the registry that can prevent printing but normally only at that workstation.  You would get a message something like "unable to process the lock file"..

  • 0 in reply to TomTarget

    The names of the files are actually the workstation name, such as DESKTOP-ORAEM0D.tmp or the name given to a machine on the network.  Right now there is a file named VISHVA-DT-1vp2.tmp that has been sitting in the TextOut directory since the 10th of January and I'm unable to delete it because it's listed as still in use.  Usually once the report or activity is done, the tmp file is converted to a .001 RAR file or something similar.  I'm at a complete loss at this point.  I showed my Accounting Manager your response and she's familiar with the issue you described, but that's not what is happening with their reports.

  • 0 in reply to Voorhees80

    HI, the TMP files in /home/textout are generated by legacy report printing. In Sage 100 2017 that would be Work Order, MRP, Job Cost etc.....

    If you are unable to delete the file, identify the workstation generating the temp file,   user is most likely directing print output to an invalid printer, offline printer etc......or leaving report preview windows open.  If you are unable to delete the file, clear the printer queue on the workstation and delete

    John Nichols

    Sage 

Reply
  • 0 in reply to Voorhees80

    HI, the TMP files in /home/textout are generated by legacy report printing. In Sage 100 2017 that would be Work Order, MRP, Job Cost etc.....

    If you are unable to delete the file, identify the workstation generating the temp file,   user is most likely directing print output to an invalid printer, offline printer etc......or leaving report preview windows open.  If you are unable to delete the file, clear the printer queue on the workstation and delete

    John Nichols

    Sage 

Children