running SQL 2005 under a user account cause servicefail to start

Hi,
I have changed the SQL Server account from local system to .\administrator
and then SQL Server failed to starts
the event log log 5 errors:
event ids: 17120, 17826, 17182, 17182, 26049
SQL Server could not spawn FRunCM thread. Check the SQL Server error log and
the Windows event logs for information about possible related problems.
Could not start the network library because of an internal error in the
network library. To determine the cause, review the errors immediately
preceding this one in the error log.
TDSSNIClient initialization failed with error 0x5, status code 0x1.
TDSSNIClient initialization failed with error 0x5, status code 0x40.
Server local connection provider failed to listen on [
\\.\pipe\SQLLocal\SQL2005 ]. Error: 0x5
my other services works fine under the administrator account (AS2005,
RS2005...)
any idea?
thanks.
Jerome.Hi
This looks like a permission thing, you may want to check the network
configuration. Have you tried removing named pipes?
John
"Jéjé" wrote:
> Hi,
> I have changed the SQL Server account from local system to .\administrator
> and then SQL Server failed to starts
> the event log log 5 errors:
> event ids: 17120, 17826, 17182, 17182, 26049
> SQL Server could not spawn FRunCM thread. Check the SQL Server error log and
> the Windows event logs for information about possible related problems.
> Could not start the network library because of an internal error in the
> network library. To determine the cause, review the errors immediately
> preceding this one in the error log.
> TDSSNIClient initialization failed with error 0x5, status code 0x1.
> TDSSNIClient initialization failed with error 0x5, status code 0x40.
> Server local connection provider failed to listen on [
> \\.\pipe\SQLLocal\SQL2005 ]. Error: 0x5
>
> my other services works fine under the administrator account (AS2005,
> RS2005...)
> any idea?
>
> thanks.
>
> Jerome.
>
>
>|||yes, no changes
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:5A1CA870-06E8-4D43-A7E6-A715FD46281E@.microsoft.com...
> Hi
> This looks like a permission thing, you may want to check the network
> configuration. Have you tried removing named pipes?
> John
> "Jéjé" wrote:
>> Hi,
>> I have changed the SQL Server account from local system to
>> .\administrator
>> and then SQL Server failed to starts
>> the event log log 5 errors:
>> event ids: 17120, 17826, 17182, 17182, 26049
>> SQL Server could not spawn FRunCM thread. Check the SQL Server error log
>> and
>> the Windows event logs for information about possible related problems.
>> Could not start the network library because of an internal error in the
>> network library. To determine the cause, review the errors immediately
>> preceding this one in the error log.
>> TDSSNIClient initialization failed with error 0x5, status code 0x1.
>> TDSSNIClient initialization failed with error 0x5, status code 0x40.
>> Server local connection provider failed to listen on [
>> \\.\pipe\SQLLocal\SQL2005 ]. Error: 0x5
>>
>> my other services works fine under the administrator account (AS2005,
>> RS2005...)
>> any idea?
>>
>> thanks.
>>
>> Jerome.
>>
>>|||Hi
I assume going back to local system still works? Have you tried a domain
account or a different local administrator?
John
"Jéjé" wrote:
> yes, no changes
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:5A1CA870-06E8-4D43-A7E6-A715FD46281E@.microsoft.com...
> > Hi
> >
> > This looks like a permission thing, you may want to check the network
> > configuration. Have you tried removing named pipes?
> >
> > John
> >
> > "Jéjé" wrote:
> >
> >> Hi,
> >>
> >> I have changed the SQL Server account from local system to
> >> .\administrator
> >> and then SQL Server failed to starts
> >> the event log log 5 errors:
> >> event ids: 17120, 17826, 17182, 17182, 26049
> >> SQL Server could not spawn FRunCM thread. Check the SQL Server error log
> >> and
> >> the Windows event logs for information about possible related problems.
> >>
> >> Could not start the network library because of an internal error in the
> >> network library. To determine the cause, review the errors immediately
> >> preceding this one in the error log.
> >>
> >> TDSSNIClient initialization failed with error 0x5, status code 0x1.
> >>
> >> TDSSNIClient initialization failed with error 0x5, status code 0x40.
> >>
> >> Server local connection provider failed to listen on [
> >> \\.\pipe\SQLLocal\SQL2005 ]. Error: 0x5
> >>
> >>
> >>
> >> my other services works fine under the administrator account (AS2005,
> >> RS2005...)
> >>
> >> any idea?
> >>
> >>
> >>
> >> thanks.
> >>
> >>
> >>
> >> Jerome.
> >>
> >>
> >>
> >>
> >>
>
>|||Hi
Another thought! Have you tried changing the pipe name in SQL Server
Configuration Manager?
John
"Jéjé" wrote:
> yes, no changes
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:5A1CA870-06E8-4D43-A7E6-A715FD46281E@.microsoft.com...
> > Hi
> >
> > This looks like a permission thing, you may want to check the network
> > configuration. Have you tried removing named pipes?
> >
> > John
> >
> > "Jéjé" wrote:
> >
> >> Hi,
> >>
> >> I have changed the SQL Server account from local system to
> >> .\administrator
> >> and then SQL Server failed to starts
> >> the event log log 5 errors:
> >> event ids: 17120, 17826, 17182, 17182, 26049
> >> SQL Server could not spawn FRunCM thread. Check the SQL Server error log
> >> and
> >> the Windows event logs for information about possible related problems.
> >>
> >> Could not start the network library because of an internal error in the
> >> network library. To determine the cause, review the errors immediately
> >> preceding this one in the error log.
> >>
> >> TDSSNIClient initialization failed with error 0x5, status code 0x1.
> >>
> >> TDSSNIClient initialization failed with error 0x5, status code 0x40.
> >>
> >> Server local connection provider failed to listen on [
> >> \\.\pipe\SQLLocal\SQL2005 ]. Error: 0x5
> >>
> >>
> >>
> >> my other services works fine under the administrator account (AS2005,
> >> RS2005...)
> >>
> >> any idea?
> >>
> >>
> >>
> >> thanks.
> >>
> >>
> >>
> >> Jerome.
> >>
> >>
> >>
> >>
> >>
>
>|||finally its the solution, the named pipe protocol cause the error.
I disable it, and all works fine...
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:BAC11602-9BC9-490B-868F-C2FDC9E3E1DE@.microsoft.com...
> Hi
> Another thought! Have you tried changing the pipe name in SQL Server
> Configuration Manager?
> John
> "Jéjé" wrote:
>> yes, no changes
>> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
>> news:5A1CA870-06E8-4D43-A7E6-A715FD46281E@.microsoft.com...
>> > Hi
>> >
>> > This looks like a permission thing, you may want to check the network
>> > configuration. Have you tried removing named pipes?
>> >
>> > John
>> >
>> > "Jéjé" wrote:
>> >
>> >> Hi,
>> >>
>> >> I have changed the SQL Server account from local system to
>> >> .\administrator
>> >> and then SQL Server failed to starts
>> >> the event log log 5 errors:
>> >> event ids: 17120, 17826, 17182, 17182, 26049
>> >> SQL Server could not spawn FRunCM thread. Check the SQL Server error
>> >> log
>> >> and
>> >> the Windows event logs for information about possible related
>> >> problems.
>> >>
>> >> Could not start the network library because of an internal error in
>> >> the
>> >> network library. To determine the cause, review the errors immediately
>> >> preceding this one in the error log.
>> >>
>> >> TDSSNIClient initialization failed with error 0x5, status code 0x1.
>> >>
>> >> TDSSNIClient initialization failed with error 0x5, status code 0x40.
>> >>
>> >> Server local connection provider failed to listen on [
>> >> \\.\pipe\SQLLocal\SQL2005 ]. Error: 0x5
>> >>
>> >>
>> >>
>> >> my other services works fine under the administrator account (AS2005,
>> >> RS2005...)
>> >>
>> >> any idea?
>> >>
>> >>
>> >>
>> >> thanks.
>> >>
>> >>
>> >>
>> >> Jerome.
>> >>
>> >>
>> >>
>> >>
>> >>
>>