HomeTallyPrimeManage Your DataData - FAQ and Errors & Resolutions

 

Explore Categories

 

 PDF

Data – FAQ and Errors & Resolutions

This topic contains Error Codes, Error Messages, and frequently asked questions related to Data in TallyPrime.

Data Security – FAQ

You can restrict users from accessing Back Dated vouchers.

Days allowed for Back Dated vouchers – By default this field is set to 0. Enter the required number of days. Alteration or Insertion of back dated vouchers can be done within the number of days mentioned from the Date of Last Entry of vouchers

Cut-off date for Back Dated vouchers – You can specify the required date. TallyPrime does not allow you to record a transaction prior to the date mentioned. This can be used in addition to Days Allowed for Back Dated vouchers. This input will be useful in situations where you have completed the audit and do not require any changes in the data.

Case 1: When the Cut-off date is set to 0 (zero).
Scenario: ABC company Ltd: The last date of transaction is 30 Apr 2021. The user should not alter or pass the transaction from 1 Apr 2021-14 Apr 2021. Users should only pass the transaction on 15 Apr 2021 and onward. 

Note: Currently TallyPrime will not consider last date of transaction. Hence TallyPrime will allow you to alter or pass the transaction backward by 15 days from the last date of the transaction starting from 29 Apr 2021, so from 29 Apr 2021-15 Apr 2021.

Configure the following settings to restrict users’ access to Back Dated vouchers.

  1. Days allowed for Back Dated vouchers to 15.

Cut-off date for Back Dated vouchers to 0 (zero).
Click here for more detailed instructions on how to restrict access to Back Dated vouchers.

Note: With every change in the date of the last entry, the voucher restriction changes as well.

Case 2: When the Cut-off date is set to any date.
Scenario: ABC company Ltd: The last date of transaction is 30 Apr 2021. The user should not alter or pass the transaction from 1 Apr 2021- 14 Apr 2021. User should only pass the transaction from 20 Apr 2021 onward.

Configure the following settings to restrict users’ access to Back Dated vouchers.

  1. Days allowed for Back Dated vouchers to 15.
  2. Cut-off date for Back Dated vouchers to 20 Apr 2021.
    Click here for more detailed instructions on how to restrict access to Back Dated vouchers.
Note: As of the last day of the transaction, if the cut-off date happens to fall before the days allowed for back dated vouchers, TallyPrime will restrict access to the voucher whichever date is earlier. For example, the last date of the transaction is 30 Apr 2021. The days allowed for the Back Dated vouchers are 15 days, and the cut-off date is set to 20 Apr 2021. TallyPrime will allow users to alter or pass the transaction starting from 29 Apr to 21 Apr. The user will not be allowed to alter or pass the transaction on 20 Apr 2021 backward until 15 Apr 2021.

Security levels can be configured to allow or disallow access to a feature. Various type of access can be provided to a feature such as full access, create, alter, display, print, and preview.

Click here for detailed instructions on how to restrict user access to any particular items in Security Levels based on your requirement.

To remove TallyVault password specified earlier, open the required company, and enter the Tally Vault password.

  1. Alt+K (Company) > TallyVault.
    Alternatively, Gateway of Tally > Alt+K (Company) > TallyVault.
  2. Enter the details in TallyVault screen of your company.
    1. Specify the Old Password. A pre-filled company name will appear based on the company you selected to remove the TallyVault password for.
    2. Leave the Password field as shown below.
      The TallyVault Password Screen
      You will see a warning message stating that your company's data will no longer be encrypted.
      Warning Message screen when leaving the Password blank, which will remove encryption from Company data.
  3. Press Y to accept the screen. As always, you can press Ctrl+A to save.
    A message will appear informing you that removing your TallyVault password will close all the reports, vouchers, and masters without saving any changes.
    The Information Message screen for removing the TallyVault password will close all reports, vouchers, and masters without saving any changes.
  4. Press Y to accept the screen.
    A message will appear asking to create a copy of your company.
  5. Choose the required option as needed.
    On choosing Yes, TallyPrime will create a new company by assigning a new company number and retaining the existing company name.
    For more information on TallyVault for your company, click here.

Take a backup of your data before changing the Admin username and password.

Click here for the detailed instructions on how to change Admin level username and password.

TallyVault is an enhanced security system to maintain the privacy of the company that you have created in TallyPrime. It uses a non-stored password with an advanced algorithm to validate a new user without prior knowledge of the password. The decrypted form of data is not stored on the system. Hence, the TallyVault password cannot be retrieved, resulting in permanently losing access to your company information.

You can remove the Security Levels provided to users when they are no longer required.

Click here for the detailed instructions on how to remove Security Levels defined for users.

In TallyPrime, the Tally.NET Auditor has the Owner's rights by default. This right allows the Auditor to view all reports. In case the Auditors are different for VAT, Service Tax, TDS, and TCS, then the Client can configure the Tally.NET Auditor with corresponding rights so that only the concerned auditor can view statutory reports.

Click here for the detailed instructions on how to assign Security Levels for Statutory Reports.

As the Tally.NET Authentication was enabled in the Security Levels screen, you were unable to enter the password.
The List of Users for Company in TallyPrime

To disable the option in Security Levels:

  1. Alt+K (Company) > User Roles > Select the required Security Levels.
    Alternatively, Gateway of Tally > Alt+K (Company) > User Roles > Select the required Security Levels.
    The Security Levels screen appears.
    The Security Levels Screen in TallyPrime
  2. Set the option for Use Tally.NET Authentication to No.
    You can now proceed to authorize the user and enter the password as required.

It is necessary to prepare a price list for the required stock item at different price levels before restricting users from altering the stock item rates.

Click here for the detailed instructions on how to create a Price list for stock items. Therefore, when an invoice is recorded, the rate field will be skipped, and the rates from the price list will be used.

Click here for the detailed instructions on how to restrict users from altering stock item rates.

There is no way to break the password if you are accessing the company data with a single user login. However, if you have a multiuser login to access the company data, you can open the company using a user level password and then export all the masters and vouchers to it.

  1. How to do authentication for HTTP request?

Scenario: The company is created with a User ID and a Password. Will TallyPrime authenticate the company login credentials whenever an HTTP request is received?

An HTTP request is a request sent by a computer to servers to obtain information. The server responds with the information it requested. TallyPrime receives HTTP requests from third-party applications to fetch the required information. When a request is received and the company is loaded, TallyPrime will respond to the request by sending the information regardless of whether the company is password protected or not. Hence, there is no authentication required to process HTTP requests.

Scenario: After successfully synchronizing data with the branch office, we noticed that the Balance Sheet was displaying incorrect figures. On reviewing the accounts, we found that the Ledger opening balances and Item opening balances were incorrect. The Ledger opening balance and Item opening balances at HO were replaced with the Ledger and Item opening balances of the branch. Is it possible to restrict this from happening in the future?

Yes, it is possible to restrict the Ledger and Item opening balance at HO from being replaced with the Ledger and Item opening balance of the branch.

This can be done in the Client Rule Creation/Alteration screen by setting:

  1. Overwrite opening balances for ledger to No.
  2. Overwrite opening balances for stock item to No.

You can disable either one of the options or both, based on your requirements.

Click here for detailed instructions about how to disable overwriting of opening balances and more information about Data Synchronization.

Error Codes

Error Messages

This error can be resolved by following the steps below:

  1. Create a Data Backup.
  2. Check file size of Transmgr.900. If the file size is 1 KB, restore the earlier backup, if any.
  3. If the Transmgr.900 file size is large, follow the steps of Repair below:
    1. Take the existing backup of the corrupted data and perform Zero Command Repair.
    2. Check the bad sectors on the Hard Disk as well. Click here to view the procedure.

This error can be resolved by following the steps below:

  1. Create a Data Backup.
  2. Check file size of Manager.900/Linkmgr.900. If the file size is 1 KB, restore the earlier backup, if any.
  3. If the Manager.900/Linkmgr.900 file size is large, follow the steps of Repair below: 
    1. Take the existing backup of the corrupted data and perform Zero Command Repair.
    2. Check the bad sectors on the Hard Disk as well. Click here to view the procedure.

To resolve this error, follow the steps below:

  1. Upgrade to the latest version of TallyPrime.
  2. Backup your existing company data, and Repair.

You will be able to learn how to resolve errors tmessage.tsf, tstate.tsf, and tstate.tsf error code 32 here.

  • Error - tmessage.tsf
    This error appears on the client machine.

  • Error - tstate.tsf
    To resolve this error, follow the steps below:

    1. Ensure that all the files/sub-folders in the data folder have full access permissions enabled for the relevant users.
    2. Provide full access permission to all the users (working on TallyPrime).
    3. Verify the network connectivity.
  • Error - tstate.tsf error code 32
    Cause: This error occurs while splitting company data when third-party software is used for data backup, and the .tsf files are saved by this third-party application for backup.

    Solution: Add the .tsf files to the exclusion list of the data backup software.

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

Cause: This error occurs due to the duplication of masters (ledgers) in your company.

Solution:
Recommended: Upgrade to the latest release of TallyPrime to prevent this error.

Interim Fix

To fix this issue in your current release, you need to Repair your company data. After Repairing the data, the duplicated masters (ledgers) will be removed from your company data.

  1. Take a backup of the company data.
  2. Go to Gateway of Tally > F12 (Configure) > Data Configuration.
  3. Set Load Companies on startup? to No.
    However, if the option Load Companies on startup? was set to Yes by default, then you have to modify the tally.ini file (Tally configuration settings).
    To modify the tally.ini file:

    1. Go to the TallyPrime application folder on your computer.
    2. Open the tally.ini file.
    3. Set Default Companies= No.
    4. Press Ctrl+S to save the settings.
  4. Close TallyPrime.
  5. Use Command Prompt to enter the path where Tally.exe is located, followed by the data path and the ID number in the error message.
    For example, C:\Program Files\TallyPrime\tally.exe data 1284.
    If your data is stored in a different folder or drive (for example, D:\TallyPrime\tally.exe “D:\client data” 1234), enter the relevant path.

    TallyPrime now starts in the Command Prompt.

  6. Press Ctrl+Alt+R to repair the company data.

Cause: This error message appears when splitting data if bill-wise details in a transaction are not saved completely.

Solution: The transaction with incomplete bill-wise details must be re-accepted.

  1. Open the spl file available in the TallyPrime folder and check the bill numbers mentioned.
  2. Go to Gateway of Tally Day Book.
    Alternatively, press Alt+G (Go To) > type or select Day Book.
  3. Select the transactions mentioned in the spl file.
  4. Verify the Bill-wise details in the transaction and re-accept.
  5. Re-start the splitting process.

Cause: The error appears when the default group has been altered in TallyPrime while splitting the company data.

Solution:

  1. Open spl file available in the TallyPrime installation folder.
  2. Search for the error message in the file.
  3. Rectify the errors, as per the instructions.
  4. Proceed with splitting the company data.

Cause: The error occurs when the default journal voucher type is changed while splitting company data. 

Solution: Upgrade to the latest release of TallyPrime.

Post a Comment

Is this information useful?
YesNo
Helpful?