Sage 100

 View Only
Back to discussions
Expand all | Collapse all

Disaster Recovery and file locking

  • 1.  Disaster Recovery and file locking

    Posted 08-05-2020 16:50
    Client was running Sage 2016 Advance PU5 when server crashed. IT was able to recover an image of the server and some backups. They restored one of their backups. I did a clean install of 2016, applied PU5 and then migrated the restored system files and data to the clean install. Checked the GL data, but the last fiscal year was 2017. This backup was too old.

    They were able to get the MAS_XXX company data folder from around the time the server crashed. I copied that MAS_XXX folder into the MAS90 folder, but it looks as though multiple files must be locked. I'm being prompted to convert data, but that shouldn't be the case, as the module and company files are all on 5.30.5, so there's no need to convert. When I try to convert I get and Error #0 Record/File busy Program SY_CompanyConversion.pvc line 332

    Is there a software that would be able to check the properties of a file and discover whether or not it's locked? I've used computer management to look for locked files but there's none. ​​

    ------------------------------
    John Kerr
    Net at Work
    ------------------------------


  • 2.  RE: Disaster Recovery and file locking

    Posted 08-05-2020 16:58
    Was the backup from version 5.30.5?
    If not, it is possible the records migrated in SY_Activation have the older level and that is why you got the prompt to convert.
    As for dealing with lock files, have you tried restarting?
    You can also try SysInternals' Process Explorer to view what might be locking files.
    https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer


    ------------------------------
    David Speck II
    Tennessee Software Solutions
    ------------------------------



  • 3.  RE: Disaster Recovery and file locking

    Posted 08-05-2020 17:41
    I checked SY_Activation for the company key that I'm trying to convert and all levels are 5.30. There are old records in there for company codes that have been created and deleted over the years though.
    The backup provided to me was from 5.30

    ------------------------------
    John Kerr
    Net at Work
    ------------------------------

    Original Message


  • 4.  RE: Disaster Recovery and file locking

    Posted 08-05-2020 17:49
    When restoring from backups be sure to double-check NTFS permissions and the "read only" file attribute.
    Within a disaster recovery situation, AV software may be on full volume.  Set AV exclusions per the Sage KB article.
    (Dealing with anything less than a full MAS90 folder backup will be an exercise in frustration... good luck!).

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 5.  RE: Disaster Recovery and file locking

    Posted 08-05-2020 17:06
    You might try coping the data to your office computer, convert the data, then copy the converted data back to the client server.  It may avoid unknown programs locking the tables.

    ------------------------------
    Doug Higgs
    Midwest Commerce Solutions, Inc
    (312) 315-0960
    Assistant to the Traveling Secretary
    ------------------------------



  • 6.  RE: Disaster Recovery and file locking

    Posted 08-05-2020 17:51
    REMINDER - we are updating the 90minds.com site today and you may have intermittent access until the change over is completed.

    ------------------------------
    Moira Goggin
    Executive Director
    90 Minds, Inc.
    ------------------------------

    Original Message


  • 7.  RE: Disaster Recovery and file locking

    Posted 08-05-2020 17:57
    Thanks for the reminder @Moira Goggin​

    ------------------------------
    John Kerr
    Net at Work
    ------------------------------

    Original Message


  • 8.  RE: Disaster Recovery and file locking

    Posted 08-05-2020 18:47
    I'm trying to update an existing 2016 that I have saved locally to product update 5. After that I'll create the company code and then copy in my MAS_XXX data folder. Do you know which file I need to edit to make sure that I create the company with the same company key as my source company? Need to make sure the company key is identical, in order not to have problems when I copy the folder back.

    ------------------------------
    John Kerr
    Net at Work
    ------------------------------

    Original Message


  • 9.  RE: Disaster Recovery and file locking

    Posted 08-05-2020 19:07

    Hi John,

      The company key is in SY_Company.M4T in the MAS_System directory.   I have never seen references to company key in the data files unless it is premium.   

     

    Thank you,

     

    Bob Osborn

    ACI Consulting

    p 714.282.0378 ext. 402    f 714.282.0235

     

    Bob@ACIconsulting.com

     

     ACISignature1                  

    MCP_SE_Small.bmp

    This communication, including attachments, is confidential and may contain proprietary information intended only for the proposed recipient. Please notify the sender and delete this message if you believe that you have received this message in error or if you are not the proposed recipient. Unauthorized disclosure, copying, or distribution of the information is strictly prohibited.

     

     

     

     




    Original Message


  • 10.  RE: Disaster Recovery and file locking

    Posted 08-05-2020 19:34
    Thanks Bob
    I think there's a file which keeps track of the company keys. When you go into company maintenance and create a new company code, that file assigns the next sequential company key. I need to make sure that when I create my company record, it's generated with the same key that mine already has.
    Need to poke around in the system files.

    ------------------------------
    John Kerr
    Net at Work
    ------------------------------

    Original Message


  • 11.  RE: Disaster Recovery and file locking

    Posted 08-05-2020 19:36
    Assuming your intended key is higher than the new system, just keep creating and deleting company codes until SY_Company has the value you want.

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 12.  RE: Disaster Recovery and file locking

    Posted 08-05-2020 19:39
    Yes, I think that might be the way to go.

    Thanks @Kevin Moyes​

    ------------------------------
    John Kerr
    Net at Work
    ------------------------------

    Original Message


  • 13.  RE: Disaster Recovery and file locking

    Posted 08-05-2020 19:56
    I found it. SY_surrogate. Edit field 4 to be one less than the company key you need. Create the company code and it generates with the correct key.

    ------------------------------
    John Kerr
    Net at Work
    ------------------------------

    Original Message


  • 14.  RE: Disaster Recovery and file locking

    Posted 08-18-2020 10:53
    Message moved to Sage 100 community.

    ------------------------------
    Moira Goggin
    Executive Director
    90 Minds, Inc.
    ------------------------------

    Original Message


Related Content