Incorrect no. of pli/rpli transaction
Problem related to inclusion of incorrect no. of pli/rpli transaction in the csv file is rectified.
Download Here
Fetching PLI/RPLI data from counter & Treasury
Problem related to fetching PLI/RPLI data from counter is rectified.
Download Here
Monday, May 24, 2010
Friday, May 21, 2010
Thursday, May 20, 2010
Sanchaya Post Day Begin Query
use post
delete from dcl.daybegin
delete from dcl.last_working_day
delete from dcl.si_exec_update
delete from dcl.daybegin
delete from dcl.last_working_day
delete from dcl.si_exec_update
Sanchaya Post Query for Data Restore
Run Query analyzer, select ‘Master’ database and execute the following command –
>· Select sid from sysxlogins where name = ‘DCL’
>For example: The result of this command may be as follows:
>0x603B633FF489D411AD9A000021DD037E
>2. Execute these commands one by one
>Ø sp_configure ‘allow updates’,1 Press Ctrl E
>Ø reconfigure with override Press Ctrl E.
>3. Select ‘post’ database and execute the following statements:
>Ø Update sysusers set sid = 0x603B633FF489D411AD9A000021DD037E
> where name = ‘DCL’
>
>Note: Value of sid obtained by step 1 has to be used in the above update statement.
>Repeat step 3 after selecting the other four (BPRO, BPLOG, SOSB, SIGN and SO’s if necessary) databases one by one and executing the same query. After all the databases have be modified with the SID, go to the next step.
>
>4. Execute these commands one by one
>Ø sp_configure ‘allow updates’,0 Press Ctrl E
>Ø reconfigure with override Press Ctrl E.
>
>5. You can now run the data entry / online transactions as usual.
>· Select sid from sysxlogins where name = ‘DCL’
>For example: The result of this command may be as follows:
>0x603B633FF489D411AD9A000021DD037E
>2. Execute these commands one by one
>Ø sp_configure ‘allow updates’,1 Press Ctrl E
>Ø reconfigure with override Press Ctrl E.
>3. Select ‘post’ database and execute the following statements:
>Ø Update sysusers set sid = 0x603B633FF489D411AD9A000021DD037E
> where name = ‘DCL’
>
>Note: Value of sid obtained by step 1 has to be used in the above update statement.
>Repeat step 3 after selecting the other four (BPRO, BPLOG, SOSB, SIGN and SO’s if necessary) databases one by one and executing the same query. After all the databases have be modified with the SID, go to the next step.
>
>4. Execute these commands one by one
>Ø sp_configure ‘allow updates’,0 Press Ctrl E
>Ø reconfigure with override Press Ctrl E.
>
>5. You can now run the data entry / online transactions as usual.
Wednesday, May 19, 2010
-------------------- DOWNLOADS HERE -----------------------
SPEEDNET 3.1.1 CLIENT SETUP : Downloads dtd 17/07/2009
SPEEDNET README 3.1.1 : Downloads dtd 17/07/2009
SPEEDNET URL : Download
SPEEDNET 3.1 SERVER SETUP : Download
SPEEDNET 3.1 CLIENT SETUP : Download
COMMUNICATION 3.1 SETUP : Download
RD CUSTOMERPACK SETUP : Download
RD CUSTOMERPACK UPDATE : Download
SANCHAYPOST 6.5 ALL PATCH : Download
SANCHAYPOST - DB CREATION PATCH : Download ( FOR SANCHAY POST 6.5)
SANCHAYPOST - BPRO UPDATES : Download
SANCHAYPOST - NEGATIVE LIST : PATCH : Download
CCBRIDGE 3.5 SETUP: Download
eMO Pay inSlip - New : Download
Computer History Sheet : Download
SPEEDNET README 3.1.1 : Downloads dtd 17/07/2009
SPEEDNET URL : Download
SPEEDNET 3.1 SERVER SETUP : Download
SPEEDNET 3.1 CLIENT SETUP : Download
COMMUNICATION 3.1 SETUP : Download
RD CUSTOMERPACK SETUP : Download
RD CUSTOMERPACK UPDATE : Download
SANCHAYPOST 6.5 ALL PATCH : Download
SANCHAYPOST - DB CREATION PATCH : Download ( FOR SANCHAY POST 6.5)
SANCHAYPOST - BPRO UPDATES : Download
SANCHAYPOST - NEGATIVE LIST : PATCH : Download
CCBRIDGE 3.5 SETUP: Download
eMO Pay inSlip - New : Download
Computer History Sheet : Download
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 .. Temporary Solution- Click Here
Tuesday, May 18, 2010
Hirens Boot CD 10.4
Dear friends,
Hirens Boot CD 10.4 is a very useful bootable CD, with many features. Hope this CD will help all our SA's in their day to day office work & other staff for their home use.It contains all most every thing we want in a single CD, including Antivirus, password recovery, disk partioning etc--Download this CD from any of the following links:
Download Link 1 or Download Link 2
after downloading extract the zip file, you will find an ISO image, burn the image using the Burncdcc.exe located below.
Miscellaneous Softwares
V2Conversion 3.0 dtd 05/04/2010
SB Plugin & V2Conversion Updates dtd 31/03/2010SanchayPost DB Creation :
RMS : CRC Setup
Inspector Software Setup : Download
Inspector Software 2.1 Updates : Download
Inspector Software 2.2 Updates : Download
Monday, May 17, 2010
Treasury-Account-Head-Problem
Download and run attached exl. ( Download )execute the attached script using script tool.if the accountheads are required for the current date execute the following:use treasurygoupdate_megh66_accountheadsif the accountheads are required for a particular date:use treasurygoupdate_megh66_accountheads_bydate 'ddmmyy'in this ddmmyy explanation is as follows:if the date is 07/05/2010 then it will be equal dd/mm/yyyy so the ddmmyy will be 070510. This can be applied to any date on the same analogy.
SQL TOOL
1) Hi guys, Im posting a new SQL tool which I found interesting(free ware for 30 days). Use it on your own risk as Im not responsible for any negetive aspects, If possible run it on a dummy server. Hope this tool will help us in understanding various aspects of SQL, understanding design,logins,scripting etc---here to Download
2)I found this tutorial very useful in our daily life, I've uploaded it.Download Here
Meghdoot 6.6.1 Problems & Solutions
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.
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.
Subscribe to:
Posts (Atom)