My customization is missing after migrating to a new Server/Host.
Description
Cause

When a migration process is not completed or not completed successfully, it can result in missing customization. Company configured data is stored within the 9.5\Accounting folder on the Server or Host in the following subfolders:

  • Dict
  • Formula
  • Global
  • Inquiry
  • Misc (if the Tax.prx file is stored here)
  • Report
  • Screen
  • Security
  • Template

If you are using the Migration Tool and it appears to complete, but your customization is missing and the log file is not created and/or the Migration folder is not created within the Accounting folder, the permissions on the Share or the Folder at C:\ProgramData\Sage\Timberline Office may not be set correctly.

Resolution

Complete the migration process by running the Sage.STO.ServerMigrator utility (see Chapter 5: Server Migration in your User Guide).  If you've been using the Migration Tool and it still isn't completing successfully, check the permissions on the Share and/or Folder - the Share should allow Full Control to the Everyone Group, the folder should allow Full Control to your Timberline Users and/or Administrators you could also use the Everyone group.

If your old Server or Host is no longer available, you should:

  1. Restore/copy the 9.5 folder from the original Server or Host to your new Server or Host in a temporary location (e.g. C:\Customization\9.5).
  2. Share the folder you placed the 9.5 folder into (e.g. Customization).
  3. Run the Sage.STO.ServerMigrator and direct it to the share on your temporary location (e.g. \\NewServer\Customization\9.5).
  4. Complete the migration process for the Server only.

Additional information

  • You will need to manually migrate the company data and reassign access to non-administrator users.
  • If you have used the software on the new Server/Host prior to completing these steps, you will lose any customization changes made to the system prior to completing the migration and may want to Archive entries in your Log Viewer prior to completing the migration.
  • If the program still does not perform as expected, please contact Sage Support or your Business Partner.
Steps to duplicate
Related Solutions