Wednesday, October 30, 2013

FIXED : POSTMAN 7.8 TAKE LONG TIME FOR DAY END

Postman 7.8 Takes Long Time For Day End Process

Meghdoot Millennium Postman 7.8 delay in Process of day end after successful upgradation.

Issues:

             After  Update MM7.8 while day end Postman Module it takes long time to day end some times it leads from few minutes to few hours. 
.

Solution:

Download Attached (fordayend_process)Exl from PoTools
Execute on server using Script Tool.exe


Mirror 1: Google Drive

Mirror 2: Box

THANKS TO : POTOOLS.BLOGSPOT.COM

SPEEDNET 4.0 UPDATED STATUS NOT UPDATED IN SPEEDNET MIS


SpeedNet 4.0 Updated Status Not Updated In SpeedNet MIS
SpeedNet 4.0 has been updated Client and Server Modules successfully with Database up-gradation. But while check in SpeedNet MIS Site

Under Tools option > SpeedNet Upgradation Status

Office Name shows 
  • Status Not Available
  • Only Client Upgraded
  • Only Communication upgraded. 


Solution

If the databases were upgraded completely and messages were lost due to some reason,

  1. Download VersionMessages_Regeneration_Soln_15102013.exl from PoTools
  2. Run the attached script file using Meghdoot ScriptTool

Note: Take full database backups before execute the above exl.

If above method not working kindly do complete Upgaradation in Client Machine as per pending status in SpeedNet Status

THANKS TO :POTOLLS.BLOGSPOT.COM 
T

Friday, October 18, 2013

ix: SpeedNet Virtual bag Messages Not Received

virtual bag messages are not receiving in speednet. 
Some of the offices virtual scanning not comes for Bag opening and article invoicing due to non availability of Virtual message file from central server (Not transmitted from Despatched office) or not received from central server to destination offices.

Solution:
              The virtual message file available in central server and not received in our office due to the following reason.
trxchx.txt file available in RXD folder 
Delete trxchx.txt folder from RXD:

  1. Exit  Speed Net communication from your Machine.
  2. Go to RXD folder, it exists inside EMS Client Folder / C:\Program Files\EMS Client
  3. Check whether trxchx.txt available in RXD Folder. 
  4. If available delete trxchx.txt from your RXD folder.
THANKS TO : POTOOLS.BLOGSPOT.COM

Saturday, October 19, 2013

Despatch 7.8 Configuration & Solution for Slow process

Fixed Despatch 7.8 Configutaion and Despatch 7.8 Slow Process

Issues:
Despatch 7.8 Functioning slowly while do prepare bag/Bundles, it take 2 to 3 seconds for each article added with bag.
Some time after Update Office master in Despatch 7.8 Supervisor while Remove red entries/ Unwanted bags from bag Master it shows an error message as "  There are articles which are already include in this bag. You can not delete this bag "
Solution:

Both the above issues can be fixed by follow the below steps:
  • Modify the red color entries in Despatch -> Supervisor -> Master -> Due Bag -> Modify.
  • If you want to delete old due bag entries then -
Take counter database backup delete your old data from POS System Administrator login.  (Keep only for past 18 months data in system).
     * If you have not used the concern due bag for the last 18 month you can delete that entries through Despatch Supervisor -> Master ->Due Bag -> Add Tab.
Recommended Despatch.exe: 
 

Despatch 7.8 Latest 

Issues:
After Update 7.8 in Despatch 
  • Speed/EPP and unwanted bags are can not remove from bag type option.
  • we are unable to see include button in bundles option, that is not visible and also we could not re-size include bundles window. kindly make Include button visible in "Include Bundle option", otherwise resize include bundle window. 
Please follow the steps below.
1. Download Despatch.exe v7.8 from PoTools
2. Copy and replace new DESPATCH.exe file in your application folder 
3. Please disable the Speed bag by 
        Despatch > Supervisor > Master Menu > Bag Type > Modify
Issues Fixed:
1. SPEED articles are fetching in the despatch module.
2. Last two characters of article/bundle bar code should be IN for closing bag for foreign register articles letters.
THANKS TO :- POTOOLS.BLOGSPOT.COM
 

Monday, October 14, 2013

MEGHDHOOT 7 UPDATE 8 ERROR & SOLUTION

Meghdhoot Millineum 7 Update 8 has been released on 11/09/2013. After that we have faced many errors and got solution from CEPT, Mysore.here PoTools provides Consolidation of MM7.8 Solution

MM 7.8 Latest Exe Given CEPT, Mysore.

Despatch 7.8 Dated: 19-Sep-2013
R Net Communication v3.0 -PO: 09-Oct-2013
Postman 7.8 dated: 11-oct-2013

Error Description shown in below

Despatch 7.8

                   Major issues in MM 7.8 Official is Despatch module, Problem with opening of Despatch Module i.e it ask every time to update "Kindly Update R Net Hub master through R Net Communication".

Guide was supplied for Receive Hub master by PoTools

After over come this issues by receive Hub master through R Net communication and Update Office master in Despatch Supervisor, we can login Despatch Module as operator.
But, we could not close Parcel Bag due to Circlewise barcode limitation, Scanning Fields not clear automatically during Prepare Bag/Bundle and Insured bag not able to close the direct desgination.

To overcome the above issues Get Latest Despatch.exe supplied by CEPT, Mysore.

R Net Communication 3.0 - PO

       Latest R Net Communication have Some New features added. we can not login as Despatch Operator with out R Net Communication v3.0 - PO. But In windows 7 64-bit operating System and Some other Machine while Running R Net Communication it Shows an Error message as
Microsoft.Jet.OLDB.4.0 provider not registered on the local machine. 

So that we are not able to receive R Net Hub master files from CEPT central Server. 


Postman 7.8 

       Postman 7.8  Problem with BO VPP article Amount comes to Zero after invoicing with correct amount. CEPT Mysore provides Latest Postman 7.8 exe to overcome the above issues.

THANKS TO : POTOOLS.BLOGSPOT.COM

Saturday, October 5, 2013

DBAnalyzer for Sanchay Post
 
 

NOTE: Generation of Consolidated Report is a TIME CONSUMING PROCESS. All offices are advised to generate this report after completing the daily routines like DAY-END process, Database Backup, etc.
 

SPEEDNET 4.0 BNPL CUSTOMER NOT ELIGIBLE TO BOOK


After Upgrading SpeedNet 4.0 while do BNPL Booking it shows error Message asBooking Restricted : Customer Not eligible to Book.
This type of error occurs due to the following reasons:

Customers

  • Agreement Period is expired.
  • Bill pending for Payment.

In SpeedNet 4.0 every BNPL Customer should be prepare and Generate Bill  in speednet module itself.

After Generate Pending bills then Move to Monthly Payment option.

For Pending Bills:
  1. Generate Bill for BNPL Customers.
  2. Make Payment using Monthly Payment option (Operator > BNPL > BNPL Customer >Monthly Payment).
   then Select Customer Name and Bill Month > Fetch  then update Payment for Pending Bills

Agreement Period Expired:
     Customer Agreement Period get expired after completion of Agreement period.
Note: Customer agreement will lapse in case of pending bills more than 2 months old and the customer status will be shown as Discontinued.

In case Agreement Period is lapsed/ Expired. New Agreement has to be made with customer for Continue BNPL Booking using the Following option.

For New agreement under Supervisor > BNPL > Customer Master > Agreement > Add option,
select the customer and complete the data entry.