FAQ Meghdoot 6.6.1

Point of Sale

1.      RPLI transactions cannot be booked.

Solution: Do not enter Date Of Acceptance and Agent Code while doing RPLI transactions till a new service pack is supplied.

2.      Stored procedure missing error while doing submit account.

Solution: EMO database upgradation should be done before Counter upgradation. You should do emo database upgradation and then do the counter database upgradation.

3.      The following error log after counter database upgradation.

1. COUNTER

22:36:28:============================================

22:36:28:         SCRIPT EXECUTION DETAILS (counter)

22:36:28:============================================

22:36:29:[Column names in each table must be unique. Column name 'AgentCode' in table 'PostalLifeInsurance' is specified more than once.] : Script Execution Error : While executing statement ALTER TABLE PostalLifeInsurance ADD AgentCode nvarchar(15) NULL

22:36:29:[Column names in each table must be unique. Column name 'FirstYearPremium' in table 'PostalLifeInsurance' is specified more than once.] : Script Execution Error : While executing statement ALTER TABLE PostalLifeInsurance ADD FirstYearPremium money NULL

22:36:29:[Column names in each table must be unique. Column name 'DateOfAcceptance' in table 'PostalLifeInsurance' is specified more than once.] : Script Execution Error : While executing statement ALTER TABLE PostalLifeInsurance ADD DateOfAcceptance datetime

Solution: These error messages will come if counter database is upgraded twice. These error messages  can be ignored.

4.      Active X component cannot create object.

Solution: Reinstall the application after deleting the old installation cab files. If you are getting any error while registering the dlls then do the following

Register the dll by entering the following in the Run dialog box window.(Start - Run)

Regsvr32 ApplicationPath\dllname

eg.Regsvr32 H:\POS\cash.dll

5.      While doing submit accounts ‘Server not configured for RPC’

Solution: Run the following query using query analyzer

exec sp_serveroption @server='myserver', @optname='rpc', @optvalue='true'

go

exec sp_serveroption @server='myserver', @optname='rpc out', @optvalue='true'

go

in the myserver replace the myserver with your servername.. It will solve the RPC problem

6.      While doing submit accounts error ‘Operation is not allowed when the object is closed’

Solution : Run Counter13042010.exl using script tool.

7.      While booking MO Videsh, Countries and currencies are not coming

Solution :  If countries, currencies are not coming in Movidesh booking then patch is available in ftp site...

ftp://ftp.ptcinfo.org/ForSKRegionAndCoimbatoreRegionProjectArrowTesting/MOVidesh/EuroGiroTest.rar

8.      While performing Day End, Multiple step operation generated errors. Check each status value

Solution: Please download the zip file from http://www.sendspace.com/file/r7xz78. Unzip it and follow the instruction given in readme.

9.      Invalid object name 'ECounter..ENVIRONMENT'.

Solution : Upgrade eCounter database

TREASURY

1.      In treasury module while entry in postman returns error shown ‘POSTMAN DATA BASE IS NOT AVAILBLE QUITTING’

Solution:  Run the following query using query analyzer

exec sp_serveroption @server='myserver', @optname='rpc', @optvalue='true'

go

exec sp_serveroption @server='myserver', @optname='rpc out', @optvalue='true'

go

in the myserver replace the myserver with your servername.. It will solve the RPC problem

2.      Accounts Heads not coming

Solution: Please run treasury1.exl using script tool.

After executing the script, run query analyzer and execute the following query selecting treasury database.

update_megh66_accountheads_bydate 'ddmmyy'

ddmmyy stands for the date on which account heads not appeared. ex: if the date is 06/04/2010 then ddmmyy will be 060410

DESPATCH

1.      While performing Day End, Multiple step operation generated errors. Check each status value

Solution: Please download the zip file from http://www.sendspace.com/file/r7xz78. Unzip it and follow the instruction given in readme.

2.      Station articles are not fetching in Despatch

Solution:  Local delivery / Station articles will not be fetched for despatch in the Despatch module.You can fetch local article for delivery through postman module. The data will be correctly fetched in DET.

POSTMAN

1.      Local articles are showing not sent out for delivery in DET

Solution:  The option "Fetch from Counter" should be used on the day of invoicing these articles to Postman beats.  For ex: If you have booked local articles today and you want them to be sent to beats on tomorrow, you should not use the Fetch from Counter option today.  This option to be exercised on the next dayonly.

In such a situation, even if you don’t fetch today, all these local articles will be treated as "Despatched" in DET.  Hence Pls use the Fetch from Counter option on the date of invoicing the articles to postman.

SUB ACCOUNTS

For any type of error coming after upgradation pl.do the following.

Restore the backup of Sub accounts, Sub Treasury, BO Sub accounts taken before upgradation....and continue your work till solution is provided by PTC.

eMO

1.      Object reference not set error while doing paid verification

Solution: Please ensure that eMO Account heads are created properly. SubAccount and SupplySubaccount databases are running and correct treasury server name is given while configuration. Ensure that Socodemapping is done correctly. Ensure that HOAccount date and SOaccount dates are entered correctly both in eMO operator and subaccount modules.