Download Account. Exe Dated 28-07-2010
A latest accfix.exe and Account.exe for solving the problem of duplicate records shown in Increment Register is available below.Download and upgrdate the account database by running accountsfix.exe, replace the accounts exe.
Thursday, July 29, 2010
Wednesday, July 28, 2010
DBAnalyzer Dated 26-07-2010
Download DB Analyzer dated 26-07-2010
Recent additions in DBAnalyzer >> Reports
1. Reports in connection with AML - Reports for SB, MIS, TD, SCS, NSC and KVP deposits/opening and withdrawals/closure transactions are available under 'Income tax report' option.
2. List of Branch offices
3. List of Accounts BO wise
4. Provision to modify agent license expiry date is made available in 'RD Accounts - Agent-wise' option
Recent additions in DBAnalyzer >> Reports
1. Reports in connection with AML - Reports for SB, MIS, TD, SCS, NSC and KVP deposits/opening and withdrawals/closure transactions are available under 'Income tax report' option.
2. List of Branch offices
3. List of Accounts BO wise
4. Provision to modify agent license expiry date is made available in 'RD Accounts - Agent-wise' option
Thursday, July 15, 2010
Wednesday, July 7, 2010
Tuesday, June 8, 2010
Sub Account Day End Problem
Sub Account Day End Problem
1. Please Download this attached file and run with script tool executor ..
2. after this .. pl. execute the query mentioned below in SQL Query Analyzer ...
execute treasury..update_megh66_accountheads_bydate '010610'
Pl. also check ..the option 'Convert Temporary Fields' under tools menu through supervisory login ..
If the missing heads are listed, then make them permanent ...
During the course you may need to perform undo day's work .. perform day end and day begin once again ..
Friday, June 4, 2010
Monday, May 17, 2010
Thursday, May 13, 2010
Sanchay Post S.O to H.O Data Transfer
SO to HO data transfer (regular, without bridge) problems and solutions:------------------------------------------------------------------------
1.How to reset the sequence number to 1 at SO? Use the option ‘DBAnalyzer >> Data Transfer >> SO - HO Data Transfer’ before doing day-end on the day data transfer is to be commenced. Select only the schemes for which data transfer is planned to be commenced. Files with sequence number 1 will be generated during day end for the initialised schemes. This option has to be executed only once at a SO for any scheme. This should not be done if transfer of data from SO to HO has already been performed for this SO through Sanchay Post.
2. How to reset the sequence number to 1 at HO for a SO? Use the option ‘DBAnalyzer >> Data Transfer >> HO - SO Data Transfer’ before doing day end on the day data transfer is to be commenced. Use this option for the SO for which data transfer from HO is planned to be commenced. Files with sequence number 1 will be generated during day end for the initialised SO, if any data is available. This option has to be executed only once for a SO.
3. What are the preparatory steps for commencement of SO to HO data transfer? The following points are to be ensured:a. POCode at HO & SO should be the same. If not, at SO use DBAnalyzer to change code.b. Include HO name in SOs (Using PO Name & Address Form) in a separate row.c. Designate the nodes for ‘Day end’. Files are generated in the node in which day end is performed.d. Check whether the fields ‘Name’ / ‘City’ / ‘Pincode’ are not blank for the schemes in which datatransfer is to be commenced.e. Rectify the discrepancies listed in DBAnalyzer.
4. Files for data transfer are not generated at SO in the designated system and folder and cannot be regenerated. Wait for ‘day-end completed successfully’ message. If this is not done files will not be generated and cannot be regenerated also. File creation for HO is the last task performed during day end and if the day end process is ended abruptly due to user intervention or otherwise, file creation for SO will not happen. If Files are not generated at SO for some schemes then check ‘Initialisation >> PO Name & Address’ form and ensure that the scheme is selected in ‘Set Scheme Computerisation Status’ option.
5. Files generated at SO are without extension and hence cannot be imported at HO HO name and code to be initialized in SO. Include HO name in SOs (Using PO Name & Address Form) in a separate row
6. 'Data does not belong to [soname]’ message displayed while importing data. Select the file again and retry Logout and login to SOSB module and retry Ask SO to re-generate the file & resend. If this problem persists, it could be due to OS mismatch (XP / Vista / Windows 2003). Re-generate file in a different system at SO or import the file in a different system at HO.
7. RD bulk posting data not transferred. RD bulk data gets transferred only if Bulk posting is done before generation of the file (before day-end).
1.How to reset the sequence number to 1 at SO? Use the option ‘DBAnalyzer >> Data Transfer >> SO - HO Data Transfer’ before doing day-end on the day data transfer is to be commenced. Select only the schemes for which data transfer is planned to be commenced. Files with sequence number 1 will be generated during day end for the initialised schemes. This option has to be executed only once at a SO for any scheme. This should not be done if transfer of data from SO to HO has already been performed for this SO through Sanchay Post.
2. How to reset the sequence number to 1 at HO for a SO? Use the option ‘DBAnalyzer >> Data Transfer >> HO - SO Data Transfer’ before doing day end on the day data transfer is to be commenced. Use this option for the SO for which data transfer from HO is planned to be commenced. Files with sequence number 1 will be generated during day end for the initialised SO, if any data is available. This option has to be executed only once for a SO.
3. What are the preparatory steps for commencement of SO to HO data transfer? The following points are to be ensured:a. POCode at HO & SO should be the same. If not, at SO use DBAnalyzer to change code.b. Include HO name in SOs (Using PO Name & Address Form) in a separate row.c. Designate the nodes for ‘Day end’. Files are generated in the node in which day end is performed.d. Check whether the fields ‘Name’ / ‘City’ / ‘Pincode’ are not blank for the schemes in which datatransfer is to be commenced.e. Rectify the discrepancies listed in DBAnalyzer.
4. Files for data transfer are not generated at SO in the designated system and folder and cannot be regenerated. Wait for ‘day-end completed successfully’ message. If this is not done files will not be generated and cannot be regenerated also. File creation for HO is the last task performed during day end and if the day end process is ended abruptly due to user intervention or otherwise, file creation for SO will not happen. If Files are not generated at SO for some schemes then check ‘Initialisation >> PO Name & Address’ form and ensure that the scheme is selected in ‘Set Scheme Computerisation Status’ option.
5. Files generated at SO are without extension and hence cannot be imported at HO HO name and code to be initialized in SO. Include HO name in SOs (Using PO Name & Address Form) in a separate row
6. 'Data does not belong to [soname]’ message displayed while importing data. Select the file again and retry Logout and login to SOSB module and retry Ask SO to re-generate the file & resend. If this problem persists, it could be due to OS mismatch (XP / Vista / Windows 2003). Re-generate file in a different system at SO or import the file in a different system at HO.
7. RD bulk posting data not transferred. RD bulk data gets transferred only if Bulk posting is done before generation of the file (before day-end).
Saturday, May 8, 2010
Wednesday, May 5, 2010
Monday, May 3, 2010
Sub Account Day End Error
1. Please Download this attached file and run with script tool executor ..
2. after this .. pl. execute the query mentioned below in SQL Query Analyzer ...
execute treasury..update_megh66_accountheads_bydate '010510'
Pl. also check .
.the option 'Convert Temporary Fields' under tools menu through supervisory login ..If the missing heads are listed, then make them permanent ...
During the course you may need to perform undo day's work .. perform day end and day begin once again ..
2. after this .. pl. execute the query mentioned below in SQL Query Analyzer ...
execute treasury..update_megh66_accountheads_bydate '010510'
Pl. also check .
.the option 'Convert Temporary Fields' under tools menu through supervisory login ..If the missing heads are listed, then make them permanent ...
During the course you may need to perform undo day's work .. perform day end and day begin once again ..
Thursday, April 22, 2010
Wednesday, April 21, 2010
Thursday, April 15, 2010
FAQ Meghdoot 6.6.1
FAQ Meghdoot 6.6.1
1Point 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\dllnameeg.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.
1Point 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\dllnameeg.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.
Thursday, April 8, 2010
Meghdoot SP1 Solutions
1. If countries, currencies are not coming in Movidesh booking then patch is available in ftp site...
ftp://ftp.ptcinfo.org/Meghdootv6.6/PointOfSale/eurogiroCountryProblem/EuroGiro.zip
ftp://ftp.ptcinfo.org/Meghdootv6.6/PointOfSale/eurogiroCountryProblem/EuroGiro.zip
2. Delete Duplicate Account Head in Subaccounts ( Change into Current Date = ‘yyyy-mm-dd’)Use Subaccounts
EXECUTE [H_DeleteDuplicate] @TransDate = '2010-04-09'
3. For treasury problem :
Run the attached Treasury1.exl file using script tool. ( Download )
After executing the script, run query analyzer and execute the following query
Use Treasury
execute update_megh66_accountheads_bydate 'ddmmyy'
Note: ‘ddmmyy’ stands for the date on which account heads not appeared. ex: if the date is 09/04/2010 then ddmmyy will be 090410
Run the attached Treasury1.exl file using script tool. ( Download )
After executing the script, run query analyzer and execute the following query
Use Treasury
execute update_megh66_accountheads_bydate 'ddmmyy'
Note: ‘ddmmyy’ stands for the date on which account heads not appeared. ex: if the date is 09/04/2010 then ddmmyy will be 090410
4. For Accounts PBS Problem:
1. If u are getting the error while generating PLI file then
Please run the following query using query analyzer on NICPLI database
select * from NICPLI..NICMASTER where pliorrpli ='P'
see the results, If no record is returned , it means that there are no PLI record in ur NICPLI database and thus u are getting the BOF error. So u will have to transfer the pli records from master csv file, which u have downloaded from website, using bridge software and select "Delete old records and insert new records" option button. Then transfer rpli records using "Append records" option button.
Please run the following query using query analyzer on NICPLI database
select * from NICPLI..NICMASTER where pliorrpli ='P'
see the results, If no record is returned , it means that there are no PLI record in ur NICPLI database and thus u are getting the BOF error. So u will have to transfer the pli records from master csv file, which u have downloaded from website, using bridge software and select "Delete old records and insert new records" option button. Then transfer rpli records using "Append records" option button.
2. If u are getting the error while generating RPLI file then
Please run the following querry using query analyzer on NICPLI database
select * from NICPLI..NICMASTER where pliorrpli ='R'
see the results, If no record is returned , it means that there are no RPLI record in ur NICPLI database and thus u are getting the BOF error.
>So u will have to transfer the pli records from master csv file, which u have downloaded from website, using bridge software and select "Delete old records and insert new records" option button. Then transfer rpli records using "Append records" option button."
Please run the following querry using query analyzer on NICPLI database
select * from NICPLI..NICMASTER where pliorrpli ='R'
see the results, If no record is returned , it means that there are no RPLI record in ur NICPLI database and thus u are getting the BOF error.
>So u will have to transfer the pli records from master csv file, which u have downloaded from website, using bridge software and select "Delete old records and insert new records" option button. Then transfer rpli records using "Append records" option button."
Subscribe to:
Posts (Atom)