SELECT name, physical_name, state_desc FROM sys.master_files ORDER BY database_id (go) List the files referenced in system table:.Start the SQL server service in recovery mode:.In case the above link becomes unavailable, here's a short summary: To correct this, allowing uninstallation, this worked for me:ġ) Set service to use local account (Start -> Local Services -> SQL-Server->Properties -> Log on -> Local System acccount) In my case the reason for the uninstaller getting stuck at SqlEngineConfigAction_repair_validation_Cpu64 were invalid file paths in the SQL server's system tables.
#Uninstall microsoft sql server 2008 r2 64 bit how to
So to clarify, the question is how to resolve the issue of the Repair, Remove, or Install process hanging?Īs a followup, it turns out the root cause of the corruption was shutting down the Windows 7 PC without first explicitly stopping the SQL Server services, even though SQL Server Express was not actively being used at the time.ĮDIT3: Issue seems to have been resolved in SQL Server 2014 Express. I'm guessing the down-vote was because this was not stated in the form of a question. (provider: SSL Provider, error: 0 - The wait operation timed out.)(Microsoft SQL Server, Error: 258) It either tries forever with no timeout or error displayed, or it displays this error:Ī connection was successfully established with the server, but then an error occurred during the pre-login handshake. SSMS (SQL Server Management Studio) fails to connect to the instance. Error 1053: The service did not respond to the start or control request in a timely fashion. Windows could not start the SQL Server (SQLEXPRESS) service on Local Computer. When the service is manually stopped and then started, it displays this error: "SQL Server (SQLEXPRESS)" service has a status of "Started" on system reboot, but gets stuck in "Starting" status when the service is manually restarted using the Restart option. Symptoms of the database corruption, in case this helps: For other attempts, the services were manually stopped, and changed from "Automatic" to "Manual". When trying to install a 2nd instance, the install process seemed to hang at the SqlEngineDBStartConfigAction_install_configrc_Cpu64 step.įor some of the attempts, the SQL Server services were not manually stopped beforehand.
When trying to remove the instance, the uninstall process seemed to hang at the SqlEngineConfigAction_remove_validation_Cpu64 step. It was at that step for a long time with no noticeable CPU usage, so I finally cancelled the repair process. When trying to repair the instance, the repair process seemed to be stuck at the SqlEngineConfigAction_repair_validation_Cpu64 step. I suspect it was related in some way to my use of Entity Framework, but have no proof yet. An instance of SQL Server 2012 Express became corrupted somehow.
0 kommentar(er)
