FAQ's on Revision of Interest Rates and Various Changes in SB rulings (5)

1.	Even after running the ‘MoF_RateChange.exe’ patch, the software shows wrong maturity date for MIS and NSC 5 Year Issue.
	The maturity date shown in the software will continue to show the older maturity period and will not affect any present activity and hence you can ignore the maturity date displayed in the software. As per the SB order No 23/2011 the certificates needs to be stamped and signed by the Postmaster before being given to the customer.
2.	What is the procedure to follow for allotting registration number for the NSC issue after the implementation of the new SB orders?
	For NSC 5 Year issue the previous block of registration number allotted for NSC 6 Year issue should be continued without break.  For the new NSC 10 Year issue, a new block of registration number is to be allotted. At present, NSC 10 Year issue is to be handled manually and is NOT available in the Sanchay Post software.
3.	What is the procedure to follow for return of KVP stock and for issue of duplicate KVP?
	A report is provided in DBAnalyzer (dated 02/12/2011) under Database Discrepancies >> KVP >> KVP Stock to list the KVP unsold stock from the Sanchay Post database. This report can be printed at each office and sent to HO along with the stock. These reports should be consolidated at HO while returning the stock to CSD. A provision to make the stock ‘NIL’ will be provided later.
4.	Should some stock for issue of duplicate KVP be retained at the HO while sending unsold stock to CSD?
	No, all the stock of unsold should be returned to CSD.
5.	Is the new rate of one percent deduction on the rate specified applicable for TD PMC for TD accounts opened before 01/12/2011?
	Yes, the new rate of TD PMC is applicable for all TD accounts opened before or after 01/12/2011, but prematurely closed on or after 01/12/2011.

Patch for Removal of ceiling for maximum balance in SB accounts

Patch for Removal of ceiling for maximum balance in SB accounts

(SB Order No.20/2011) now available. The order comes into effect from 1st October 2011. The downloaded file should be unzipped and executed from the DB Analyzer folder.

Click here to download Patch

 

Meghdoot 7 : Point of Sale Submit Account Error & MSDTC Services Error

Problem:

After installation SQL Express and M.M.7.0 
1. RPC errore while submitting  POS Submit account 
2. Error Message like " MSDTC SERVICES IS NOT RUNNING "


Solution:

1.

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

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

Note:  Replace 'myserver' with your servername in the above query.

2. Go to Services (Control Panel-- Administrative Tools--Services ) and then start the service 'Distributed Transaction Coordinator' (MSDTC) with start up type as 'Automatic' and Log On As 'Network Service' as shown in the attachment.   Then execute the below mentioned Query relating to 'RPC' error to solve the problem.

Screen Shot - Distributed Transaction Coordinator' (MSDTC)

Meghdoot7 Installation Guide

India Post wins Skoch Digital Inclusion Award 2011 for ePost Corporate

India Post’s ePost Corporate service has won Skoch Digital Inclusion Award 2011. The service has been rated amongst the Top-100 ICT Projects in India during 2011 in an accessment across government, corporate, financial and public sector. 

The award was received by Ms Radhika Doraiswamy, Secretary, Department of Posts from Mr. Montek Singh Ahluwalia, Deputy Chairman, Planning Commission in a function held on 1^st September 2011 at New Delhi.

Skoch Digital Inclusion Award 2011 - Citation

Source : http://www.indiapost.gov.in/DI_Awards_2011.html

Error while updating Office master of RNet in SQL 2008

While executing the office master query in Query Analyzer for RNet Office Master updation, the query is completed with the following error:
"Msg 2627, Level 14, State 1, Line 4
Violation of PRIMARY KEY constraint 'PK_Office_Master'. Cannot insert duplicate key in object 'dbo.Office_Master'.The statement has been terminated."

Solution:
Run the attached exl file through scripttool.exe

Download

RNet - 'http is not registered' error

Problem:

While running RNet communciation, the following error mesage
"The channel "http  is not registered with remoting services"."

Solution:

Do the following steps to rectify this problem:

1. Go to the folder C:\windows\System32\drivers\etc ( if you have installed windows on D partition then the path will be like D:\windows\System32\drivers\etc)

2. Open the file “Hosts” file using notepad
3. There will be an entry like the following inside the hosts file
   127.0.0.1 localhost

Add one more entry below.
218.248.43.143 regnnet.ptcmysore.gov.in

Revised instructions for handling BPL accounts

How do we open BPL Accounts in Sanchay Post Version 6.5-R2?

 

Henceforth, BPL accounts should be opened in the ONLINE MODULE only and the account number allotted will be from the regular SB block. While opening BPL acounts, counter officials should enter the following details under the Introducer particulars:

a) Select ‘Others’ in the dropdown option for Scheme.
b) Enter ‘BPL’ in the introducer name, address, city and pincode.

This is mandatory for all BPL accounts, failing which the account cannot be classified as a BPL account. The counter officials should be suitably instructed without fail. The same procedure is to be adopted for opening of BPL accounts in the SOSB Online module.

For BPL accounts already opened in NREGS Data Entry Module:

a. Open Form No. 0459 in Initialisation Group
b. Add a new block
c. Enter the starting number and the last number of the accounts opened as BPL accounts.
c. In the 'Latest Number' field, enter the last BPL account number opened.
d. Click on 'Save'

The corresponding block should be deleted from the initialisation of NREGS Account Number Blocks.
Example: The block allotted for BPL accounts in NREGS is 50001 to 55000 and accounts have been opened upto 50120. Delete the block 50001 to 55000 in the NREGS module. In Online module use Form number 0459 to add a new block with starting number as 50001, ending number as 50120 and latest number as 50120.

If no BPL account has been opened in the block allotted then delete the block in the NREGS module; no need to add any block in the Online module.

Reports for BPL accounts is available in DBanalyzer >> Reports >> BPL Accounts.

SpeedNet 3.1.2 Revised Version ( Release Date - 23/07/2011)

SpeedNet 3.1.2 Revised Version ( Release Date - 23/07/2011) available in PTC, FTP site

  Download

This Release is specifically for providing:

i) Provisions for Prepaid/Advance Customers with Booking/Billing/Reports options.

ii) Enhanced features for Collection Agents including Billing w.r.t. acceptance of articles from Prepaid/Advance/BNPL Customers.

iii) Newly Installed and configured SpeedNet not to have BOs in Office Master - In compliance with the requirement of adding all of BOs of Pin Code Directory into SPC Site Office master data, latest BO data is available at SPC Site.
For more details, please see the New installation Notes as to how to update the latest BO data into local database.

iv) Weight Limit for Foreign EMS Articles as per Dte Lr No. 22-1/2011-DA dated 22/06/2011 is provided.

v) EPP Related : -
EPP Booking for BNPL Articles with Circle allotted Barcode prefix validation, EPP Distance Configuration for Cities, closing separate EPP Bag with EPP Articles was already provided vide release dated 20/05/2011. Delivery of EPP Articles was already available in the SpeedNet earlier version and the same is continued.
In this release we have provided – Circle Wise EPP Bag Barcode Series validation as per Dte Lr. No 10-20/2008 BD&MD dated 06/06/2011.

vi) Article/ Bag Barcode validation for Print To Post Centers who book and bag UID Articles with U series Barcodes as per Dte Lr. No. 51-53/2010-BD&MD dated 14/07/2011

vii) Handling of U Series Barcoded UID Articles at Delivery Offices: Offices other than Print To Post Centers can receive the Bags from Print to Post Centers and receive the articles, issue to post man for delivery or send for other offices for delivery with U series Barcodes.

viii)BO Bag Close with UID Bundles/Articles at Delivery Office.
When Print to Post Centers close Bags with Bundles of UID Articles to Delivery offices, there may be also Bundles for BOs of those Delivery Offices.

As those UID Bundles shouldn’t be opened at Delivery Office – BO Bag Close with UID Bundles/ Articles if any sent loose, is provided.

ix) MNOP Hub Master Data : Latest revisions to the Hub Master are available in this release. Supervisor has to use the option Master-> Hub Details and Update option to get the latest data. Latest data can be viewed thereafter. 

Download Link :  Click Here

NREGS/BPL Account Initialisation

1.Install Sanchay Post with NREGS option.
2.Run NREGS patch for MS SQL 2000 & MS SQL 2005 Ver 6.5
3.Give the sa password and save it.
4.And then click Execute patch and wait for confirmation message.
5.For HO and SO go to NREGS -> Data Entry.Login with Data entry supervisor login.
6.Then go to Intialisation -> Account Number -> and click Add.
7.Enter the account block details.
8. Then go to NREGS -> Data Entry. Login with Data entry operator login.
9.Then go to NREGS-> Open Account and open the accounts.
10.For transactions go to NREGS -> Transactions and give the account number and enter the transactions.
11. For day to day LOT entries use LOT entries.
12. After entering transactions/LOT entries open DB Analyzer give the server name.
13.Go to Reports -> Zero Balance Accounts LOT.
14.Select the BPL option and also select the account block numbers and click ok.
15. LOT will be displayed click on Print.

16.LOT will be created as file in the C:\.
17.Open the file with Microsoft Excel and then print the LOT.

18. The same transaction also will be included in Sanchaypost Regular LOT

Error 429 Solution & Error Opening Database SQL 2000

Re-register the following DLLs by using Regsvr32.exe, and then restart the computer:

C:\Program files\Common Files\System\ADO\Msado15.dll
C:\Program files\Common Files\System\Ole Db\Oledb32.dll
C:\Program files\Common Files\System\Ole Db\Sqloledb.dll
C:\WINNT\System32\Atl.dll

Use Regsvr32.exe to register the preceding DLLs.

For example, at the command prompt type (or) copy & paste and Enter OK

C:\>regsvr32 C:\Program Files\Common Files\System\ADO\Msado15.dll
C:\>regsvr32 C:\Program Files\Common Files\System\Ole Db\Oledb32.dll
C:\>regsvr32 C:\Program files\Common Files\System\Ole Db\Sqloledb.dll
C:\>regsvr32 C:\WINNT\System32\Atl.dll

List of Candidate declared as Selected on Merit in the Postmaster Grade-I examination

List of Candidate declared as Selected on Merit in the Postmaster Grade-I examination held on 12th June, 2011 from JHARKHAND Sl Roll Number Name of Candidate SC/ST Paper I Paper II Total 1 2020000022 Arun Kumar Singh 108 132 240 2 2020000015 Ganga Nand Mishra 120 114 234 3 2020000005 Hemant Kumar Pati 110 110 220 4 2020000003 K L Krishna Murthy 108 110 218 5 2020000018 Md Jasim Khan 106 110 216 6 2020000004 Pradeep Kumar Mishra 114 102 216 7 2020000006 Sanjeev Kumar 100 112 212 8 2020000007 Vinod Kumar 118 86 204 9 2020000026 Somnath 118 86 204 10 2020000003 Samshad Ahmad 100 90 190 11 2020000042 Satish Kumar SC 92 78 170 12 1920000032 Sukhlal Manjhi ST 88 76 164 Congratulation for Success to all of above Candidate

How to repair a SQL Server 2005 Suspect database

Sometimes when you connect to your database server, you may find it in suspect mode. Your database server won’t allow you to perform any operation on that database until the database is repaired.

A database can go in suspect mode for many reasons like improper shutdown of the database server, corruption of the database files etc.

To get the exact reason of a database going into suspect mode can be found using the following query,

DBCC CHECKDB (‘YourDBname’) WITH NO_INFOMSGS, ALL_ERRORMSGS

Output of the above query will give the errors in the database.

To repair the database, run the following queries in Query Analyzer,

EXEC sp_resetstatus yourDBname;

ALTER DATABASE yourDBname SET EMERGENCY

DBCC checkdb(yourDBname)

ALTER DATABASE yourDBname SET SINGLE_USER WITH ROLLBACK IMMEDIATE

DBCC CheckDB (yourDBname, REPAIR_ALLOW_DATA_LOSS)

ALTER DATABASE yourDBname SET MULTI_USER

And you are done.

You should keep one thing in mind while using the above queries that the repair mode used here , REPAIR_ALLOW_DATA_LOSS, is a one way operation i.e. once the database is repaired all the actions performed by these queries can’t be undone. There is no way to go back to the previous state of the database. So as a precautionary step you should take backup of your database before executing above mentioned queries.