Online Lessons on Different Categories

SB Order 10/2012 - Change in text of column no.2 printed in the Standardized Uniform Savings Bank Passbook from Page No.2 to 24

Posted by SYSTEM ADMINISTRATOR Wednesday, 22 August 2012

Change in text of column no.2 printed in the Standardized Uniform Savings Bank Passbook from Page No.2 to 24

FOR ORDERS CLICK HERE

REVISION OF POSTAGE RATES OF FOREIGN PARCELS (AIR/SAL) W.E.F. FROM SEPTEMBER 2012.

View / Download orders of new postal foreign rates

R NET COMMUNICATION MODULE-COMMON PROBLEMS NOTICED AND SOLUTION

In some of the sub offices, R Net module   stops automatically.  Then data will not be transmitted to central server.     Remove the Rnet communication module from the Auto start. For this select the option RUN from start menu of windows and type  MSCONFIG  andunckeck  Rnetcommunication.exe from startup option.  Then add a scheduled task to run the R net commincation.exe using the option Accessories--->system tools--->Task scheduler(in win 7) /scheduled tasks(in win XP)   option.  While adding the scheduled task do not select the option, When I logon. Select the option Daily and give a time to run the R net communication .exe.  The time should be  the time  after 10 or 15 minutes when the server and client system started.  Suppose server and client starts at 9 O clock, then give the time as 09:10. 

  In the case of some sub offices, booking details are updated in site. But Delivery details are not updated in site. In this case check the following.

a) Check whether Non delivery code is given correctly in My office->environment of postman module.   Non delivery code in the case of delivery office will be  00

b) check whether communication module path given is correct or not.

  In some of the offices it is noticed that even though the communication module is running Data is not transmitted to central server.  In that case please check whether   trxcheck.log file is there in C:\Program Files\RegisterNet Communication\TXD  folder.  If present, delete this file. Data will be transmitted to Central server.

An office will reflect in R Net enabled office list on a particular day , only when  booking of RL is done on that day. The delivery data will be updated in the site correctly and that office will reflect in Delivery MIS. 

Posted by System Administrators, Indiapost,Kerala

TDS Software New

TDS Software

Download 

Software Developed by
R.Karunagaran
System Manager
Tirupattur HPO – 635601
Mobile :9894213404
Email: Karunagaran78@Gmail.com

Did you know the action of Function Keys (F1 - F12)

Did you Know Each F Keys and for What it actually?

F1-Help
F2-Rename
F3-Search
F4-Address Bar
F5-Refresh
F6-Spelling
F8-Safe Mode
F10-Menu Bar
F11-Re-size
F12-Save

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.

SQL server database can go in suspect mode for many reasons; some of them are given below:

Improper shutdown of the database server
Corruption of the database files
Unavailable device files
Unavailable database files
Database resource used by operating system
SQL Server incorrectly asserts free data page space when a row is inserted



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


SUPPOSE YOUR DATABASE NAME IS TREASURY THEN

DBCC CHECKDB (TREASURY) 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 TREASURY;

ALTER DATABASE TREASURY SET EMERGENCY

DBCC checkdb(TREASURY)

ALTER DATABASE TREASURY SET SINGLE_USER WITH ROLLBACK IMMEDIATE

DBCC CheckDB (TREASURY, REPAIR_ALLOW_DATA_LOSS)

ALTER DATABASE TREASURY 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.

Courtesy:-MRSUPPORT