How to troubleshoot Sage 50 error “New periods could not be assigned” ?

How to troubleshoot Sage 50 error “New periods could not be assigned” ?

Emma Asked on December 4, 2017 in Sage 50.
Add Comment
  • 1 Answer(s)
    Best answer

    Unable to assign new periods while completing the year end wizard? Are you facing an error message that says “New periods could not be assigned”? Well, this error message indicates that the closing of the year end process is encountering a problem while assigning new periods to each transaction in the system and requires manual intervention. The problem arises either because the periods are not being created correctly or they can’t be correctly assigned during the year end wizard.

    But, don’t worry! The error message can be easily fixed by following the troubleshooting steps mentioned below. However, you must always create a backup of your data before performing the solution. Also, if necessary, you can seek expert assistance from our Sage support technicians by dialing our toll free Sage Support Number 1 888-489-0694 We can help you fix the error message within minutes to help you get going.

    Steps to resolve the error message

    Step 1: Restore backup and try closing the year again

    1. Restore the backup that you have created before closing the fiscal year.
    2. Now go to Company Information and make a note of the company Directory.
    3. Close Sage 50.
    4. Browse to your company folder by following the below mentioned path:

    \Program Files\Sage Software\Company

    1. Keep files that end with DAT, DDF, PTB, PWP, CAX, MKD, a VERSION.TXT , KMSKeys.xml and DETAILS.INI , CrystalReports.udl, *.PRT , and ~PVSW~.LOC file. Delete all other files.
    2. Delete the following files also, if present:
    • DAT
    • DAT
    • DAT
    • DAT
    • DAT
    • LOC
    • DAT
    • DAT
    1. Now open Sage 50 and try to close the fiscal year again. If the problem still persists, restore to the backup made earlier and proceed to Step 2.

    Step 2: Data Verification

    1. Click on File.
    2. Select Data Verification.
    3. Now select the option for Both Tests and click Start.
    4. Create a back up by clicking Save when prompted.
    5. Once the test is complete, try closing the Fiscal Year again. If the issue still persists, proceed to Step 3.

    Step 3: Chart of Accounts / Journal Synchronization

    Note: Before running any integrity checks, always ensure that you are on the latest batch of your release. In order to check updates, go to Services and select Check for Updates.

    1. Click Start and select Run.
    2. Type “C:\Program Files\Sage Software\Peachtree\Peachw.exe” –i
    3. Click to open Sage 50. Integrity Check will now be available from the File menu.
    4. Now open your Company.
    5. Create a complete backup of your data.
    6. Change your accounting period to Period 1.
    7. Now select File from the menu and select Integrity Check.
    8. Click Continue to proceed further.
    1. Select Reindex Files box.
    2. From the Reindex File List, select Jrnl Header and click OK.
    3. Access the Integrity Check and click Continue.
    4. Once again select Reindex Files box.
    5. From the Reindex File List, now select Jrnl Rows and click OK.
    6. Access the Integrity Check and click Continue.
    7. Select Chart of Accounts/Journal box under the Data Synchronization Tests section and click OK.
    8. Check if your issue has been successfully resolved.

    That’s it. By following the aforementioned steps, you can easily fix the Sage 50 “New periods could not be assigned” error. But, if you are still facing the problem or if there are issues while performing the steps, give us a call. Dial our toll free Sage Technical Support number 1 888-489-0694 and our friendly technicians can help you resolve the error message in no time. Not just that, they will also optimize the speed and performance of your computer to help you make the most of technology. For efficient troubleshooting of all Sage 50 errors in minimum time, call Sage Accounting Solution today.

    Support Team Answered on December 4, 2017.
    Add Comment
  • Your Answer

    By posting your answer, you agree to the privacy policy and terms of service.