Non Receipt of Electronic Data of Parcel COD Articles at Delivery Post Office

The non receipt of electronic data of a particular Parcel COD article at a delivery post office is largely either due to operational errors or error in R Net Communication. Precisely there are 06 parameters which need to be checked specifically before arriving at probable reason for non receipt of electronic data of any Parcel COD article at a delivery PO and further diagnosis of the issue. All these 06 parameters along with relevant details are listed below. 

It is requested to check each of these 06 Parameters to ensure that it satisfies the desired status, before raising the issue with the CEPT Support Desk. Do mention the actual status against each of the 06 parameters while raising any issue of non receipt of electronic data with CEPT to enable us to ensure speedy disposal of the case.

Note: After receiving the Request Resend option by the Postman Supervisor, the Central Server may take some time to honor the request depending upon the load on the Central Server and hence please wait for at least 02 Hrs, run the R Net Communication and check. 

Solution Number 01: Office properly upgraded to Meghdoot version 7.9.1 but reflecting as Not Upgraded in Parcel Net MIS  Report  Office Not 

Upgraded to version 7.9.1 

 After upgradation of office, version update files are generated automatically and are communicated to Central Server through R Net Communication which in turn updates the MIS Report. However in the instant cases it seems there might have been some issues in the transmission of version update files to the central server through R Net communication after upgradation of office with update 7.9.1. Therefore in order to re-generate the version update files internally, please run the scripts kept at the location mentioned below using Meghdoot Script Tool after taking backup of counter database. Thereafter run the R Net Communication. After some time please check the MIS Report for confirmation.

https://drive.google.com/folderview?id=0BwFc-gw9rPGoLTlGOFJON0NhZkE&usp=sharing 

 There are 02 Script Files kept at the location mentioned above:

1. Counter23042014.exl: For upgradation of Despatch to 7.9.1 & Point of sale to 7.91. 

2. Postman&Rnetcommunication_versionupdate7.9.1.exl: For upgradation of Postman to 7.9.1 & R Net Communication to 7.9.1 

Download whole Document

View / Download

eMO Issues with Receive / Transmit in Update 7.9.1

After updating of the Meghdoot 7.9.1 we are receiving the eMOS but they are not available for printing. eMOs booked at this office is also not transmitted.

Error log file is as under:

Parameter name: codepage 09:03:30:7.8 - [UnZipping]1 is not a supported code page. Parameter name: codepage
09:13:18:7.8 - [Zipping]1 is not a supported code page.
Parameter name: codepage
09:13:30:7.8 - [UnZipping]1 is not a supported code page.
Parameter name: codepage

Note : It may be Problem with Zip/ UnZip Data in eMO Client

Solution

• Go to Control Panel > Regional Settings 
• Click Additional Settings under Format.
• Click on Reset Button to reset the Default values for Regional Settings.

eMO - General Printing Error after Upgrade 7.9.1

Meghdoot 7 Update 9.1 eMO Module Printing error

Issues Listed

After Update MM 7.9.1 ,In Some Offices ,the following eMO problem faced.

For every single eMO print in Operator login -> 2 eMO print out paper is coming (the same eMO no)

For every single eMO reprint in Supervisor login -> 3 eMO print out paper is coming (the same eMO no)

Even change the printer driver, printer (Epson LX300,LX1170,Laser Printner) or given print out from any systems, the same issue exists.

Solution

1. Take eMO db backup
2. Download the attached exl and run it through script tool
3. Finally check the eMO print out
4. Still eMO printing issue persists, Please Contact CEPT

Download Delete Duplicate eMO Office Name

Download

Tips and Tool for Upgrade Status of Meghdoot 7.9.1 in Parcel Net

Upgrade Meghdhoot Parcel Net Update

1. Upgrade Meghdoot Parcel Net Update 7.9.1 Released dated 29.03.2014.
2. Download and execute Postman Issues and Solutions.
3.  Download Revised Postman exe from PoTools.

Tips to Upgrade Status of Parcel Net 7.9.1

• after Upgrade Parcel Net Update 7.9.1 in Post offices all the updated modules should open/execute at once before Run R Net Communication.
• Download Upgrade Status Tool from PoTools to Check the version of Point of sale, Despatch, Postman and R Net communication.

Download (Version Checker)

Download

Note: After Update just Open all Update MM Application at once before Check/Execute R Net Communication.

Version - Message Upgrade Exl for Parcel Net 7.9.1

Download EXL

Download 

Meghdhoot Update 7.9.1 dated 29.03.2014

Parcel Net Update

Postman  Issues and Solution

Postman Solution

Postman  Revised Executable File

Postman Solution

Postman7.9.1 Issues & Solutions

Postman7.9.1 Issues & Solutions

Download

Module	Issue	Solution
Postman	Missent redirected Parcel COD articles are shown in “Articles In Deposit” report	Please execute the script file CODinDeposit.exl
Postman	EVP articles delivered at BO are not coming for BO EVP Verification	Please execute the script file Dly_Select_BOEVPsForVerification.exl

Tool for Mismatch BO Name in Sub Account and Postman 7.9.1

Tool for BO Name Comparison in Sub Account 7.8 and Postman 7.9.1  

Developed by : Ketan Joshi SA, Palanpur HO.

Issues Contact : k9724675876@gmail.com

Download(Tool)

Download

Parcel Net Update MM 7.0 Update 9.1 Revised Dated 07.04.2014

Meghdoot 7 Update 9.1 Revised dated 07.04.2014

Meghdoot 7 Update 9.1 Revised version is uploaded in FTP on 07.04.2014. Major Modification between MM7 Update 9.1 dated 29.03.2014 and dated 07.04.2014 is only Point of Sale 7.9.1 eBillHOLib.dll 

Download

Only Point of Sale 7.9.1 Revised 07.04.2014

Download

Complete Update of Post Office Release dated 29.03.2014 and Revised dated 07.04.2014 

Download

Major Bugs : Fixed Released dated 29.03.2014

BNPL Parcel

1. Viewing the Bill of previous months

Despatch :

1. Invalid use of null while bag despatching .
2. After saving the articles in bag, articles are appearing in the pending articles report.
3. Articles fetched from postman are not included in bag.
4. String or binary data would be truncated while fetch articles from postman.

Postman:

1. In Reports->COD->To BOs,”All BOs” Option is not working –Now it works
2. While invoicing the registered articles for bulk customers in Postman Module By clicking counter Radio Button ,error: Run Time Error 5 -solved
3. While invoicing the registered articles for bulk customers in Postman Module fetched  By clicking Virtual Radio Button, error: Run Time Error 5-solved
4. While invoicing the registered articles for bulk customers in Postman Module fetched  By clicking Receipt Radio Button, error: Run Time Error 5 –solved 
5. Type Mis Match Error while Register bag Opening -Solved
6. Type Mis Match Error while Register Bundle Opening-Solved
7. Latest Rnet communication v7.9.1 will solve Duplicate COD article coming for Invoicing
8. Divert To Beat COD articles are Not coming for BO COD Verification In postman Supervisor-now Divert to beat will come for BO COD verification
9. Return To Sender COD articles are Not coming for BO COD Verification In postman Supervisor- now RTS COD article will come for BO COD verification
10. Automation error while invoicing COD article under post sorting
11. Can not convert Varchar to uniqueidentifier while dayend
12. RB is not available for opening even though it is received in a bag
13. “EMO Paid Report” showing same EMO numbers more than one.
14. BO Parcel cod are coming under BO evp verification has been solved
15. COD Window Undelivered messages are not generating –Now it will generate
16. Now Counter Articles while Invoicing to beat , barcode scanner can be used to scan the article without searching from bunch of article number in dropdown list.