Showing posts with label administrator. Show all posts
Showing posts with label administrator. Show all posts

Wednesday, March 28, 2012

Running/Starting MSDE Server as Power User automatically

I am able to install MSDE as an Administrator. The server will also
start (with the little icon in system tray showing the white circle
with a green play graphic).
I am able to use the server perfectly fine as a user under the
Administration group.
However, when I created a local account under POWER USER group, the
server does not start or connect to any servers.
I have to manually type in my computer's name at which point it will
start.
I have also had trouble installing the server and having it
successfully run under a POWER USER group.
Anyone have any soultions?
Gautam Lad
hi,
"Gautam Lad" <gautam@.hbfenn.com> ha scritto nel messaggio
news:3a492d07.0501031241.1e0cf675@.posting.google.c om
> I am able to install MSDE as an Administrator. The server will also
> start (with the little icon in system tray showing the white circle
> with a green play graphic).
> I am able to use the server perfectly fine as a user under the
> Administration group.
> However, when I created a local account under POWER USER group, the
> server does not start or connect to any servers.
> I have to manually type in my computer's name at which point it will
> start.
> I have also had trouble installing the server and having it
> successfully run under a POWER USER group.
> Anyone have any soultions?
as SQL Server requires a lot of admin privileges at startup, in order to
register services, install MDAC (if needed) and loo of COM server, the best
way to go is installing it as mmber of admins WinNT role...
as regard running SQL Server, it's services (MSSQLSERVER and SQLSERVERAGENT
for a default instance) usually run under LocalSystem WinNT special account,
but you can run them under any admin member WinNT account, as special
privileges for file system and registry access...
in usual solutions, MSDE is installed from admins and run under their
account (LocalSystem and/or standard WinNT local admin accounts), but WinNT
logged users are (as best practice) traditional non admin users, that's to
say power users or limited users, and you should not see problems this
way... you have to check the account the services are running under...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
sql

Tuesday, February 21, 2012

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.
>> >>
>> >>
>> >>
>> >>
>> >>
>>