Sage 100

 View Only
  • 1.  Odd one. Sage 100 Standard version 2015. I cannot

    Posted 01-31-2018 18:19
    Odd one. Sage 100 Standard version 2015. I cannot run PE processing from a workstation (terminal Server) but it works fine when running Sage100 directly from the server. No users are logged into the company, nothing shows on master console. If I try to go to options for any module from the terminal server workstation, I get the typical ""task in use"" message. similarly if I try to run PE processing in any module I get a message **The file PO PurchaseOrderHeader is being used by another task and cannot be opened** (different table listed depending on the module). But if run Sage100 from the server everything works fine. The user must have run PE processing in December so this apparently just happened in the last 30 days or so. Anyone ever seen this? I'm thinking maybe a network permissions issue but I'm not sure what to look for or what to tell their IT staff to look for.


  • 2.  RE: Odd one. Sage 100 Standard version 2015. I cannot

    Posted 01-31-2018 18:27
    I actually don't know the exact answer, but the timing (within last month) is suspicious. I'd look at the suggestion in Sage's Defect KB article 106266, about Microsoft Windows Update (KB4051034) and(KB4054518). They are at least easy enough to remove and then retest.


  • 3.  RE: Odd one. Sage 100 Standard version 2015. I cannot

    Posted 01-31-2018 18:31
    that's a good thought maybe if I apply the hotfix?


  • 4.  RE: Odd one. Sage 100 Standard version 2015. I cannot

    Posted 01-31-2018 18:35
    Yes, I forgot that Sage has some hotfixes available at the bottom of that article. I have two customers I'd like to do that for (with older versions), but I haven't done it yet.


  • 5.  RE: Odd one. Sage 100 Standard version 2015. I cannot

    Posted 01-31-2018 19:39
    Have you rebooted everything?


  • 6.  RE: Odd one. Sage 100 Standard version 2015. I cannot

    Posted 02-01-2018 04:55
    I could not reboot the terminal server last night - too many users were logged in. I ran what I needed at the server and I'll have IT reboot it today or tonight and see if that resolves the issue. It just seems odd to me.