Sage 100

 View Only
  • 1.  Customer called yesterday - Sage 100 2016.3 Standa

    Posted 04-11-2017 06:58
    Customer called yesterday - Sage 100 2016.3 Standard - trying to copy company, They get to JC and receive a file in use message and the copy stops. - Have reviewed Master Console to ensure nobody was in - Have rebooted Sage 100 server I've never seen Sage actually stop during the copy process like this (I always presumed if someone was in that it would just skip files). Anyone seen?


  • 2.  RE: Customer called yesterday - Sage 100 2016.3 Standa

    Posted 04-11-2017 07:07
    Anything in the LOCK folder?


  • 3.  RE: Customer called yesterday - Sage 100 2016.3 Standa

    Posted 04-11-2017 08:33
    Good thought. I removed all the LCK files , still getting ""All users must exit TST before performing this function"". Have tried the copy both while in the TST company and switching to another company code.


  • 4.  RE: Customer called yesterday - Sage 100 2016.3 Standa

    Posted 04-11-2017 08:35
    https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=44992&sliceId=1&cmd=displayKC&dialogID=35318&docType=kc&isLoadPublishedVer=&stateId=35328&docTypeID=DT_Article&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl


  • 5.  RE: Customer called yesterday - Sage 100 2016.3 Standa

    Posted 04-11-2017 08:43
    I don't know what was happening. Ultimately I deleted TST (which didn't happen automatically as it balked about a file in use in APxxx, so I took out the eFiling folder manually which seemed to be what was holding the remove data). After I took that eFiling out manually I was able to re-create TST and copy live to TST.


  • 6.  RE: Customer called yesterday - Sage 100 2016.3 Standa

    Posted 04-11-2017 09:22
    @WayneSchulz - I just experienced this same issue, and I, too, removed the eFiling folder from the Payroll module to get the copy data to work.


  • 7.  RE: Customer called yesterday - Sage 100 2016.3 Standa

    Posted 04-11-2017 17:11
    I always look for locked files in Computer Management, then look to see if FRx, SBI, Providex I/O, a scheduled import job or anything else might be interfering and reboot if none of that works. Though this year, I think a PEP file was the culprit once.