x Want to participate? Join the group to interact
Options
  • State Suggested Answer
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 107 subscribers
  • Views 4107 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
45
topics
91
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
962
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
Voorhees80

TMP files not deleting automatically, disrupting reports.

SUGGESTED
Posted By

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 Reply Children
  • 0 in reply to FormerMember

    Not really.  Our rep went into the server and unchecked "KeepAlives" and that helped a little, but every now and then I still have to identify ghost users via the PID on the server and end the process to allow the TMP file associated with the session to be deleted.  Pretty much zero help from Sage themselves on the issue, and we've submitted a few tickets.

  • 0 in reply to Voorhees80
    SUGGESTED

    I'd echo what John said above - the most common source of this issue I've seen has been print to preview in Work Order. The issue is they leave the preview window open for far too long. Best example I can give is just before lunch, they print to preview and then go to lunch for an hour. The channel closes, and to the user it's not anything that is earthshattering... no big error message, etc. You're left with that orphan out there causing issues however.

    Other things to check - Are the users who access the legacy modules leaving the temp files LAN users or WAN? If they are LAN users, what brand NIC is in the machine they use? Although it's long since the recommendation was given to me 15 some odd years ago, it was once advised to NEVER use a Realtek card as they were notorious for dropping packets and connection when communicating to the server. The end result was corrupted data as Sage doesn't like to have network blips. To this day we have our Dell's ordered with Intel NICs (Realtek is the default for most of the workstations they sell) and can say the corruption issues back in day have never come back. I dare say I'm not the only still Realtek averse Sage admin out there. Also check the NICs to make sure any "green" power saving settings aren't able to kick in.

    If they are WAN users, how are they accessing system? RDS? Citrix? There are some settings in Citrix that can wreak havoc if not carefully analyzed before making full production use - printing being the biggest PITA of them all.

    On your final comment, take this as a bit of constructive criticism.. It's not Sage's job to know your network. They don't know your layout, loads and quirks (we all have quirks in our networks.) So the folks like John above and the Tools Team really can't get drawn into trying to solve what is either likely an end-user issue or a connectivity issue that would be impossible for them to diagnose from their desks, taking time away from the other customers who they can help with issues that are in their wheelhouse. The one who should really be helping you is your reseller, but it doesn't really sound like they are experienced in network connectivity issues. That being said, this is your chance to be the hero - go download Wireshark and monitor your server and the most frequently problematic workstation that is printing to the legacy modules. Don't be shocked to find something basic.. I once found a 4 port 10/100 hub behind a cubicle wall that was connected to another unmanaged switch and was plugged back into itself. Needless to say... Sage was cranky until we found that piece of junk.  Good Luck!

*Community Hub is the new name for Sage City