Solutions to the problems reported after release of Update-8 to Meghdoot7.0.

CLICK HERE TO DOWN LOAD THE SOLUTIONS AND PATCHES TO UPDATE 8

Solution to the Common Errors in Accounts PBS Module

Name of exe file: Schedule7.8.exe

The above mentioned exe file shall resolve following errors / issues in Accounts PBS Module:

1. Pensioner DA Arrear generation.
2. Deletion of PLI / RPLI unwanted Policies.
The steps to be followed for using the above mentioned exe are as follows:
i. Please download the above mentioned ‘Schedule7.8.exe’ from the Solution Folder
on ftp site. Then rename it as ‘Schedule.exe’.
ii. Now replace the old exe with this latest exe (Schedule.exe) into the specified
folder.
Note 1: Procedure to be followed for Pensioner DA Arrear generation:
1. Pension with 80% DA should be drawn for the months required i.e. July 2013 to Sep
2013.
2. Modify (NOT NEW DA ) the DA under Allowances --> Modify --> Select Correct DA
already configured i.e. 80% in this case --> Edit --> Select 80% config --> Enter from
month 07/2013 and rate as 90%.
3. Generate Arrear Vouchers --> Select that particular DA which was configured as
90%...because many offices are having many DA in different names.
4. Reports --> Arrears; the Arrear Vouchers shall be displayed.
Note 2: Deletion of PLI / RPLI Unwanted Policies:




1. After running the said exe a new submenu will appear under the “Tools” menu
named as “Delete PLI RPLI unused data from PLI Master”.
2. This option will delete only those PLI / RPLI Policy Numbers from PLI Master Table
for which no transaction of any type has since been done in the office.
3. In order to delete the PLI / RPLI Policies for which any transaction has take place in
the office at first those particular transactions should be get deleted first, then this
option to be used for deletion of those wrong policies, then enter correct policy
details and then re-enter those transactions which were deleted.
= = = / = = =


Solution for Common Errors in Despatch Module

 Modifications done after update 8.

1. General Information.
 In order to resolve some common technical issues arose in the Despatch Module after
upgradation of office with latest update 8 of Meghdoot 7.0; a revised ‘DESPATCH.exe’ is
kept along with this document.
 In order to resolve some other common errors 02 exl files are also kept along with this
document.
 The errors / issues resolved through the exe / exl file are detailed below.
2. Pre-requisite.
 Ensure that Up-gradation is carried out after Day End in all modules.
 Ensure that the office is upgraded with latest Update-7.3 to Meghdoot Version 7.8.
 Ensure that backups of all databases and mdb files are taken and securely preserved.
 Ensure 100% successful running of the database up-gradation. If any error occurs while
executing any exl file, please send the log file to CEPT Help Desk
(Support@ceptmysore.net).
3. Detailed Up-gradation Procedure
 In case of exe file:
o Download the Revised “DESPATCH.exe” file from the Solution folder in ftp.
o Rename existing DESPATCH.exe file in Point of Sale Application folder.
o Copy the revised “DESPATCH.exe” file to Point of Sale Application folder.
o Disable the Speed Bag Despatch -> Supervisor -> Master Menu -> Bag Type -
> Modify.
 In case of exl file:
o Download the concerned exl file from the Solution folder in ftp.
o Please take backup of Counter Database.
o Please run the script using Meghdoot Script Tool.
Solution for Common Errors in Despatch Module
3. Technical Issues / Bugs / Errors Fixed through the revised exe & exl files.
Name of exe file: DESPATCH.exe
The above mentioned exe file shall resolve following errors / issues:
1. Non-feeding of mobile number does not allow for completion of transaction.
2. Speed Articles are getting fetched in the Despatch Application.
3. Even after deleting EPP / SPEED bags by Supervisor, on reopening of Despatch
Application, deleted bags are recreated automatically.
4. While closing Foreign Registered Articles it prompts a message that “Last two
characters of Article bar code should be IN” and does not allows electronic
dispatch of foreign registered articles.
5. While scanning the articles at the time of closing bags, the Article Number area
does not gets cleared automatically after scanning of a particular article thereby
causing difficulty / delay in scanning.
6. Error Message: “For your Circle ……….. first character of Parcel Article Barcode
should be C”.
7. The last two characters of the Article Barcode should IN - for parcel and Express
parcel articles only.
8. Error Message: “For your ……….. circle bag barcode should be in between ………
and ………… but we have received bag barcode number ………. and ……… for closing
the parcel bags.
9. While closing Speed bag in Despatch Module, errror message that articles should
be start with R, but for Speed Articles will start with E(Ex:EN545369491IN).
10. Error message: “Implicit conversion of varchar value to varchar cannot be
performed because the collation of … collation while opening the Unregistered
Letter Bag”.
Name of exl file: ModifyBagNameSize60.exl
The above mentioned exl file shall resolve following errors / issues:
1. Error Message: String or binary data would be truncated while configuring due
bags.
Issue: While invoicing larger number of article in a bag for dispatching the process is getting very
slow.
Solution: Please take counter database backup and delete your old data. (Keep only for past 18
months data in system). The old data may be causing slowness.

Name of exl file: Counter21102013.exl
The above mentioned exl file shall resolve following errors / issues:
1. [Microsoft][ODBC SQL Server Driver] [SQL Server] Could not find stored procedure
a. P_GetBagsDespatched
b. VersionUpdate
c. Check_VersionNo
d. P_GetBORegArticlesForTransmission
e. P_GetBOParcelArticlesForTransmission
f. P_DBDespatchVesrion
g. G_GetRegArticlesForTransmission
h. G_GetParcelArticlesForTransmission
i. G_GetBookedArticlesForTransmission
j. DuplicateBarcodeForSPLRDArticles
k. P_DueBagClosed
l. Bag_Details
Name of exl file: P_DueBagsDetails.exl
The above mentioned exl file shall resolve following message:
1. Message while configuring Parcel Due bags in Supervisor Despatch: Parcel due
bags are not available in the list view of the due bag configuration for dispatch
supervisor.
Name of exl file: P_GetBagsDespatched.exl
The above mentioned exl file shall resolve following message:
1. Error Message while dispatching: Implicit conversion of varchar value to varchar
cannot be performed because the collation of the ..collation conflict.
Name of exl file: DuplicateBarcodeForSPLRDArticles.exl
The above mentioned exl file shall resolve following message:
1. Duplicacy of articles while closing the bag.
= = = / = = =



Solution to the Common Errors in Postman Module

Name of exe file: POSTMAN.exe
The above mentioned exe file shall resolve following errors / issues in the Postman Module:
1. VPP amount becomes 0(zero) for BO Invoiced VP Parcel Article.
2. “Parcel in Deposit” Sub Menu under the Reports Menu is not available.
3. Fetch from Counter for Parcel Article in supervisor is not coming in Receipt Side of
Parcel Abstract.
The steps to be followed for using the above mentioned exe are as follows:
i. Please download the above mentioned ‘POSTMAN.exe’ from the Solution Folder on
ftp site.
ii. Rename the exe which is inside the Postman folder.
iii. Now paste this latest exe (POSTMAN.exe) downloaded from ftp site into the said
Postman folder.
Name of the exl file: BOTRANSACTION_DATE.exl
The above mentioned exl file shall resolve following errors / issues in the Postman Module:
1. [Microsoft][ODBC SQL Server Driver] [ SQL Server] Could not find stored procedure
a. MO_Insert_WithBORemarks,
b. MO_Select_EnquiryFromBOArticlesTable,
c. MO_Update_WithBORemarks,
d. Par_Insert_BOArticles,
e. Par_Insert_WithBORemarks,
f. Par_Select_EnquiryFromBOArticlesTable,
g. Par_Update_WithBORemarks,
h. Reg_Insert_BOArticles,
i. Reg_Insert_WithBORemarks,
j. Reg_Select_EnquiryFromBOArticlesTable,
k. Reg_Update_WithBORemarks,
l. RegNet_Msg_BOArticlesDelivered,
m. RegNet_Msg_BOArticlesUnDelivered,
n. RegNet_Msg_BOParcelsDelivered,
o. RegNet_Msg_BOParcelsUnDelivered


The steps to be followed for using the above mentioned exe are as follows:
i. Please download the above mentioned ‘BOTRANSACTION_DATE.exl’ from the
Solution Folder on ftp site.
ii. Take postman database backup.
iii. Please first run the ’BOTransaction_Date.exl’ using Script Tool and
iv. Then run the “postman_2.exl” (which is one of the two exls of the update 8) using
script tool.
Name of the exl file: BagType.exl
The above mentioned exl file shall resolve following errors / issues in the Postman Module:
1. [Microsoft][ODBC SQL Server Driver] [ SQL Server] Could not find stored procedure
a. Reg_Rep_BagReceipt
b. RegNet_Msg_BagsReceived
c. Invalid Column Name ‘Bag_Type ‘
The steps to be followed for using the above mentioned exe are as follows:
i. Please download the above mentioned ‘BagType.exl’ from the Solution Folder on
ftp site.
ii. Take postman database backup.
iii. Please first run the ‘BagType.exl’ using Script Tool and
iv. Then run the “postman_2.exl” (which is one of the two exls of the update 8) using
script tool.
= = = / = = =




Solution to the Common Errors in R Net Communication Module

Error Message: Error Converting Data Type Varchar to Int
Solution:
In update 8 of Meghdoot 7.0 we have released R Net Communication 3.0, please use this.
This will solve your problem.
Name of the exl file: BOOfficeId_missing_RedirectedArticles_table.exl
The above mentioned exl file shall resolve following errors / issues in the Postman Module:
1. [Microsoft][ODBC SQL Server Driver] [ SQL Server] Could not find stored procedure
P_GetBORegartilceforTransmission.
The steps to be followed for using the above mentioned exe are as follows:
i. Please download the above mentioned
‘BOOfficeID_missing_RedirectedArticles_table.exl’ from the Solution Folder on ftp
site.
ii. Take counter database backup.
iii. Please first run the ‘BOOfficeID_missing_RedirectedArticles_table.exl’ using Script
Tool and
iv. Then please run the “Counter11092013.exl” once again which is released as part of
update 8.
= = = / = = =


Solution to the Common Errors in Extraction of Speed Post related values in the Project Arrow
DET Reports

Name of exl file: DET_25062013.exl
The above mentioned exl file shall resolve following errors / issues:
1. Issues related to difference in Local Speed Net Deposit / Receipt / Missent / RTS
figures and Project Arrow DET Deposit / Receipt / Missent / RTS figures.
The steps to be followed for using the above mentioned exe are as follows:
i. Please download the above mentioned ‘DET_25062013.exl’ from the Solution
Folder on ftp site.
ii. Take full database backup.
iii. Run the said DET_25062013.exl using Meghdoot Script Tool.
Important Note: Execution of DET_25062013.exl file will affect the DET figures for future dates
only.
= = = /= = =