Sage 100

 View Only
  • 1.  I have a customer on Sage 100 2017 Premium. They r

    Posted 06-01-2018 10:10
      |   view attached
    I have a customer on Sage 100 2017 Premium. They recently updated their server with Windows Updates (Azure) and now report random error messages which start with ""A file is in use by another task"" (see screenshot). They are able to end through and eventually go back into SO Entry. They also use Accellos which looks as if it might be the first error with file SO254_RBDownloadRoutines.pvc Any thoughts? I've suggested repeatedly that they look at ant-virus, anti-malware and any type of continuous backup process that could be running. They say none of that is the issue.


  • 2.  RE: I have a customer on Sage 100 2017 Premium. They r

    Posted 06-01-2018 13:09
    OMG, I just got done emailing off to Scanco re someone who keeps getting an error about file in use when trying to sync a completion from Xscan. The file in use is a WO file, which made me think maybe that SYINIT file, but we replaced that with no change. I""m going to go see if this client had a windows update.


  • 3.  RE: I have a customer on Sage 100 2017 Premium. They r

    Posted 06-01-2018 15:45
    Can confirm that the customer states they are not doing any updating - just going into the system and seeing this message. They say they can click end on the error message and then go back into Sage without getting the error. This customer claims no Anti-Virus or Malware scanning in use. They are on Azure but that's not something new (I think they've been on it 1+ year).


  • 4.  RE: I have a customer on Sage 100 2017 Premium. They r

    Posted 06-04-2018 10:12
      |   view attached
    It is possible, since they have a third-party integration, that they could be experiencing a SQL Deadlock. If that is what is happening, the user would receive the 'File in use by another task' error message. We have experienced this issue before with another client where ScanForce and Starship were both installed and one of the applications was locking the record while the other was attempting to update. You can determine what is going on by running a SQL trace profiler or watch the process monitor in SQL Management Studio, when the event happens (assuming it can be duplicated on demand/consistently).