Summary
When you remove Internet Explorer 8, your earlier version of Internet Explorer is restored with your customizations (such as add-in, Favorites, and your home page). However, Internet Explorer 8 is a part of Windows 7. Therefore, if you remove Internet Explorer 8, you will have to install a third-party browser to be able to browse the Internet (Only apply to Windows 7).
Resolution
To uninstall Internet Explorer 8, follow the instructions for your version of Windows. To follow these steps, you must be logged on to Windows as an administrator.
Important You cannot uninstall Internet Explorer 8 if it is set as not removable. This occurs if you install Internet Explorer 8 before you install Service Pack 3 (SP3) for Windows XP. If this scenario applies to you, then you must uninstall SP3 before you can uninstall Internet Explorer 8. For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:
950719 You cannot uninstall Internet Explorer 7 or Internet Explorer 8 after you install Windows XP Service Pack 3
Steps for Windows XP or for Windows Server 2003
To uninstall Internet Explorer 8, follow these steps:
1. Close all programs.
2. Click Start, and then click Control Panel.
3. Click Add or Remove Programs.
4. In the list of currently installed programs, click Windows Internet Explorer 8, and then click Remove.
Note If Windows Internet Explorer 8 does not appear in the list of installed updates, try the alternative steps for Windows XP or for Windows Server 2003.
5. Follow the instructions to uninstall Internet Explorer 8.
6. When the uninstall program is finished, restart your computer.
Now go to the "Did the "Let me fix it myself" steps fix the problem?" section to verify that your earlier version of Internet Explorer is restored.
Did the steps fix the problem?
1. After you restart your computer, open Internet Explorer.
2. Click About Internet Explorer on the Help menu. If Internet Explorer 6 or 7 appears in the About Internet Explorer dialog box, then you are finished with this article.
3. If Internet Explorer 8 is not removed, or you cannot open Internet Explorer 6 or 7, you can try the alternative steps or you can contact support.
Source From: http://support.microsoft.com/kb/957700
Wednesday, October 28, 2009
Tuesday, October 27, 2009
Jaya One - Duck King 王蒂鴨
Monday, October 26, 2009
Tuesday, September 29, 2009
Wednesday, August 12, 2009
Recover corrupted Database in SQL Server 2000
Recover from a corrupted Database in SQL Server 2000
This is a useful article or not I don’t know, but when your database is corrupted then this article helps you a lot.
Make sure that the database being restored is from the same Product level as the server you are restoring to. I once faced an issue when trying to restore a database from an SP4 to a non-SP4 database server.
1. Detach the corrupted MDF from Enterprise Manager.
2. Save the corrupted MDF to a safe location.
3. Now create a new database with the same name (the location must be the same as the ‘corrupted MDF and LDF’)
4. Stop the SQL Server service.
5. Now replace this MDF and LDF (New database) with the ‘corrupted MDF and LDF’
6. Start SQL Server service.
7. Launch Enterprise Manager. Now you should be able to see the database in suspect mode.
8. Launch Query Analyzer and select the master database. Issue the following commands in this order:
Order 1:
sp_configure ‘allow updates’, 1
go
Order 2:
reconfigure with override
go
9. You can now make changes to the system catalog tables.
10. Now to check the status of our database. Issue the following command
select status from sysdatabases where name’ your databae name’ (replace with your database name)
NOTE: remember the status code
11. Now execute the following command:
update sysdatabases
set status=32768 where name=’your database name’
12. Next restart SQL Server Service.
13. You will now be in Emergency Mode.
14. Now create a destination recovery database, called dbrecover and try to push data from the corrupt database to the new dbrecover database using DTS.
15. Now issue the following undocumented command:
DBCC rebuild_log(‘your database name’, ‘new log filename with path’)
àDBCC rebuild_log ('neptune', 'D:\MSSQL2000\MSSQL\Data\test_log.ldf')
16. After this successful execution, you will need to get into your database, so issue the following commands:
Step 1:
Use master
go
sp_dboption ‘your database name’, ‘single_user’, ‘true’
go
Step 2:
Use master
go
DBCC CHECKDB(‘your database name’, REPAIR_ALLOW_DATA_LOSS)
go
17. Finally set your database back to a normal status by issuing the following command:
Step 1:
Use master
go
update sysdatabase
set status=0 where name=’your database name’
go
18. Now you can see that your database is back online.
19. As a precautionary measure, please disable updates the sysem catalogs immediately by issuing the following command:
Step 1:
Use master
go
sp_configure ‘allow update’, 0
go
Step 2:
Use master
go
Reconfigure with override
go
This is how one recovers a corrupted mdf database and brings it back online.
This is a useful article or not I don’t know, but when your database is corrupted then this article helps you a lot.
Make sure that the database being restored is from the same Product level as the server you are restoring to. I once faced an issue when trying to restore a database from an SP4 to a non-SP4 database server.
1. Detach the corrupted MDF from Enterprise Manager.
2. Save the corrupted MDF to a safe location.
3. Now create a new database with the same name (the location must be the same as the ‘corrupted MDF and LDF’)
4. Stop the SQL Server service.
5. Now replace this MDF and LDF (New database) with the ‘corrupted MDF and LDF’
6. Start SQL Server service.
7. Launch Enterprise Manager. Now you should be able to see the database in suspect mode.
8. Launch Query Analyzer and select the master database. Issue the following commands in this order:
Order 1:
sp_configure ‘allow updates’, 1
go
Order 2:
reconfigure with override
go
9. You can now make changes to the system catalog tables.
10. Now to check the status of our database. Issue the following command
select status from sysdatabases where name’ your databae name’ (replace with your database name)
NOTE: remember the status code
11. Now execute the following command:
update sysdatabases
set status=32768 where name=’your database name’
12. Next restart SQL Server Service.
13. You will now be in Emergency Mode.
14. Now create a destination recovery database, called dbrecover and try to push data from the corrupt database to the new dbrecover database using DTS.
15. Now issue the following undocumented command:
DBCC rebuild_log(‘your database name’, ‘new log filename with path’)
àDBCC rebuild_log ('neptune', 'D:\MSSQL2000\MSSQL\Data\test_log.ldf')
16. After this successful execution, you will need to get into your database, so issue the following commands:
Step 1:
Use master
go
sp_dboption ‘your database name’, ‘single_user’, ‘true’
go
Step 2:
Use master
go
DBCC CHECKDB(‘your database name’, REPAIR_ALLOW_DATA_LOSS)
go
17. Finally set your database back to a normal status by issuing the following command:
Step 1:
Use master
go
update sysdatabase
set status=0 where name=’your database name’
go
18. Now you can see that your database is back online.
19. As a precautionary measure, please disable updates the sysem catalogs immediately by issuing the following command:
Step 1:
Use master
go
sp_configure ‘allow update’, 0
go
Step 2:
Use master
go
Reconfigure with override
go
This is how one recovers a corrupted mdf database and brings it back online.
Subscribe to:
Posts (Atom)