Sabka Dost....... India Post...... DISCLAIMER CERTIFICATE - All the information on this website is published in good faith and for general information purpose only. We do not make any warranties about the completeness, reliability and accuracy of this information. Any action you take upon the information on our website is strictly at your own risk. And we will not be liable for any losses and damages in connection with the use of our website. From our website, you can visit other websites by following hyperlinks to these sites. While we strive to provide only links to useful and ethical websites, we have no control over the content and nature of these sites and the links to other websites do not imply a recommendation for all the content found on these sites. Please be also aware that when you leave our website, other sites may have different privacy policies

Tuesday, June 28, 2011

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.

Wednesday, March 2, 2011

Error in speednet communication

Please download and replace the new communication exe from
http://www.sendspace.com/file/swrhk2

Tuesday, March 1, 2011

Error while configuring speedpost city in Point of Sale

1.  Please download the file SPC.exe  from http://www.sendspace.com/file/48zu38
2. Copy this exe to the installation folder i.e. "C:\Program Files\Meghdoot
Millennium - Point Of Sale" and run the exe file and provide the Point of Sale SQL server name
3. Login as supervisor to Point of Sale and go to menu My Office -> Environment
click on Speed Post Tab and select you SPC City name and click on OK button.

Tuesday, February 15, 2011

Despatch Solution

Item cannot be found in the collection to cooresponding to the requested name or ordinal.
Down load the file .
http://www.sendspace.com/file/66tt8y

Saturday, January 22, 2011

TO CHECK WARRANTY OF SYSTEMS AND PRINTERS

EPSON WARRANTY CHECK
http://echannel.epson.com.sg/epson/warrantyin.nsf/eWarranty?Openframeset

HP WARRANTY CHECK
http://www13.itrc.hp.com/service/ewarranty/warrantyInput.do

HP Business products warranty check (Eg:- For Scanners)
http://h20000.www2.hp.com/bizsupport...jsp?country=IN

SEAGATE WARRANTY CHECK
http://support.seagate.com/customer/warranty_validation.jsp?form=0

WESTERN DIGITAL WARRANTY CHECK
http://support.wdc.com/warranty/index.asp?lang=en

Sunday, October 31, 2010

eMO Updates 161010

Some additional reports has been given which may facilitate to reduce the - Pending Not Paid EMOs.

Please do the following
1. Download the emoupdate.zip file
2. Extract the contents. There will be following files eMO,

emo15102010.exl , emooffices29092010.exl, emoPincodes29092010.exl and a Readme.txt file

3. if you have not upgraded the emodatabase with Meghdoot 6.6 sp1 released during April /May 2010, please upgrade with Meghdoot 6.6 SP1. Without upgradation, if this update is applied it may cause some errors in the new reports.
4. Take a backup of emo database and existing emo.exe and place in safe location.
5. If steps 2 and 3 are statisfied, proceed with instructions in Readme.txt
6. Anyissues /errors during upgradation please mail to ptcdesk@gmail.com
Download 

Sunday, October 17, 2010

How to add BO in SPCC Office updation

FIRST YOU HAVE TO ADD THE BOS AS THE LINKED OFFICES. FOR THAT GO TO THE FOLLOWING . YOU HAVE TO LOGIN WITH USER NAME & PASSWORD FOR YOUR SPC.A SITE WITH A BANNER AS SPEED NET OFFICE UPDATION WILL BE OPENED.THERE GO IN THE FOLLOWING MANNER , ADD ADDITIONAL OFFICES . FILL UP THE OFFICE DETAILS SUCH AS BO'S NAME ITS PINCODE , IMPORTANT YOU HAVE TO GIVE OPTION NO FOR THE IS DELIVERY OFFICE : NO. AND THEN CLICK SEND . SAME WAY UPDATE ALL THE BOS . THEN GO TO DOWNLOADS . IN THAT Download ALL data CircleWise -> SELECT YOUR CIRCLE (TAMILNADU). AND THEN CLICK DOWNLOAD . A TEXT FILE WHICH CONTAINS THE FILE NAME AS SPCC------(your spc pincode) WILL BE DOWNLOADED.THEN GO TO SPEED NET COMMUNICATION , GO TO TOOLS -> UPDATE OFFICE DATA FROM SERVER BROWSE THE FILE DOWNLOADED AND THEN CLICK UPDATE NOW. A MESSAGE WILL APPEAR AS " YOUR OFFICE DATA HAS BEEN SUCCESSFULLY UPDATED MESSAGE WILL APPEAR. NOW GO TO SPEED NET APPLICATION . GO TO DELIVER -> INVOICING -> ARTILE FOR OTHER OFFICES . THERE YOU CAN FIND THE BO NAME IN THE TAB OFFICES. INVOICE THE ARTICLE FOR THAT BO AND AFTER DELIVERY REMARKS COMES UPDATE THE SAME THROUGH REMARKS FROM OTHER OFFICES -> SPEED POST. CALL THE SPEED NET COMMUNICATION. THATS ALL .