HomeTallyPrimeManage Your DataData ManagementData Migration & Data Corruption - FAQ

 

Explore Categories

 

 PDF

Data Migration – Release 3.0

This section lists some of the frequently asked question (FAQ) specific to Data Migration in TallyPrime Release 3.0.

The Company Number is 6 digits in TallyPrime Release 3.0 after migration to break the compatibility of of that data in the earlier TallyPrime release. However, data migration retains a copy of the 5 digit company data so that you can use the same in the supported earlier release of TallyPrime.

In a multi-user setup using TallyPrime, all client and server nodes must be updated to the latest release to ensure seamless data functionality and synchronization across all nodes. If you’re experiencing issues locating your company data, it’s advisable to upgrade your TallyPrime server license. For guidance on updating your server, please refer to the Update TallyPrime Server License topic.

In certain cases, after migrating company data from TallyPrime 2.1 to TallyPrime 3.0, you might encounter an issue where the data is not visible in TallyPrime 2.1. This occurs because TallyPrime 2.1 backs up the company data folder during migration, adding a suffix (migrated to 3.0) to the folder name. To make this data visible in TallyPrime 2.1, simply remove the added string (migrated to 3.0) from the data folder name.

    1. Gateway of Tally > F1 (Help) > About and press Enter.
      About screen opens.
      Under Data Information you can see Location of Company data.
      Data Path in TallyPrime
    2. Note down the company data location path and open it on the desktop.
    3. Rename the required company data folder by removing the string (migrated to 3.0).

Once removed, the company data will be visible in TallyPrime 2.1.

Yes. When you migrate your data to Release 3.0, TallyPrime retains a copy of the 5-digit company. You can continue to use this data in the compatible release of TallyPrime as you used to.

No, it is not mandatory to take a backup of the data while migrating to Release 3.0. Therefore, the option to take a backup before migration is set to No by default. However, as a recommended practice, TallyPrime allows you to also take a backup during migration. For more information, refer to the Data Migration topic.

By default, the company data is created under the same data folder that has the corresponding 5-digit company data.

Currently, TallyPrime does not allow setting or changing the path for the data during migration.

We are expecting an increase in the size of the migrated data in Release 3.0. Therefore, TallyPrime identifies the available disk space in your computer and analyses the required disk space for migration and backup. In case there is less disk space to migrate or backup the data, TallyPrime prompts you about the same during migration.

In this situation, you can ensure that the required disk space is available in your computer, before you migrate or back up the data. For more information, refer to the Low disk space during migration & backup section under the Data Migration topic.

Yes, all the existing edit logs for masters and transactions will be available in the migrated data. However, if TallyPrime identifies exceptions in any of the masters or transactions during migration, the edit log details for those masters and transactions are lost.

For more information on the impact on Edit Log due to migration, refer to the Impact of migration on Edit Log section under the Data Migration topic.

Yes. The experience of moving data from TallyPrime Release 3.0 to TallyPrime Edit Log Release 3.0 and vice versa remains the same as it was in TallyPrime Release 2.1.

Yes, TallyPrime allows you to migrate data also from Tally.ERP 9 and Tally 9 versions to TallyPrime Release 3.0. For more information, refer to the Migrate Company Data from Tally 5.4, 6.3 and 7.2 to TallyPrime section under the Data Migration topic.

During migration, the progress bar displays the count by considering deleted vouchers/masters, internal master types (such as Income Tax Classification) and so on, which are not part of the migration success screen.

The migration process creates some internal data, known as purpose data, for the company to ensure better performance of the GST-related reports and relevant Edit Log reports. Therefore, there is an increase in the size of the migrated data.

The process for migrating a group company is similar to how you migrated in the earlier releases. On migrating a group company, each member company gets migrated one after the other.

Depending on the total size of the member companies, it is recommended that you maintain sufficient disk space in your computer before migrating a group company.

This can happen due to the following reasons:

  • One or more files from the company data folder is already in use. Ensure to close the files and check if the migration is progressing.
  • One or more files from the company data folder are set as blacklisted for any antivirus software in your computer. Remove the files from the list, and check if migration is progressing.
  • The company data folder has folder-level restrictions such as deletion, copy, read, and so on. Remove such folder-level restrictions from the company data folder and migrate the data again.

The latest release of TallyPrime makes your data migration experience seamless. Whenever you need to move from TallyPrime Release 3.0 to TallyPrime Edit Log Release 3.0, migrate your data similar to how you migrated from the earlier release of TallyPrime. For more information, refer to the Data Migration topic.

No, the vouchers or masters that are part of the exceptions report do not participate in the books of accounts. Once you have resolved the exceptions in those masters and vouchers, they will start appearing in your books of accounts.

To capture any exception in data while importing or synchronising:

  • Press Alt+O (Import) > Configuration > and set Behaviour of Import when Exceptions exist to Record Exceptions and Import.

Yes. In any of the exceptions report, press Ctrl+H (Change View) > select Exception-wise and press Enter.

  • In the Sync Exceptions report, you can also press F4 (Rule) > select the Rule (such as Master RuleTransaction Rule, or All Rule Types) to view the exceptions specific to the selected rule.

Vouchers and masters that are part of the exceptions report do not participate in your financial reports and Books of Account, until they are resolved.

No. Vouchers and masters that already are part of any exceptions report cannot be exported to another machine. The same is also applicable in case of data import.

Once a master/voucher becomes part of the exception report, TallyPrime erases any previously available edit log information for the same. Once you resolve the exceptions, TallyPrime will create a log for resolving the master/voucher as Created due to Data Resolution.

Once a master/voucher becomes part of the exception report, TallyPrime erases any previously available edit log information for the same. Such masters/vouchers may no longer be authentic and reliable according to the company rules. Once you have resolved the exceptions, these masters/vouchers can continue to participate in the Books of Accounts with any new edit log, as and when applicable.

Recording of data exceptions are currently supported for the Repair, Migrate, Sync and Import features. We will consider recording data exceptions during Split in a future release.

TallyPrime will record all exceptions during Import, if the imported data does not follow the rules and configurations set for the Company, such as Books beginning date, Zero-valued transactions, and so on.

Data Migration – Release 2.1 and Earlier

The FAQ under this section are applicable to data migration in Release 2.1 and earlier versions of TallyPrime

If you are using older releases of Tally (such as 5.4, 6.3, and 7.2), you cannot migrate your data directly to TallyPrime. You will have to first migrate your data to Tally.ERP 9, and then migrate to TallyPrime.

To migrate the data from Tally 5.4/6.3/7.2 to Tally.ERP 9, and then to TallyPrime, follow the steps shown below:

  1. Take a backup of the Tally 5.4/6.3/7.2 data by following the required backup process.
  2. Copy the required company folder of 5.4 or 6.3 or 7.2 to Tally.ERP 9 data folder.
  3. Start the migration tool (tally72migration.exe) from the location where it is available. You need to download the tool from Tally Solutions website.
  4. Select Migrate Data in the Tally.ERP 9 Data Migration Tool.
  5. Enter the company data path in the Directory field, and select the company in the Name field.
  6. Press Enter when the Rewrite? message appears.
  7. Press Enter when the message Backup before rewriting? appears. The data is backed up before being rewritten to Tally 7.2 format for migration.
  8. Press Enter when the Migrate? message appears.
  9. On successful migration, the message Migration Completed, Check Statistics appears. Compare the statistics and ensure that data migration is complete.
    Note: The migrated company number is prefixed with an additional 0 and appears in five digits. When you open the data in the latest release of Tally.ERP 9, you will be prompted to migrate to Release 6.x. Press Enter to migrate.
  10. Copy the data folder migrated to the latest release Tally.ERP 9, to the TallyPrime data folder.
  11. Open TallyPrime. Press Alt+F3 (Select Company) to open the List of Companies. You can see the status Migration Required against the migrated company folder, which you had copied from Tally.ERP 9 data folder.

    Alternatively, you can also migrate your data by pressing F1 (Help) > Troubleshooting > Migrate.
  12. Select this company and press Enter. If the company has a username and password, you will be asked to enter the details.
  13. Press R (Migrate) to continue. If you want to alter the backup path and data location before migrating, then press C (Configure).

    After migration is complete, your company data is ready to be used in TallyPrime.

A group company created in Tally 7.2 cannot be migrated to TallyPrime. It is suggested to migrate the individual companies to TallyPrime, and then group them once again in TallyPrime to create a group company. However, it is advised to take a backup of the data before migrating.

Customisation done in Tally 7.2 will not work in TallyPrime. You need to migrate the customized programs to a format that is compatible with TallyPrime. To migrate the program files (.tcp files) follow the steps given below:

  1. On installing TallyPrime in the existing folder the .tcp will automatically get converted to a format compatible with TallyPrime.
    Or
    Start TallyAdmin tool.
  2. Click File Format Conversion.
  3. Select TCP (Tally Compliant Format).
  4. In the Source File(s) specify the path and filenames.
  5. Click Convert.

The specified file is converted to new format compatible with TallyPrime, and the original file is retained as backup with .bak extension.

Or

In case the customized programs have an extension .txt, it is suggested to mention the correct path in Load selected TDL files on startup in TDL Configuration screen.

Do the following before commencing data migration:

  1. Ensure that tally9.exe and tally72migration.exe are available in the same folder.
  2. Close all other applications that are open before commencing migration.
  3. Go to File menu in Internet Explorer and uncheck the option Work offline.
  4. Scan for virus on the system.
  5. In case the data size is too large it is advisable to use a system with higher configurations.
  6. Disable real time protection on your anti-virus software.

To resolve this problem, in the stock item alteration screen, select the costing method as FIFO Perpetual, also match the Unit of measure and Godown.

Reason

This error occurs when the Unit Symbol is altered to numeric/alphanumeric. For example, Nos to Nos1 or Kgs to KgsA (Gateway of Tally > Alter > Units).

Solution

Follow the steps given below to resolve this issue.

  1. Create a new company in Tally 5.4/6.3/7.2 (for the same financial year and with features similar to that of the migrating company).
  2. Export the Masters and Vouchers, and import them to the newly created company.
  3. Migrate the newly created company data to Tally.ERP 9 and then to TallyPrime.

Reason

This error might occur during data migration.

Solution

Increase the screen resolution by following the steps given below:

  1. Right click the desktop.
  2. Select Properties.
  3. In the Display Properties window, click Settings tab.
  4. Increase the Screen resolution to 1366 x 768.

Data path in client system can be changed when data path in server system is changed.

While loading Tally in client system, if no companies are available on disk:

  • Check if data is shared from the server machine.
  • Check whether the user in client system has rights to access the data folder.
  • Check the data path configured in client system.

 

To configure the data path

  1. Share the data folder from the server system. Provide full permission to access the data folder. Click here to view the data sharing process.
  2. Go to Start > Run > type Server system name/ip followed by (i.e back slash) and press Enter. The folders which are shared from server machine will appear.
  3. Open respective Tally data folder and copy the address path.
  4. Load TallyPrime in client machine, and press Alt+F1 (Help) > About > under Data Information, select Location of Company data and press Enter.
  5. Change the data path by providing the new data path.
  6. Press Enter to view the updated data path.
  7. Press Esc to save.

If you have migrated your data to TallyPrime, you cannot open the same data using an earlier release of Tally. Therefore, it is recommended that before migrating your data, take a backup or copy of your data and open the backed-up data in the earlier release, if needed.

Cause

This error occurs when data from a higher release of TallyPrime is loaded in a lower release.

Solution

Load the data in the same release of TallyPrime that was used earlier. We recommend that you download the latest release of TallyPrime, install it in a new folder, reactivate, and restore the data backup.

Cause

This error appears while splitting company data when a third-party software is used for data backup, and .tsf files are saved by this third-party application for backup.

Solution

Add the .tsf files in the exclusion list of the data backup software.

Note: Contact your system administrator to add files to exclusion list.

Upgrade to TallyPrime and repair your data to resolve this issue.

The data may display Repair Required, as shown below:

Press Enter on the data > click Yes, to Repair. The data will be repaired.

Solution

Backup the current company data and repair.

Data from Tally 4.5 has to be migrated to Tally 7.2, then to Tally.ERP 9, and then to TallyPrime. The tools required to convert data from 4.5 to 7.2 are available on the Tally website.

Procedure for converting data from Tally 4.5 to TallyPrime involves the following steps:

  1. Converting the data of Tally 4.5 to Tally 7.2 compatible data, using Tally 4.5 to Tally 7.2 data conversion utility.
  2. Migrating the Tally 7.2 compatible data to Tally.ERP 9, using Tally 7.2 data migration utility.

 

Convert data from Tally 4.5 to Tally 7.2

  1. Download Tally 4.5 data converter utility.
  2. Run the Convert45to72.exe and extract the files (WCVTALLY.EXE, TW45250.DLL, and CNVTALLY.DAT) to Tally 4.5 application folder.
  3. Double-click the file WCVTALLLY.EXE (the icon will be identical to Tally Icon). The Company Info screen appears. (You can also execute this file from the command prompt click Start > Run > type C:WCVTally.EXE C:)).
  4. Select the company to be migrated.
  5. Click Yes in conversion confirmation message.

Note: The Conversion utility will run in black and white only (even if you have a colour monitor).

 

Migrate Tally 7.2 compatible data to TallyPrime Data

  1. Install Tally.ERP 9 and TallyPrime.
  2. Download the tally72migrate.exe from Tally website, copy it to the Tally.ERP 9 application folder.
  3. Double-click the tally72migrate.exe. The utility will launch the Tally Data Migration Tool and Tally.ERP 9.
  4. Select Migrate Data in the Migration Company screen.
  5. Specify the directory where Tally 7.2 compatible data (Tally 4.5 converted data) is located in the field Directory.
  6. Select the company to be migrated from the List of Companies.
  7. Click Yes in the message displayed to start migration. The status of migration from Tally 7.2 to Tally.ERP 9 is shown in the Migration Messages pane.
  8. Press any key in the Migration Completed Check Statistics message. A Congratulation message appears confirming completion of data migration.
    Note: If any error occurs during migration, it gets logged into migration.err file, which is automatically generated in Tally.ERP 9 application folder.

    The migrated company is by default saved in the directory which was specified in the directory field (refer point 5 above). The migrated data folder is prefixed with a 0 and appears as a 5-digit number. For example, if the company folder number before migration was 0099, after migration it would be 00099.

  9. Now your migrated data is ready to be migrated to TallyPrime.
    Note: If you want to migrate Tally 4.5 data to Tally 9, the process is same. Instead of installing Tally.ERP 9, install Tally 9 and follow the above process.
  10. Copy the data folder migrated to Tally.ERP 9 to TallyPrime data folder. Migrate the data to TallyPrime.

Cause

While migrating data from 6.3 or earlier releases, this error may occur when you enter strings other than numerals in the Value Basis field under Additional Accounting Entries in the Voucher Type Class screen.

Solution

Open the company where this error occurs, and correct the data entered in the Value Basis field in the Voucher Type Class screen.

This will fix all the XML import errors that occur while importing, migrating, or synchronizing data.

This error appears on the client machine.

The tmessage.tsf error appears as shown below:

Solution

  • Ensure that all the files/subfolders in the data folder are given full access to relevant users.
  • Allow full access permission to all the users (working on TallyPrime).
  • Check the network connectivity.

Cause

When the E-mail from mentioned is wrong.

Solution

Verify the email id entered in E-mail from field, ensure it is correct and then proceed with emailing.

The table below shows the list of files which are part of the database structure used in TallyPrime, along with a brief description or function of the respective data file.

Data Files for
File Contents/Function
Tally 5.4/6.3/7.2 Tally 9/Tally.ERP 9/TallyPrime TallyPrime 3.0
Company.500 Company.900 Company.1800 Contains Company Profile along with Statutory Information related to the respective company
CmpSave.500 CmpSave.900 CmpSave.1800 Is the Backup copy of Company.900
NA NA AddlCmp.1800 Non-frequent accessed information of company – legacy use (for e.g. MCA).
Manager.500 Manager.900 Manager.1800 Consists of master level information such as Groups, Ledgers, Item Masters, etc.
Tr01263.500 TranMgr.900 TranMgr.1800 Stores the transactions entered. In earlier versions of Tally, there was a transaction file created for every month. Due to data structural changes made in TallyPrime, only one file is created which is available across financial years.
Tr01264.500
Tr01265.500
Tr01266.500
TrnLots.500 LinkMgr.900 LinkMgr.1800 Contains the detailed information on bill references, order numbers, batch numbers and tracking numbers. In earlier versions of Tally individual files were created for bill references, order numbers, batch numbers and tracking numbers.
TrnOrds.500
TrnRefs.500
TrnTNos.500
NA NA SecTran.1800 This file stores the records corresponding to Summary objects, Exchange Activity, Export Summary, Return Transactions (both Accounting and Statutory).
NA NA Status.1800 Has Status information (for e.g. Include status/Exclude status etc.) for both vouchers as well as Statutory.
NA NA Aggr.1800 Used for storing aggregate information (key and accumulated value used for instant report for Statutory related reports).
NA NA CfgRept.1800 Has Report Configurations (used when Save View is performed).
MsgRead.TSM TACCESS.TSF TACCESS.TSF Used for controlling access to the database.
Exclusv.TSM TEXCL.TSF TEXCL.TSF Used when database is accessed for administrative functions.
MsgKeep.TSM TSTATE.TSF TSTATE.TSF Tracks the state of database and ensures that data is safely written to the respective files.
  TMESSAGE.TSF TMESSAGE.TSF Used for two-stage writing ensuring consistency and persistence.

Query

Record Insertion Failure in database error occurred while loading a company/saving a voucher in TallyPrime. How to avoid this in future?

Solution

When this Record Insertion error is displayed, it is suggested that you follow the steps given below:

  1. Backup your data.
  2. Press Alt+F1 (Help) > Settings > Startup > set Load companies on startup to No.
  3. Perform a simple repair by pressing Ctrl+Alt+R.
    Alternatively, you can press Alt+F1 (Help) > Troubleshooting > Repair.
  4. In case the problem persists, it is suggested to perform a Zero command rewrite.
  5. We suggest an upgrade to latest release.
  6. In case the problem persists contact Tally Support.

Cause

This message is displayed while repairing the data.

Solution

While repairing the data, check if there is sufficient space in the hard disk or any external drive where the data is located.

Note:

The minimum free space required while repairing the data should be double the size of the data. For example: If the data size is 4 MB, then the free space available should be at least 8 MB.

It is recommended to repair the company data stored in a local disk, rather than the data stored in an external drive.

Accessing TallyPrime data from external drivers is very slow because there might be differences between the USB ports.

The USB ports USB 3.0 is 10 times (572 megabytes per second) the speed of USB 2.0 (57 megabytes per second). However, in order to get better speed, plug your USB 3.0 device into a USB 3.0 port. If the port is 2.0, and the device 3.0, than the speed will go down from 572 MBps, to 57MBps (and vice versa). This means USB 2.0 and USB 3.0 are compatible with each other, but you will just get slower speed when you are using a combination of them, and not just 3.0.

The speed of USB 3.0 also provides more power to devices that require higher amount of power to operate. It can provide 50% more power than USB 2.0 does through the cable itself. USB 3.0 reduces the time required for data transmission. Hence, the data processing becomes faster compared to the USB 2.0, and may differ from one to another i.e. USB 2.0 and 3.0, in terms of power and speed.

For more information on USB 3.0 visit https://www.usbgear.com/

Query

How to handle the error – Data path specified for more than one Tally.ini, displayed on clicking the tally72migration tool?

Solution 1

The error may be due to multiple data paths in the file, Tally.ini. Steps to remove additional data paths:

  1. Go to Tally application folder.
  2. Open the file, Tally.ini (file type is Configuration settings).
  3. Delete the second data path/location of data files, if any (not the primary data path).
  4. Save the Tally.ini file.

Solution 2

Change the settings for Default Companies in the file, Tally.ini. Steps to change the settings:

  1. Go to the Tally application folder.
  2. Open the file, Tally.ini.
  3. Set Default Companies to No.
  4. Save the Tally.ini file.
  5. Load the migration tool again.

Cause

  • A system process is deleting data files.
  • Virus.
  • Manual deletion by a user.

Solution

The solution for this issue is to enable system audit, which will help the system admin to identify the reason for deletion.

  1. Open Control Panel in the system, and navigate to Administrative Tools.
  2. Open the Local Security Policy.
  3. Expand Local Policies appearing on the left side > click Audit Policy.
  4. Double click the Audit object access which appears on the right side.
  5. Enable Success and Failure as shown below.
  6. Click OK to save the changes.
  7. Right-click the TallyPrime data folder. Select Properties. Go to Security tab and click Advanced as shown below:
  8. Go to Auditing tab, and click Continue as shown below:
  9. Click Add.
  10. Click Select a principal.
  11. Type Everyone > click Check names. You will see that the word Everyone will get underlined.
  12. Click OK.
  13. Auditing entry for data screen opens. Click Show advanced permissions.
  14. Select the options as shown below:

    With this configuration, all the users will be disallowed from deleting the data files.
    Further, to find out the reason for deletion of any data file, right click on My computer. Click Manage. Expand Event Viewer appearing on the left side. Select Windows Logs > under Windows Logs select Security as shown below:

    You can keep the cursor on the bottom part of the screen and press Ctrl+F. In the Find window that opens, paste the data path for which you have enabled audit and click on Find Next as shown below:

    The search result will display the details of deletion.

To ensure data is not shared with client systems in offline mode, you can disable caching of shared folders.

  1. Right-click the data folder and select Properties.
  2. Navigate to the Sharing tab, and click Advanced Sharing in the data Properties window as shown below:
  3. Click Caching in the Advanced Sharing window as shown below:
  4. Select the option No files or programs from the shared folder are available offline in the Offline Settings window as shown below:
  5. Click OK to accept the settings.

Cause

This message appears if you try to split the company data when TallyPrime is in Educational Mode.

Solution

Configure your existing license or reactivate your license.

This error might be displayed even after configuring the port number for ODBC, in the About page of TallyPrime.

Cause

The port number specified may already be in use.

Solution

  1. Press Alt+F1 (Help) > About > select Client/Server and ODBC Services and press Enter.
  2. Enter a different Port number.
  3. Press Enter to restart TallyPrime.

Cause

This error occurs when the backup process is not completed properly, leading to a partial or incomplete backup file, or when the disk (external drive) containing the backup file is corrupted. Further, due to limited space on the external drive, only a part of the backup may be saved on the file.

Solution

Click Yes in the error message to recover data. In case the recovery process is not successful,

  • Restore an earlier backup file and re-enter any missing data.
  • Contact Tally Solutions with the data. In case the data is recoverable, the recovered data will be sent to you.

For computer in which the operating system installed is Windows XP or a higher version:

  1. Right-click the TallyPrime icon, and select Run as administrator.
  2. The Select Company screen appears. Select the required company from which you want to extract the data. The About page displays the Client/Server with ODBC Services. If the port number is not configured, you can configure it by following the steps given below:
    • Press Alt+F1 (Help) > About > select Client/Server and ODBC Services and press Enter.
    • Enter the Port number. By default the port is set to 9000, as shown below:

      Note: In case the port number mentioned is occupied by another application, you need to provide another port number.

Malware slows down your computer and corrupts the data. Such data cannot be recovered. If you have the system backup, you can restore it, and check if it can be used.

In one particular system data is not getting shared/displayed. The system could be a laptop which has not been configured to the same domain. If there is mismatch between the domain, the data won’t get shared. To resolve this:

  1. From desktop, click on Start > Control panel > Network and Internet.
  2. Click on Home Group.
  3. Click on Change advanced sharing settings.
  4. Under Domain, select Turn off the password protected sharing.
  5. Click on Save Changes and re-login to system. Now you will be able to share/display the data.

Cause

This particular error may occur, if you do not have full access to the Tally Data folder or the device is write protected.

Solution

Ensure that the Data folder is shared for full access, or the device on which you wish to create the Company is NOT “write protected”.

In case the error persists, send an email to support@tallysolutions.com.

It is suggested to restore the earlier data backup and continue working. In case the backup restored is up to an older date, the data until the current date needs to be updated manually. In case you do not have a backup, we recommend that you start taking a backup every day.

Checking for bad sectors on hard disk helps you identify sections of hard disk that are not being utilised for storing data, and is wasted. Proper data on hard disk space usage will help you manage your data better and system to perform read write functions effectively.

  1. Open command prompt.
  2. Enter chkdsk on the command prompt screen.
  3. Check the amount of space (KB) in bad sectors.
  4. De-fragment the hard disk based on the results in the report, if required.

Note: Ensure system backup is created before performing de-fragmentation.

Cause

This message is related to the medium on which the backup is taken. The prompt is Tally’s unique way of ensuring that the user has already checked and wants the Tally backup to overwrite all the information available on the medium (such as floppy, zip diskette, and so on).

Solution

Select Yes if you wish to overwrite the available information.

Cause

This error appears during data backup process if the destination hard disk or drive is affected with virus.

Solution

Scan the hard disk or drive and check.

Cause

This error appears while opening a company, if the file size of TranMgr.900 is 1 KB.

You will not be able to use this data.

Solution

The company will open only when the file size of TranMgr.900 is more than 1 KB, depending on the data entered.

Restore the data backup taken earlier and check the file size of TranMgr.900. If it is more than 1 KB based on the data entered, you can open the company. If not, try to restore the data backup taken prior to that.

Post a Comment

Is this information useful?
YesNo
Helpful?