28,391
社区成员
发帖
与我相关
我的任务
分享IIS5坏了怎么办？
我用的是WIN 2000 ADVANCED SERVER，用IIS的时候提示
“连接**错误，发生意外错误0x80074002，你想继续尝试这连接吗？
”，但根本连接不上？？该怎么办？？？？
“连接**错误，发生意外错误0x80074002，你想继续尝试这连接吗？
”，但根本连接不上？？该怎么办？？？？
...全文
请发表友善的回复…
发表回复
tripofdream 2001-07-23
- 打赏
- 举报
MSDN
y928 2001-07-23
- 打赏
- 举报
哦，好，帮助里的吗？？？
tripofdream 2001-07-23
- 打赏
- 举报
Error Connecting to server, unexpected error 0x80074002 occurred
Do you wish to continue to attempt to connect in the future?
Where server is the name of the local computer.
CAUSE
This error can be occur when the metabase has become corrupted. The metabase stores settings used in Internet Information Services.
RESOLUTION
To correct this problem, you should attempt to restore the metabase from a backup. If this does not correct the problem, however, you may need to restore the metabase from a system backup.
The metabase, Metabase.bin, is located in the (default) C:\WINNT\System32\inetsrv (%WinDir%\System32\inetsrv) directory.
How to Manually Restore the Metabase When No Proper Backup Exists or the MMC Won't Start
--------------------------------------------------------------------------------
The information in this article applies to:
Microsoft Internet Information Server 4.0
--------------------------------------------------------------------------------
SUMMARY
To restore the metabase, it is recommended that you use the Restore action in the Microsoft Management Console (MMC). However, if no backup of the metabase was ever created by the MMC, or if the MMC cannot be started because the metabase has been corrupted too badly, you can attempt to manually restore the metabase by using one of the methods described in the MORE INFORMATION section of this article.
MORE INFORMATION
Note: You should back up the metabase regularly using the Backup action in the MMC.
For information on how to back up and restore the metabase by using the MMC, see the IIS Readme file, located at http://localhost/iishelp/iis/htm/core/iisread.htm#general (assuming that the product documentation is installed on the local computer).
If a Backup File Created by the MMC is Available
If the Backup action in the MMC was used to create a backup file (FileName.mdBackupNumber), but the MMC cannot be opened because the current metabase is corrupted, perform the following steps to manually restore the metabase from the FileName.mdBackupNumber file.
Stop all IIS services, and other services that rely on IIS (such as third-party applications or Microsoft Site Server).
Note: To stop IIS and its dependent services, use the NET STOP IISADMIN /Y command. For additional information, please see the following article in the Microsoft Knowledge Base:
Q236166 Using Net Stop and Net Start Commands to Force IIS Services to Re-Read the Registry
Rename the corrupted metabase file, Metabase.bin, to a new name such as Metabase.bad. The Metabase.bin file is located in the %SystemRoot%\System32\Inetsrv folder.
Copy the MMC backup metabase file, FileName.mdBackupNumber, which is located in the %SystemRoot%\System32\Inetsrv\Metaback folder, to the %SystemRoot%\System32\Inetsrv folder. Rename it to Metabase.bin.
Restart the computer.
If an Older Copy of the Metabase.bin File Exists
If no backup file created by the MMC is available, but an older copy of the Metabase.bin file exists elsewhere (typically on a system tape backup), perform the following steps:
Stop all IIS services, and other services that rely on IIS (such as third-party applications or Microsoft Site Server).
Note: To stop IIS and its dependent services, use the NET STOP IISADMIN /Y command. For additional information, please see the following article in the Microsoft Knowledge Base:
Q236166 Using Net Stop and Net Start Commands to Force IIS Services to Re-Read the Registry
Rename the corrupted metabase file, Metabase.bin, to a new name such as Metabase.bad. The Metabase.bin file is located in the %SystemRoot%\System32\Inetsrv folder.
Copy the older copy of Metabase.bin file to the %SystemRoot%\System32\Inetsrv folder.
Restart the computer.
If No MMC Backup or Older Copy of the Metabase.bin File Exists
If no backup file created by the MMC is available, and no older copy of the Metabase.bin file exists, a temporary backup of the metabase may still exist.
When the metabase is updated through the MMC or another process, a temporary backup of the metabase may be created. If the update was interrupted (which is possibly the cause of the corruption in the first place), there is a chance that this temporary file may still exist.
This temporary file is named either Metabase.bak or Metabase.bin.bak, and is located in the %SystemRoot%\System32\Inetsrv folder. If this temporary file exists, perform the following steps to attempt to restore the metabase:
Stop all IIS services, and other services that rely on IIS (such as third-party applications or Microsoft Site Server).
Note: To stop IIS and its dependent services, use the NET STOP IISADMIN /Y command. For additional information, please see the following article in the Microsoft Knowledge Base:
Q236166 Using Net Stop and Net Start Commands to Force IIS Services to Re-Read the Registry
Rename the corrupted metabase file, Metabase.bin, to a new name such as Metabase.bad. The Metabase.bin file is located in the %SystemRoot%\System32\Inetsrv folder.
Rename the temporary backup file (Metabase.bak or Metabase.bin.bak) to Metabase.bin.
Restart the computer.
If No Metabase Backup File Exists
If there are no backup files available of the metabase, the only way to restore IIS functionality is to do the following. Please note that all IIS settings stored in the metabase are lost, however.
Uninstall the Windows NT Option Pack. For additional information, please see the following article in the Microsoft Knowledge Base:
Q187870 How to Remove and Reinstall the Windows NT 4.0 Option Pack
Uninstall Internet Explorer.
Delete the Metabase.bin file from the %SystemRoot\System32\Inetsrv\ folder.
Install Internet Explorer.
Install the Windows NT Option Pack.
Additional query words: meta base back up registry corruption hose hosed hung hangs freezes frozen Internet Service Manager ISM
Do you wish to continue to attempt to connect in the future?
Where server is the name of the local computer.
CAUSE
This error can be occur when the metabase has become corrupted. The metabase stores settings used in Internet Information Services.
RESOLUTION
To correct this problem, you should attempt to restore the metabase from a backup. If this does not correct the problem, however, you may need to restore the metabase from a system backup.
The metabase, Metabase.bin, is located in the (default) C:\WINNT\System32\inetsrv (%WinDir%\System32\inetsrv) directory.
How to Manually Restore the Metabase When No Proper Backup Exists or the MMC Won't Start
--------------------------------------------------------------------------------
The information in this article applies to:
Microsoft Internet Information Server 4.0
--------------------------------------------------------------------------------
SUMMARY
To restore the metabase, it is recommended that you use the Restore action in the Microsoft Management Console (MMC). However, if no backup of the metabase was ever created by the MMC, or if the MMC cannot be started because the metabase has been corrupted too badly, you can attempt to manually restore the metabase by using one of the methods described in the MORE INFORMATION section of this article.
MORE INFORMATION
Note: You should back up the metabase regularly using the Backup action in the MMC.
For information on how to back up and restore the metabase by using the MMC, see the IIS Readme file, located at http://localhost/iishelp/iis/htm/core/iisread.htm#general (assuming that the product documentation is installed on the local computer).
If a Backup File Created by the MMC is Available
If the Backup action in the MMC was used to create a backup file (FileName.mdBackupNumber), but the MMC cannot be opened because the current metabase is corrupted, perform the following steps to manually restore the metabase from the FileName.mdBackupNumber file.
Stop all IIS services, and other services that rely on IIS (such as third-party applications or Microsoft Site Server).
Note: To stop IIS and its dependent services, use the NET STOP IISADMIN /Y command. For additional information, please see the following article in the Microsoft Knowledge Base:
Q236166 Using Net Stop and Net Start Commands to Force IIS Services to Re-Read the Registry
Rename the corrupted metabase file, Metabase.bin, to a new name such as Metabase.bad. The Metabase.bin file is located in the %SystemRoot%\System32\Inetsrv folder.
Copy the MMC backup metabase file, FileName.mdBackupNumber, which is located in the %SystemRoot%\System32\Inetsrv\Metaback folder, to the %SystemRoot%\System32\Inetsrv folder. Rename it to Metabase.bin.
Restart the computer.
If an Older Copy of the Metabase.bin File Exists
If no backup file created by the MMC is available, but an older copy of the Metabase.bin file exists elsewhere (typically on a system tape backup), perform the following steps:
Stop all IIS services, and other services that rely on IIS (such as third-party applications or Microsoft Site Server).
Note: To stop IIS and its dependent services, use the NET STOP IISADMIN /Y command. For additional information, please see the following article in the Microsoft Knowledge Base:
Q236166 Using Net Stop and Net Start Commands to Force IIS Services to Re-Read the Registry
Rename the corrupted metabase file, Metabase.bin, to a new name such as Metabase.bad. The Metabase.bin file is located in the %SystemRoot%\System32\Inetsrv folder.
Copy the older copy of Metabase.bin file to the %SystemRoot%\System32\Inetsrv folder.
Restart the computer.
If No MMC Backup or Older Copy of the Metabase.bin File Exists
If no backup file created by the MMC is available, and no older copy of the Metabase.bin file exists, a temporary backup of the metabase may still exist.
When the metabase is updated through the MMC or another process, a temporary backup of the metabase may be created. If the update was interrupted (which is possibly the cause of the corruption in the first place), there is a chance that this temporary file may still exist.
This temporary file is named either Metabase.bak or Metabase.bin.bak, and is located in the %SystemRoot%\System32\Inetsrv folder. If this temporary file exists, perform the following steps to attempt to restore the metabase:
Stop all IIS services, and other services that rely on IIS (such as third-party applications or Microsoft Site Server).
Note: To stop IIS and its dependent services, use the NET STOP IISADMIN /Y command. For additional information, please see the following article in the Microsoft Knowledge Base:
Q236166 Using Net Stop and Net Start Commands to Force IIS Services to Re-Read the Registry
Rename the corrupted metabase file, Metabase.bin, to a new name such as Metabase.bad. The Metabase.bin file is located in the %SystemRoot%\System32\Inetsrv folder.
Rename the temporary backup file (Metabase.bak or Metabase.bin.bak) to Metabase.bin.
Restart the computer.
If No Metabase Backup File Exists
If there are no backup files available of the metabase, the only way to restore IIS functionality is to do the following. Please note that all IIS settings stored in the metabase are lost, however.
Uninstall the Windows NT Option Pack. For additional information, please see the following article in the Microsoft Knowledge Base:
Q187870 How to Remove and Reinstall the Windows NT 4.0 Option Pack
Uninstall Internet Explorer.
Delete the Metabase.bin file from the %SystemRoot\System32\Inetsrv\ folder.
Install Internet Explorer.
Install the Windows NT Option Pack.
Additional query words: meta base back up registry corruption hose hosed hung hangs freezes frozen Internet Service Manager ISM
y928 2001-07-23
- 打赏
- 举报
就是要问该怎样修复？？
epowerlab 2001-07-23
- 打赏
- 举报
是启动的时候吗？
试着修副一下
试着修副一下
y928 2001-07-23
- 打赏
- 举报
还有没有办法？？
truemichael 2001-07-23
- 打赏
- 举报
重装喽
