09 May 2014
06 May 2014
Fixed Fetch - COD Articles in Postman Module after Update 7.9.1
COD Messages Received:
No Articles were found while fetch in Postman Module
Solution Shared by
RABINARAYAN CHOUDHURY Mobile : +91-9778236897
TIKABALI SO-762010
Solution
- Download attached Script from PoTools.
- Execute Once Using MM Script Tools.
- Now you can Fetch the Article in Postman Module.
Download
Top Performers - Change Network
94 Department of Post employees have been identified as the top performers for their outstanding contribution in the Change Network of IT Modernisation Project 2012. Our Change Leaders and Change Agents have gone that extra mile in ensuring their fellow DoP employees are aware of the upcoming solutions and have relayed employee concerns to us. We thank each one of you for taking up your role in the Change Network with such zeal and look forward to your continued efforts in the times ahead.
Click here to get the detailed list of the Top Performers
Tool for Search COD Article in Database
The search option which newly included in postman module is not checking
all the tables. Here is an Tool that will check all details including
despatch module.
Execute on PC having windows authentication
1. Provide Correct Server Name
2. Check on windows authentication
3. Type Exact COD article number then click on find status.
Note : Article Number Should be 13 Digit Only
Download
Download
Nedumkandam 685 553. Mobile: 9497278337
Developed and shared by
Rajesh CR - System Administrator.Nedumkandam 685 553. Mobile: 9497278337
05 May 2014
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.
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
24 April 2014
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: codepage09: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
- Take eMO db backup
- Download the attached exl and run it through script tool
- Finally check the eMO print out
- Still eMO printing issue persists, Please Contact CEPT
Download Delete Duplicate eMO Office Name
Download
Subscribe to:
Posts (Atom)