Monday, August 27, 2012

How to Deal with SQL Server ‘Error 10022’

English: Labeled (SQL) database icon with shor...
English: Labeled (SQL) database icon with shortcut identification (Photo credit: Wikipedia)
It has been seen that whenever you are installing SQL Server at some point you will inevitably encounter this famous error, “Windows could not start the SQL Server ([myinstancename]) on Local Computer. To know more about it you can review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 10022.”

When it happens, here's what to do: 
1. Don't try to use any step, first find the cause of the error which will help you to find the best solution for the error. The most common reason of this error is sql database corruption.
2. Step away by starting the MS SQL Server from the Windows Services apple to try to bypass the Configuration Manager. It will help you to solve the issue. You can also do it from command prompt.
3. Take another possibility while using second step. It is also possible that when user runs the command, user gets an error message which may display as: "Your SQL Server installation is either corrupt or has been tampered with (Error getting instance ID from name.). Please uninstall then re-run setup to correct this problem". This error is a symbol of huge trouble. As the error recommended to re-install the application, it may or may not solve the problem, and even worsen it by damaging or corrupting the database leading to the corruption of the MDF files.
4. If condition get worse or it can corrupt your database then only Third Party SQL  Database Repair Tool will help in this condition.
5. Another solution is, try to edit the registry entries. It needs locating of the following: HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server.
6. There may be some chances of permission issues, so also correct it.
7. If this does not work, then the last resort is un-install the SQL Server, so that all the SQL entries can be successfully removed from the registry. Now install the application again. Hopefully After installation, all the related problems of installation will get resolved.
8. If the problem still remains same then you should restore your database from updated backup.
9. Google it, In 1% case, it can be happen that after using all above steps, the error is not get solved then copying the error message and then pasting it into a Google search. You found lots of result check one by one & find the solution.

You can easily deal with this error by using all above steps!! The most recommended solution is to restore database from updated backup.
Enhanced by Zemanta

No comments:

Post a Comment