HyperV virtual machine power-off, unable to access IIS Site, SharePoint configuration database none

HyperV virtual machine power-off yesterday. After restarting, it found that it could not log on to SharePoint. After checking IIS, it found that all sites could not be opened and the error message "applicationhost. configisnotwell-formedxml ", applicationhost. the config file is in a configuration file, and the file is damaged due to power failure. The solution is

The Hyper V virtual machine was powered off yesterday. After restarting, the system found that it could not log on to SharePoint. After checking IIS, it found that all the sites could not be opened and the error message "applicationhost. config is not well-formed xml ", applicationhost. the config file is in a configuration file, and the file is damaged due to power failure. The solution is

The Hyper V virtual machine was powered off yesterday. After restarting, the system found that it could not log on to SharePoint. After checking IIS, it found that all the sites could not be opened and the error message "applicationhost. config is not well-formed xml ", applicationhost. the config file is in a configuration file, and the file is damaged due to power failure. The solution is to "C: recover this file in the \ windows \ system32 \ inetsvr \ backup \ "folder (SEE ). Then restart two services: 1 Windows Process Activation service, 2 World Wide Web Publishing Service.

After the IIS problem is solved, you still cannot log on to SharePoint and the error message "Connot connect to the configuration database" is displayed ". Check in The database and find that The database "cmdpoint_config" and "cmdpoint_admincontent" cannot be opened, and The error message "The database is not accessible." is displayed .". Use the following SQL statement to check the database status:

select state_desc from sys.databases where name='SharePoint_Config'

The database status is "Recovery_Pending". The solution is to execute the following SQL statement (see ):

ALTER DATABASE [DB_Name] SET  SINGLE_USER WITH NO_WAITALTER DATABASE [DB_Name] SET EMERGENCY;DBCC checkdb ([DB_Name], REPAIR_ALLOW_DATA_LOSS  )ALTER DATABASE [DB_Name] SET online;ALTER DATABASE [DB_Name] SET  Multi_USER WITH NO_WAIT