Hello,

The named SQL EXPRESS instance that I have installed will not start. I
opened up the list of services (in the Computer Management Console) and I
see that the SQL SERVER item shows that it should start Automatically, but
it doesn't start. When I right-click it and then click Start, it sits there
for a while before saying:

"Windows could not start the SQL Server ([myinstancename]) on Local
Computer. For
more information, review the System Event Log. If this is a non-Microsoft
service, contact the service vendor, and refer to service-specific error
code
10022."

I've completely uninstalled it, then reinstalled it, and finally rebooted. I
get the exact same behavior...same error.

I cannot find this error code on the web, anywhere...what's the problem?

Thanks!

-Adam-

By Computer Management Console I assume you mean SQL Server Configuration
Manager. Sometimes Configuration Manager isn't able to pass the error on to
you. Try bypassing Configuration Manager by trying to start SQL Server from
the Windows Services applet. (services.msc) I often find it will give me the
error.
If still no error message, then bypass the whole Windows services
infrastructure, and try starting SQL Server from the command line. Open a
command prompt, go to C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Binn and then type sqlservr.exe. Somewhere along here
you will see the error and know what to fix.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Adam Porter" <REMOVE.adamp (AT) formulaboats (DOT) com> wrote

By Computer Management Console I assume you mean SQL Server Configuration
Manager. Sometimes Configuration Manager isn't able to pass the error on to
you. Try bypassing Configuration Manager by trying to start SQL Server from
the Windows Services applet. (services.msc) I often find it will give me the
error.
If still no error message, then bypass the whole Windows services
infrastructure, and try starting SQL Server from the command line. Open a
command prompt, go to C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Binn and then type sqlservr.exe. Somewhere along here
you will see the error and know what to fix.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Adam Porter" <REMOVE.adamp (AT) formulaboats (DOT) com> wrote

By Computer Management Console I assume you mean SQL Server Configuration
Manager. Sometimes Configuration Manager isn't able to pass the error on to
you. Try bypassing Configuration Manager by trying to start SQL Server from
the Windows Services applet. (services.msc) I often find it will give me the
error.
If still no error message, then bypass the whole Windows services
infrastructure, and try starting SQL Server from the command line. Open a
command prompt, go to C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Binn and then type sqlservr.exe. Somewhere along here
you will see the error and know what to fix.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Adam Porter" <REMOVE.adamp (AT) formulaboats (DOT) com> wrote

By Computer Management Console I assume you mean SQL Server Configuration
Manager. Sometimes Configuration Manager isn't able to pass the error on to
you. Try bypassing Configuration Manager by trying to start SQL Server from
the Windows Services applet. (services.msc) I often find it will give me the
error.
If still no error message, then bypass the whole Windows services
infrastructure, and try starting SQL Server from the command line. Open a
command prompt, go to C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Binn and then type sqlservr.exe. Somewhere along here
you will see the error and know what to fix.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Adam Porter" <REMOVE.adamp (AT) formulaboats (DOT) com> wrote

By Computer Management Console I assume you mean SQL Server Configuration
Manager. Sometimes Configuration Manager isn't able to pass the error on to
you. Try bypassing Configuration Manager by trying to start SQL Server from
the Windows Services applet. (services.msc) I often find it will give me the
error.
If still no error message, then bypass the whole Windows services
infrastructure, and try starting SQL Server from the command line. Open a
command prompt, go to C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Binn and then type sqlservr.exe. Somewhere along here
you will see the error and know what to fix.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Adam Porter" <REMOVE.adamp (AT) formulaboats (DOT) com> wrote

By Computer Management Console I assume you mean SQL Server Configuration
Manager. Sometimes Configuration Manager isn't able to pass the error on to
you. Try bypassing Configuration Manager by trying to start SQL Server from
the Windows Services applet. (services.msc) I often find it will give me the
error.
If still no error message, then bypass the whole Windows services
infrastructure, and try starting SQL Server from the command line. Open a
command prompt, go to C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Binn and then type sqlservr.exe. Somewhere along here
you will see the error and know what to fix.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Adam Porter" <REMOVE.adamp (AT) formulaboats (DOT) com> wrote

By Computer Management Console I assume you mean SQL Server Configuration
Manager. Sometimes Configuration Manager isn't able to pass the error on to
you. Try bypassing Configuration Manager by trying to start SQL Server from
the Windows Services applet. (services.msc) I often find it will give me the
error.
If still no error message, then bypass the whole Windows services
infrastructure, and try starting SQL Server from the command line. Open a
command prompt, go to C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Binn and then type sqlservr.exe. Somewhere along here
you will see the error and know what to fix.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Adam Porter" <REMOVE.adamp (AT) formulaboats (DOT) com> wrote

By Computer Management Console I assume you mean SQL Server Configuration
Manager. Sometimes Configuration Manager isn't able to pass the error on to
you. Try bypassing Configuration Manager by trying to start SQL Server from
the Windows Services applet. (services.msc) I often find it will give me the
error.
If still no error message, then bypass the whole Windows services
infrastructure, and try starting SQL Server from the command line. Open a
command prompt, go to C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Binn and then type sqlservr.exe. Somewhere along here
you will see the error and know what to fix.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Adam Porter" <REMOVE.adamp (AT) formulaboats (DOT) com> wrote

By Computer Management Console I assume you mean SQL Server Configuration
Manager. Sometimes Configuration Manager isn't able to pass the error on to
you. Try bypassing Configuration Manager by trying to start SQL Server from
the Windows Services applet. (services.msc) I often find it will give me the
error.
If still no error message, then bypass the whole Windows services
infrastructure, and try starting SQL Server from the command line. Open a
command prompt, go to C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Binn and then type sqlservr.exe. Somewhere along here
you will see the error and know what to fix.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Adam Porter" <REMOVE.adamp (AT) formulaboats (DOT) com> wrote