Add maturity value in sanchay post 7.5 SSA

for add Maturity value


Click here

on request of Ravi veer

SSA DATA ENTRY MODULE LUNCH BY SDC

Patch for data entry of SSA released by SDC. Patch 14(SSA Dataentry)

Please take backup of sanchay post before install these patches.

 Click here for Patch 14

Click Here for Patch 15

Not able to open TD account in TD data entry

Not able to Open New Account in TD Data Entry Module

Problem with TD Data Entry v7.5 Patch 8.1

After Update Patch 5 or Patch 6 or Patch 8 or Patch 8.1

• Not able to Open New Account.
• Could not click on Amount field.

Solution : TD Data Entry

In Sanchay Post 7.5 after service pack 1 update we are unable to access TD Data entry.

• Use Data Entry Module alone in Sanchay Post 7.5

Note: This is only for TD Data Entry
Click here

Process of Disaster Request for pending eMOs

Steps for Updating Paid Date of eMO
 The Supervisor has to request for disaster recovery data through Transactions > Disaster Recovery > Disaster request data Menu Option. There he has to select the pincode for which disaster data is required and enter remarks.
 Once eMO Communication is run, disaster request will be sent to central server and the data for disaster recovery will be received in the next or subsequent calls.
 Once the data for disaster recovery is received from central server, the Operator has to go to DataEntry >Disaster recovery > Disaster paid entry option. There he has to select the office for which disaster paid entry is to be done. Select PNR number and enter the paid particulars.
 Thereafter, the supervisor has to perform disaster paid verification in respect of disaster paid entries done by the operator through Transactions > Disaster Recovery > Disaster paid verification option.
 After this when eMO Communication is run, disaster paid entries data will be transmitted to Server and paid data will be updated

PLI SERVICE TAX CALCULATOR 2.2

Click Here

EMO COMMUNICATION ERROR [PADDING IS INVALID AND CAN NOT BE REMOVED ERROR

Please do the following carefully.

warning ! Please do the following carefully. 


1. stop the eMO Client application if running. 

2. Open the data folder Inside RXD Folder of eMO client installation path.

3. Select details option in View menu on the top of explorer.(View->details). All files will be shown with file type and date modified.

4. Sort the files by modified date(Click on date modified column once or twice).

5. Select and cut all the files received on oldest date and time and copy into to seperate folder on desktop.( these file might be corrupted).

6. Delete all the files with file type qsq_tmp in data folder of rxd.

7. start the eMO client application.

8. Check the eMO after 10-15 minutes.

REPAIR SUSPECT DATABASE

Repair Suspect Database in SQL Server

Introduction

There can be a possibility that when you connect to an SQL Server Instance you will find the database being marked as SUSPECT. During such scenarios, you will not be able to connect to the database. In this article we will go through the steps which you need to follow to recovery a database which is marked as SUSPECT. The steps mentioned in this article works on SQL Server 2005 and higher versions.

Some of the reasons why an SQL Server database can be marked as SUSPECT

1.    1. Database could have been corrupted.
2. There is not enough space available for the SQL Server to recover the database during startup.
3. Database cannot be opened due to inaccessible files or insufficient memory or disk space.
4. Database files are being held by operating system, third party backup software etc.
5. Unexpected SQL Server Shutdown, Power failure or a Hardware failure.

Due to a hardware failure one of our database namely BPO was marked SUSPECT when the SQL Server came back online. Already due to the hardware failure we had downtime for more than two hours and adding to that when the server came back online our mostly critical database was marked as SUSPECT.

Steps to Recover a Database Marked as SUSPECT

1. Execute the below mentioned TSQL code to identify all the databases which are marked as SUSPECT.

USE_master
GO

SELECT NAME,STATE_DESC FROM SYS.DATABASES 
WHERE STATE_DESC='SUSPECT'
GO

2. Open the latest SQL Server Error Log and check for errors logged for the database which is marked as suspect. You can open SQL Server Error Log by expanding Management Node à SQL Server Error Logs. In my server I could find below mentioned entries in SQL Server Error Logs.

Sample Error Messages within SQL Server Error Log when database is marked as SUSPECT

Starting up database 'BPO'.
Error: 9003, Severity: 20, State: 9.

The log scan number (189624:16:2) passed to log scan in database 'BPO' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.

Error: 3414, Severity: 21, State: 1.

An error occurred during recovery, preventing the database 'BPO' (database ID 10) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.

CHECKDB for database 'BPO' finished without errors on 2009-12-15 11:30:28.320 (local time). This is an informational message only; no user action is required.

3. When a database is in SUSPECT mode you will not be able to get connected to the database. Hence you need to bring the database first in EMERGENCY mode to repair the database. Execute the below mentioned TSQL code to bring the database in EMERGENCY mode.

USE_master
GO 

ALTER DATABASE BPO SET EMERGENCY
GO

Once the database is in EMERGENCY mode you will be able to query the database.

 

4. Execute the DBCC CHECKDB command which will check the logical and physical integrity of all the objects within the specified database.

DBCC CHECKDB (BPO) 
GO

5. Next step will be to bring the user database in SINGLE_USER mode by executing the below mentioned TSQL code.

ALTER DATABASE BPO SET SINGLE_USER WITH ROLLBACK IMMEDIATE 
GO

6. Once the database is in SINGLE_USER mode execute the below TSQL code to repair the database. When you repair your database using REPAIR_ALLOW_DATA_LOSS option of DBCC CHECKDB command there can be some loss of data. Once the database is successfully repaired using REPAIR_ALLOW_DATA_LOSS option of DBCC CHECKDB command then there is no way to go back to the previous state.

DBCC CHECKDB (BPO, REPAIR_ALLOW_DATA_LOSS) 
GO

7. Finally, execute the below mentioned TSQL command to allow MULTI_USER access to the database.

ALTER DATABASE BPO SET MULTI_USER
GO

   

Conclusion

In this article you have seen how you can recover a database which is marked SUSPECT.

Read more: http://www.mytechmantra.com/LearnSQLServer/Repair_Suspect_Database_P2.html#ixzz3Y0iO3nw9 

PLI SERVICE TAX CALCULATOR AND READY RECKONER FOR FPOs

As per the revised rate of Service Tax for PLI / RPLI w.e.f. 01.06.2015, I have developed a Calculator for the easy use at Computerized Post Offices. I have also prepared a Ready Reckoner Table for the easy use at non-Computerized Post Offices and Branch Offices. The download links are given below.

Click here

Root element is missing in any communication

R Net Communication configuration file may corrupt due to HDD issues or System may Suddenly down. while execute R Net Communication 

Click Here

Pamphlet for Interest and Maturity Value in India Post

Click here

SSA Dataentry process (by manraj)

Click here

UPDATE PENDING FORM ERROR IN SANCHAY POST 7.5

CLICK HERE

R NET FINA L SOLUTION FOR APS WEF 01 MAY 2015

CLICK HERE

ONLY FOR UPDATE OFFICE MASTER

RD DEFULAT SOLUTION FOR APS AFTER 15TH

CLICK HERE

Sanchay post passbook printer setting

SANCHAYPOST PASSBOOK PRINTER INSTALLATION & CONFIGURATION
PassBook - Printer Settings
1. Press station 1 + local +station2 & ON the printer (30sec)& insert the paper.
2. it shows station1=continue,station2=skip,local=config
3. Press local, it shows Menu : config
4.. Press station1 to continue until the printer name display as OLEVETTI
5. Press station2, the display changes to IBM
6. continue press station1 button until it displays save changes to Y
7. switch off the printer and swith on
Add New PASSBOOK PRINTER(It is for COM1 / Serial Port)
Start -> Setting -> printer -> Add Priner -> next -> Local Printer -> Next -> Select COM1 - Serial port -> Manufacturer ( IBM) -> Printers ( IBM Pro Printer 1 or 2) Give Name as ( PASSBOOK PRINTER) -> Next -> Next -> Finsih
* for Vista OS : Select Gereric -> 9 Pin Compatible Wide
Papper Settings:
Printer and Fax (Inside the Window) Right Click in the Blank space -> Server Properties -> Tick on the Create New Form -> Form Name ( give name as "PASSBOOK" ) -> Measurement ( in Inch)Width: 8.20 Left : 0.20 Top : 0.70Hight : 5.80 Right: 0.00 Bottom : 0.20
Save
Right Click Installed PASSBOOK PRINTER-> Properties -> 1. Devise Setting -> Select PASSBOOK and Apply2. Devise Setting -> Printing Preferences -> Advanced -> Select Paper size PASSBOOK3. Right Click -> properties -> Ports -> COM1 -> configure port -> Flow Control -> Xon / Xoff -> Apply -> OK
Set as " PASSBOOK PRINTER " as DefaultTry to Print SB Passbook Best

INVALID AADHAR ID ERROR IN SANCHAY POST 7.5

Click Here

Some important things about r net communication problems

Some important  things  for r net communication 

If r net communication  is runing but files not transmitted.

First check it

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
Delete  all rows below this address

Secondly  check it

Go to the folder c:\program  files\r net communication \TXD (open it there is one another foder name txd1, and other files check there are one notpad file delete  the notpad file and run r net communication  again) and check the notpad file in txd1 folder.

From
WO Manraj Singh
Sys admin

Sanchay post 7.5 (full)

Click here

Nregaemo database error in sanchay post 7.5 (sukanya samridhi Account)

Nregaemo database create error Click here  

happy lohri dear friends

Sanchay Post-DCL is not valid User in Databases for SQL 2000 / 2005 / 2008

After Restore the Sanchay Post databases into SQL Server 2000 / SQL Server 2005 / SQL Server 2008 it shows an one of the below error message 

 

 Server user 'dcl' is not a valid user in database 'POST'

Download Click Here