SanchayPost Frequently Asked Questions

FAQ on Version 6.5

Upgradation (1) 1. While running DBAnalyzer >> Check Databases >> Version 6.5, the message "Upgradation to version 6.5 is not successful. Error Code1 : Z" is displayed. a) Run upgradation once again using Start Menu -    "Sanchay Post >> Upgrade DB >> Patch for SQL 70/ Patch for SQL 2000 & 2005 (Version 6.0 to 6.5)" b) Use DB Analyzer >> Check Databases >> Version 6.5 again, to check if the upgradation is successful.

Online Transactions (2) 1. In RD Bulk Acceptance, the error message "Not a valid agent, exiting application" is displayed. a) Copy the patches for Version 6.5 to the respective folders b) Use 'DBAnalyzer >> Database Discrepancies >> RD >> Agent Updation' option. c) Also, check the expiry date of the Agent's authority in Sanchay Post Form no. 0403   2. No. of accounts scanned not correctly displayed in ‘Signature Scanning’ report in DBAnalyzer. Based on the feedback received from various sites, some changes have been made in the ‘Signature scanning report’ available under ‘Reports’ option of DBAnalyzer. Before using Reports option go to ‘Database Discrepancies’ >> ‘Scheme’ (SB, PPF & NSS) >> ‘Account numbers with blank account status’ and rectify the discrepancies using the 'Update' button provided in the screen.

Online Transactions - SCS (4) 1. How to Extend an SCS account? Extension of SCS accounts can be performed in the software only after payment of the partial interest for the last quarter. After payment of the final partial interest, the Supervisor can extend the account (Using form no 1418). 2. While closing SCS accounts on date of maturity, in the closure screen, partial interest is not displayed. Run DBAnalyzer (exe dated 20/08/2009 or later). Select ‘Database Discrepancies >> SCS >> Updation of maturity date’ and click on ‘Display’ and wait till the message ‘Updation completed’ is displayed. Subsequent to this updation, closure can be done in Sanchay Post Online module.   3. Unable to extend SCS accounts having withdrawal type as ‘Standing Instructions’, since the final partial interest cannot be paid in cash. Run DBAnalyzer (exe dated 20/08/2009 or later). Select ‘Database Discrepancies >> SCS >> Updation of Withdrawal Type for matured accounts’ and click on ‘Display’ and enter the account number for which extension has to be performed and click 'OK'. Then, withdrawal of interest can be done in Sanchay Post Online module and subsequently extension can be performed by the Supervisor. After extension, standing instruction, if requested by the customer for the extended period, is to be added afresh using ‘Common >> SI Entries’ form.   4. Standing Instructions in respect of SCS extended accounts not posted in SB accounts The problem does exist in the software. After day-begin and the execution of SI (on the due date of interest posting for each quarter), the list of SCS accounts for which SI has not be executed can be printed from DBAnalyzer using ‘Database Discrepancies >> SCS >> Account numbers with SI without previous quarter interest withdrawal’. This list can be used for cross-verification. For the present quarter withdraw interest from such SCS accounts individually using the ‘Withdraw Interest’ Form in Online Module and select ‘Transfer to SB Account’ in the payment options and enter the SB account number. To alter the withdrawal type from ‘SI’ to cash use DB Analyzer >> Database Discrepancies >> SCS >> Select ‘updation of withdrawal type for matured accounts’ >> Enter account number and update withdrawal type.

Data Conversion V2SBCO to Sanchay Post (1) 1. After conversion from V2SBCO to Sanchay Post, while checking the "Passbook View", error message "Invalid account number" is displayed. a. Check whether the account number block is available in ‘Initialisation >> Account numbers’ in     supervisory login of Online module of Sanchay Post. b. Check whether any account numbers are displayed in ‘DBAnalyzer >> Database Discrepancies >>     [scheme] >> Index entries with different POCode’. c. Check whether any account numbers are displayed in ‘DBAnalyzer >> Database Discrepancies >>     [scheme] >> Ledger entries without index entries’

SO to HO Data Transfer (7) 1. How to reset the sequence number to 1 at SO? Use the option ‘DBAnalyzer >> Data Transfer >> SO - HO Data Transfer’ before doing day-end on the day data transfer is to be commenced. Select only the schemes for which data transfer is planned to be commenced. Files with sequence number 1 will be generated during day end for the initialised schemes. This option has to be executed only once at a SO for any scheme. This should not be done if transfer of data from SO to HO has already been performed for this SO through Sanchay Post. 2. How to reset the sequence number to 1 at HO for a SO? Use the option ‘DBAnalyzer >> Data Transfer >> HO - SO Data Transfer’ before doing day end on the day data transfer is to be commenced. Use this option for the SO for which data transfer from HO is planned to be commenced. Files with sequence number 1 will be generated during day end for the initialised SO, if any data is available. This option has to be executed only once for a SO. 3. What are the preparatory steps for commencement of SO to HO data transfer? The following points are to be ensured: a. POCode at HO & SO should be the same. If not, at SO use DBAnalyzer to change code. b. Include HO name in SOs (Using PO Name & Address Form) in a separate row. c. Designate the nodes for ‘Day end’. Files are generated in the node in which day end is performed. d. Check whether the fields ‘Name’ / ‘City’ / ‘Pincode’ are not blank for the schemes in which data     transfer is to be commenced. e. Rectify the discrepancies listed in DBAnalyzer.   4. Files for data transfer are not generated at SO in the designated system and folder and cannot be regenerated. Wait for ‘day-end completed successfully’ message. If this is not done files will not be generated and cannot be regenerated also. File creation for HO is the last task performed during day end and if the day end process is ended abruptly due to user intervention or otherwise, file creation for SO will not happen. If Files are not generated at SO for some schemes then check  ‘Initialisation >> PO Name & Address’ form and ensure that  the scheme is selected  in ‘Set Scheme Computerisation Status’ option.   5. Files generated at SO are without extension and hence cannot be imported at HO HO name and code to be initialized in SO. Include HO name in SOs (Using PO Name & Address Form) in a separate row.   6. 'Data does not belong to [soname]’ message displayed while importing data. Select the file again and retry Logout and login to SOSB module and retry Ask SO to re-generate the file & resend. If this problem persists, it could be due to OS mismatch (XP / Vista / Windows 2003). Re-generate file in a different system at SO or import the file in a different system at HO. 7. RD bulk posting data not transferred. RD bulk data gets transferred only if Bulk posting is done before generation of the file (before day-end).

Project Arrow / Meghdoot Accounts MIS (5) 1. While running Accounts MIS client, error message displayed as “Unable to continue due to the following error: There is a problem with SQL server. Login failed for user 'arrow'.”   If Accounts MIS application was being used in Meghdoot Version 6.5 earlier and you have upgraded to Meghdoot Version 6.6, contact PTC Mysore for solution. In offices where ‘Sanchay Post Project Arrow Interface’ was installed from Meghdoot 6.6 CD uninstall the ‘Sanchay Post Project Arrow Interface’ module and also delete ‘Project arrow reports’ shortcut if available in the desktop. If Accounts MIS application is installed afresh and the above mentioned error occurs, following are the possible actions: a) If Sanchay Post Version 6.0 or earlier version is used, upgrade to Version 6.5 immediately. b) If you are already using Sanchay Post Version 6.5, use DBAnalyzer to check whether you have    upgraded to Version 6.5 successfully. While checking, if DBAnalyzer displays error code 1: Z, run    ' ARROW.EXE' to create the Project database & login. c) If you have shifted operations to a new server after upgradation to Sanchay Post Version 6.5,     run 'ARROW.EXE'' to create the Project database & login and then restore the Project database's     backup, if available. Not restoring your backup of Project database or removal of the existing     Project database and recreating it using 'ARROW.EXE' will result in loss of previous transaction data. d) Use patchstatus.exe to ensure that all the patches available are installed in all the systems     running Sanchaypost and especially in the system from which day end is performed. The KPIs are updated during day end process automatically.   2. While running Accounts MIS client, error message displayed as “There is some application error. Either day end has not happened in Sanchaypost or the arrow related information for Sanchaypost is not available. Application cannot continue.”   Use PatchStatus.exe to ensure that all the patches available are installed in all the systems running Sanchaypost and especially in the system from which day-end is performed. Uninstall the ‘Sanchay Post Project Arrow Interface’ module. Delete ‘Project arrow reports’ shortcut if available in the desktop.  To view the KPIs, the option ‘Sanchay Post >> Project Arrow >> Transaction Time Report’ should only be used. The KPIs are updated during day end process automatically.   3. INSTRUCTIONS FOR USING ARROW.EXE 1. Click here to download ARROW.EXE 2. Unzip the downloaded file, copy it to the DBAnalyzer folder and run the exe file. 3. Use latest DBAnalyzer >> 'Check databases' >> Version 6.5 and verify if the message     'Upgraded successfully to Version 6.5' is displayed.   4. Offices having problem in uploading SB KPI's using Account MIS should ensure the following: In offices where ‘Sanchay Post Project Arrow Interface’ was installed from Meghdoot 6.6 CD uninstall the ‘Sanchay Post Project Arrow Interface’ module and also delete ‘Project arrow reports’ shortcut if available in the desktop. This should be done in all the systems in which the interface was installed. Ensure that Sanchay Post Version 6.5 is installed. Use DBAnalyzer to check whether you have upgraded to Version 6.5 successfully. Use patchstatus.exe to ensure that all the patches available are installed in all the systems running Sanchaypost. While performing day end ensure that the message ‘Day end completed successfully’ is received. 5. Offices having difference in the number of signatures scanned shown in SB KPI's and DBAnalyzer. Use DBAnalyzer with latest exe (dated 12/11/2009 or later) Check for patches installed in all clients using 'Patch Status' Go to ‘Database discrepancies’ >> ‘Account numbers with blank account status’ for ‘SB’, ‘NSS’ and ‘PPF’ and update. Go to ‘Reports’ >> ‘Signatures without index entries’ >> and delete the entries after confirming that the account numbers listed are not existing. Go to ‘Reports’ >> 'signature scanning report' and verify. click on the button 'List of accounts - signature not scanned' to obtain account numbers for which Specimen Signature is not scanned. The file generated can be opened and signatures to be scanned for the accounts listed in it.