I have downloaded the latest version of FVU 2.128 from TIN NSDL site.
After preparing TDS Return using e-TDS RPU Version 1.7 when I validate the .txt file and .csi file in the latest version (2.128) there is an error message displayed "T-FV-1000 Invalid File Header Record Length"
Kindly suggest how to rectify this error. Kindly provide the solution at the earliest.
I was using previously downloaded RPU for preparing e-tds return and validating the files generated through this RPU in the latest FVU version 2.128 and i was receiving error message "T-FV-1000 Invalid File Header Record Length".
Is there any change in RPU version 1.7 please inform should I download the RPU version 1.7 again and then try validating through FVU 2.128 to rectify this error?
The error **"T-FV-1000 Invalid File Header Record Length"** usually happens because the version of the Return Preparation Utility (RPU) used to generate the return file is **not compatible** with the latest version of the File Validation Utility (FVU).
### What to do:
1. **Use Compatible Versions:**
* When using FVU version 2.128, you need to ensure that your RPU is also the latest version compatible with that FVU. * RPU version 1.7 is likely outdated for FVU 2.128.
2. **Download Latest RPU:**
* Visit the official NSDL TIN website: [https://www.tin-nsdl.com](https://www.tin-nsdl.com) * Go to the TDS -> Downloads section. * Download the latest version of the RPU that matches FVU 2.128. * Prepare your TDS return file using this latest RPU version.
3. **Re-generate the Return File:**
* Using the updated RPU, prepare the .txt and .csi files afresh. * Validate these files again using FVU 2.128. * This should remove the "Invalid File Header Record Length" error.
---
### Why this happens:
* File header structure or length definitions sometimes get updated in the latest FVU. * Older RPU versions generate files with old header structures that newer FVU versions reject.
---
If you want, I can help you find the correct download links or guide you step-by-step to update the RPU and fix this error. Just let me know!