I mistakenly upgraded all of my files from 9.8 to 13.1. Having a problem with some files being recognized by software

SOLVED

I mistakenly upgraded all of my files from 9.8 to 13.1. In the process, a number of files could not be "renamed" and thus did not upgrade. I am unable to access job cost records and unable to process payments in Accounts Payable. The File Doctor report mentions using the Windows file tool to rename the problem files and then to try upgrading again. Has anyone else experienced this kind of problem?

  • 0

    This is the message on the upgrade report -

    Unable to rename C:\**\Data\000000001ABM to correct file name C:\**\Data\master.ABM.  Original data file is stored as C:\**\Data\master.ABM134. Use Windows file tool to rename the files and retry the upgrade.

  • +1 in reply to ORL
    verified answer

    Hi ORL,

    If some of the files were upgraded to 13.1, you will either need to continue with 13.1 or restore the data from a backup. There's not a way to roll them back once they are upgraded.

    You can try to rename the affected files to see if you can get back up and running data.

    In your data folder, you can use windows to rename the 000000000001ABM to Master.abm. In the PVData subfolder there will be a 000000000ABM folder, rename that to Master_abm.

    Repeat this for any other files. You may want to look at the data files in the Construction Sample Data folder as a reference for what the default names should be.

    Alternatively, you can restore the whole company from backup.

  • 0 in reply to Jesse Gordon

    Jesse,

    Thank you so much!  I followed your instructions and was able to regain access to all of my data.  You're a lifesaver!

  • 0 in reply to Jesse Gordon

    Good afternoon Jesse,

    After renaming the files that did not upgrade, everything worked fine.  However, my computer was shut down last night and when I restarted it this morning and tried to sign in to Sage, it responded with 2 messages before closing the program completely.  The first message reads:

    This program has quit. I/O Error. Pervasive status code 3012.  Local engine is not accessible to the MircroKernal router. 

    And the second reads:

    You cannot open this application because the security files have not been upgraded.  If the problem persists, ask your administrator to run Sage.Application.ConfigurationHub.exe on the server.

    Is there a way to fix this or to get around it?

    Thank you

  • 0 in reply to ORL

    Hi ORL, 

    PSC 3112 errors mean that the system is not able to connect to the database on the server. Rebooting the server and the workstation usually resolves this. 

    If the error persists, you can search for "Pervasive Status Code 3112" in the knowledgebase at www.sageKB.com for further troubleshooting.

    Thanks!