FAQs - Meghdoot 6.6 SP1

FAQs - Meghdoot 6.6 SP1

Point of Sale1. Problem: RPLI transactions cannot be booked.Solution: Do not enter Date of Acceptance and Agent Code while doing RPLI transactions.
2. Problem: ‘Stored procedure missing’ error or ‘too many arguments specified’ error while doing Submit Account.
Solution: Ecounter, EMO and counter database upgradation has to be done in a sequence. If the sequence is not followed, this error will appear. Upgrade Ecounter, then EMO and then do counter upgradation. .
3. Error after counter database upgradation; a typical error log: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 (replace ‘myserver’ with your server name):
exec sp_serveroption @server='myserver', @optname='rpc', @optvalue='true'
go
exec sp_serveroption @server='myserver', @optname='rpc out', @optvalue='true'
go
Note: The above error is related to SQL Server configuration settings and not related to the application. (RPC is Remote Procedure Call).

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 : Patch is available in ftp site...
ftp://ftp.ptcinfo.org/Meghdootv6.6/PointOfSale/eurogiroCountryProblem/

8. While performing Day End the following error is encountered:
‘Multiple step operation generated errors. Check each status value’Solution: 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
10. 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 (replace ‘myserver’ with your server name):
exec sp_serveroption @server='myserver', @optname='rpc', @optvalue='true'
go
exec sp_serveroption @server='myserver', @optname='rpc out', @optvalue='true'
go
Note: The above error is related to SQL Server configuration settings and not related to the application.

11. Accounts Heads not coming
Solution: Please run treasury130410.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. eg: if the date is 06/04/2010 then ddmmyy will be 060410

After that prepare the HO summary afresh

DESPATCH12. While performing Day End the following error is encountered:
‘Multiple step operation generated errors. Check each status value’Solution: Download the zip file from http://www.sendspace.com/file/r7xz78. Unzip it and follow the instruction given in readme.
13. Station articles are not fetching in DespatchSolution: Local delivery / Station articles will not be fetched for despatch in the Despatch module. Fetch local articles for delivery through Postman module. The data will be correctly reflected in DET.
POSTMAN14. Local articles are showing not sent out for delivery in DETSolution: 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 day only.
In such a situation, even if you don’t fetch today, all these local articles will be treated as "Despatched" in DET. Hence please use the Fetch from Counter option on the date of invoicing the articles to postman.
SUB ACCOUNTS
15. For any type of error not covered in the above paras please 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 CEPT.
eMO
16. 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.

17. All EDSOs are downgraded to BOs; How eMOs for these offices will be handled .
Concerned divisions are expected to give the new PIN Code info in respect of these offices, so that the PIN Code database is updated. Presently we are getting many faxes asking us to change the pincode of payee/remitter (wrong pincode). In order to tide over this problem, two options are provided to Divisional administrators 'Change the Payee Pincode' and 'Change Remitter Pincode' under Tools Menu.