We have sensitive data that requires the builtin\administrators group be removed so domain admins are unable to see data. When we do this, SQL can continue to run under the local system account, but the SQL Agent cannot.
Does anyone else have a solution that will lockout NT admins (both local and domain) and allow both SQL and the SQL AGENT to run properly?
TIA
Ryan HuntDid you give the new domain account sysadmin rights?
And configure it to start with that account?|||Thanks for the response. I ended up just creating a local admin account for the agent with specific SA rights to the server. Then, had the only department allowed to have access to the data change the password. This seems like the best choice...
Thanks
Showing posts with label domain. Show all posts
Showing posts with label domain. Show all posts
Friday, March 9, 2012
Monday, February 27, 2012
HELP: SQL Server Service can't start up!
I installed SQL Server 2000 on a PC which is on a domain "DOMAIN" and it
uses Windows XP Professional. I used Windows Authentication Mode (instead of
Mixed-Mode). SQL Server 2000 starts up successfully.
Then I installed on a standalone PC which is part of a workgroup "WORKGROUP"
(instead of a domain) and it uses Windows XP Professional. I selected
Windows Authentication Mode. There was a dialog for me to enter my login
details and it already had fields entered, eg:
Username: Owner
Password: <BLANK>
Domain: WORKGROUP
This standalone PC only has one user account "Owner" which is bounded to the
Administrator (the 1st account Windows XP creates for you). The password for
this account is blank. The installation process was successful. But when SQL
Server Service Manager tried to start my SQL Server, it says login failure.
Just wondering, does SQL Server 2000 doesn't like blank passwords and
auto-fails immediately? Or does it have to be on a domain? I cannot use
Mixed-Mode as my development application doesn't work with Mixed-Mode.
Andrew
ERROR.LOG and/or Event Viewer have some info?
Does the MSSQLSERVER Service start automaticaly and under Local System
account?
"Andrew Wan" <andrew_wan1980@.hotmail.com> wrote in message
news:Ox$roroIHHA.816@.TK2MSFTNGP06.phx.gbl...
>I installed SQL Server 2000 on a PC which is on a domain "DOMAIN" and it
>uses Windows XP Professional. I used Windows Authentication Mode (instead
>of Mixed-Mode). SQL Server 2000 starts up successfully.
> Then I installed on a standalone PC which is part of a workgroup
> "WORKGROUP" (instead of a domain) and it uses Windows XP Professional. I
> selected Windows Authentication Mode. There was a dialog for me to enter
> my login details and it already had fields entered, eg:
> Username: Owner
> Password: <BLANK>
> Domain: WORKGROUP
> This standalone PC only has one user account "Owner" which is bounded to
> the Administrator (the 1st account Windows XP creates for you). The
> password for this account is blank. The installation process was
> successful. But when SQL Server Service Manager tried to start my SQL
> Server, it says login failure.
> Just wondering, does SQL Server 2000 doesn't like blank passwords and
> auto-fails immediately? Or does it have to be on a domain? I cannot use
> Mixed-Mode as my development application doesn't work with Mixed-Mode.
>
|||It doesn't have 2 be on a domain.
Test it by giving the local user account a password an restart the sql
service.
Greetz,
SQLWIZ
"Uri Dimant" wrote:
> Andrew
> ERROR.LOG and/or Event Viewer have some info?
>
> Does the MSSQLSERVER Service start automaticaly and under Local System
> account?
> "Andrew Wan" <andrew_wan1980@.hotmail.com> wrote in message
> news:Ox$roroIHHA.816@.TK2MSFTNGP06.phx.gbl...
>
>
|||Hi
I'm only a novice in this field - but I had what appears to be the same
problem a few weeks back, where my SQL server service was logging in with
Windows authentication that wasn't the primary admin account (although it had
admin access). Anyway - due to a network enforced user login password
rotation - I had to change the login password and forgot that the SQL server
service was still associated with the older password. So the SQL server
service wasn't starting...login failure. As I was doing other work at the
time on the server it took a little while (longer than it should have ;-P) to
consider that it was the password change that stuffed the service startup. I
changed the authentication of the service to use the real admin
authentication (which remains outside of the network password rotation
scheme/policy) and the server services have started fine everytime since.
Cheers
Tim
"Hate_orphaned_users" wrote:
[vbcol=seagreen]
> It doesn't have 2 be on a domain.
> Test it by giving the local user account a password an restart the sql
> service.
> Greetz,
> SQLWIZ
> "Uri Dimant" wrote:
uses Windows XP Professional. I used Windows Authentication Mode (instead of
Mixed-Mode). SQL Server 2000 starts up successfully.
Then I installed on a standalone PC which is part of a workgroup "WORKGROUP"
(instead of a domain) and it uses Windows XP Professional. I selected
Windows Authentication Mode. There was a dialog for me to enter my login
details and it already had fields entered, eg:
Username: Owner
Password: <BLANK>
Domain: WORKGROUP
This standalone PC only has one user account "Owner" which is bounded to the
Administrator (the 1st account Windows XP creates for you). The password for
this account is blank. The installation process was successful. But when SQL
Server Service Manager tried to start my SQL Server, it says login failure.
Just wondering, does SQL Server 2000 doesn't like blank passwords and
auto-fails immediately? Or does it have to be on a domain? I cannot use
Mixed-Mode as my development application doesn't work with Mixed-Mode.
Andrew
ERROR.LOG and/or Event Viewer have some info?
Does the MSSQLSERVER Service start automaticaly and under Local System
account?
"Andrew Wan" <andrew_wan1980@.hotmail.com> wrote in message
news:Ox$roroIHHA.816@.TK2MSFTNGP06.phx.gbl...
>I installed SQL Server 2000 on a PC which is on a domain "DOMAIN" and it
>uses Windows XP Professional. I used Windows Authentication Mode (instead
>of Mixed-Mode). SQL Server 2000 starts up successfully.
> Then I installed on a standalone PC which is part of a workgroup
> "WORKGROUP" (instead of a domain) and it uses Windows XP Professional. I
> selected Windows Authentication Mode. There was a dialog for me to enter
> my login details and it already had fields entered, eg:
> Username: Owner
> Password: <BLANK>
> Domain: WORKGROUP
> This standalone PC only has one user account "Owner" which is bounded to
> the Administrator (the 1st account Windows XP creates for you). The
> password for this account is blank. The installation process was
> successful. But when SQL Server Service Manager tried to start my SQL
> Server, it says login failure.
> Just wondering, does SQL Server 2000 doesn't like blank passwords and
> auto-fails immediately? Or does it have to be on a domain? I cannot use
> Mixed-Mode as my development application doesn't work with Mixed-Mode.
>
|||It doesn't have 2 be on a domain.
Test it by giving the local user account a password an restart the sql
service.
Greetz,
SQLWIZ
"Uri Dimant" wrote:
> Andrew
> ERROR.LOG and/or Event Viewer have some info?
>
> Does the MSSQLSERVER Service start automaticaly and under Local System
> account?
> "Andrew Wan" <andrew_wan1980@.hotmail.com> wrote in message
> news:Ox$roroIHHA.816@.TK2MSFTNGP06.phx.gbl...
>
>
|||Hi
I'm only a novice in this field - but I had what appears to be the same
problem a few weeks back, where my SQL server service was logging in with
Windows authentication that wasn't the primary admin account (although it had
admin access). Anyway - due to a network enforced user login password
rotation - I had to change the login password and forgot that the SQL server
service was still associated with the older password. So the SQL server
service wasn't starting...login failure. As I was doing other work at the
time on the server it took a little while (longer than it should have ;-P) to
consider that it was the password change that stuffed the service startup. I
changed the authentication of the service to use the real admin
authentication (which remains outside of the network password rotation
scheme/policy) and the server services have started fine everytime since.
Cheers
Tim
"Hate_orphaned_users" wrote:
[vbcol=seagreen]
> It doesn't have 2 be on a domain.
> Test it by giving the local user account a password an restart the sql
> service.
> Greetz,
> SQLWIZ
> "Uri Dimant" wrote:
HELP: SQL Server Service can't start up!
I installed SQL Server 2000 on a PC which is on a domain "DOMAIN" and it
uses Windows XP Professional. I used Windows Authentication Mode (instead of
Mixed-Mode). SQL Server 2000 starts up successfully.
Then I installed on a standalone PC which is part of a workgroup "WORKGROUP"
(instead of a domain) and it uses Windows XP Professional. I selected
Windows Authentication Mode. There was a dialog for me to enter my login
details and it already had fields entered, eg:
Username: Owner
Password: <BLANK>
Domain: WORKGROUP
This standalone PC only has one user account "Owner" which is bounded to the
Administrator (the 1st account Windows XP creates for you). The password for
this account is blank. The installation process was successful. But when SQL
Server Service Manager tried to start my SQL Server, it says login failure.
Just wondering, does SQL Server 2000 doesn't like blank passwords and
auto-fails immediately? Or does it have to be on a domain? I cannot use
Mixed-Mode as my development application doesn't work with Mixed-Mode.Andrew
ERROR.LOG and/or Event Viewer have some info?
Does the MSSQLSERVER Service start automaticaly and under Local System
account?
"Andrew Wan" <andrew_wan1980@.hotmail.com> wrote in message
news:Ox$roroIHHA.816@.TK2MSFTNGP06.phx.gbl...
>I installed SQL Server 2000 on a PC which is on a domain "DOMAIN" and it
>uses Windows XP Professional. I used Windows Authentication Mode (instead
>of Mixed-Mode). SQL Server 2000 starts up successfully.
> Then I installed on a standalone PC which is part of a workgroup
> "WORKGROUP" (instead of a domain) and it uses Windows XP Professional. I
> selected Windows Authentication Mode. There was a dialog for me to enter
> my login details and it already had fields entered, eg:
> Username: Owner
> Password: <BLANK>
> Domain: WORKGROUP
> This standalone PC only has one user account "Owner" which is bounded to
> the Administrator (the 1st account Windows XP creates for you). The
> password for this account is blank. The installation process was
> successful. But when SQL Server Service Manager tried to start my SQL
> Server, it says login failure.
> Just wondering, does SQL Server 2000 doesn't like blank passwords and
> auto-fails immediately? Or does it have to be on a domain? I cannot use
> Mixed-Mode as my development application doesn't work with Mixed-Mode.
>
uses Windows XP Professional. I used Windows Authentication Mode (instead of
Mixed-Mode). SQL Server 2000 starts up successfully.
Then I installed on a standalone PC which is part of a workgroup "WORKGROUP"
(instead of a domain) and it uses Windows XP Professional. I selected
Windows Authentication Mode. There was a dialog for me to enter my login
details and it already had fields entered, eg:
Username: Owner
Password: <BLANK>
Domain: WORKGROUP
This standalone PC only has one user account "Owner" which is bounded to the
Administrator (the 1st account Windows XP creates for you). The password for
this account is blank. The installation process was successful. But when SQL
Server Service Manager tried to start my SQL Server, it says login failure.
Just wondering, does SQL Server 2000 doesn't like blank passwords and
auto-fails immediately? Or does it have to be on a domain? I cannot use
Mixed-Mode as my development application doesn't work with Mixed-Mode.Andrew
ERROR.LOG and/or Event Viewer have some info?
Does the MSSQLSERVER Service start automaticaly and under Local System
account?
"Andrew Wan" <andrew_wan1980@.hotmail.com> wrote in message
news:Ox$roroIHHA.816@.TK2MSFTNGP06.phx.gbl...
>I installed SQL Server 2000 on a PC which is on a domain "DOMAIN" and it
>uses Windows XP Professional. I used Windows Authentication Mode (instead
>of Mixed-Mode). SQL Server 2000 starts up successfully.
> Then I installed on a standalone PC which is part of a workgroup
> "WORKGROUP" (instead of a domain) and it uses Windows XP Professional. I
> selected Windows Authentication Mode. There was a dialog for me to enter
> my login details and it already had fields entered, eg:
> Username: Owner
> Password: <BLANK>
> Domain: WORKGROUP
> This standalone PC only has one user account "Owner" which is bounded to
> the Administrator (the 1st account Windows XP creates for you). The
> password for this account is blank. The installation process was
> successful. But when SQL Server Service Manager tried to start my SQL
> Server, it says login failure.
> Just wondering, does SQL Server 2000 doesn't like blank passwords and
> auto-fails immediately? Or does it have to be on a domain? I cannot use
> Mixed-Mode as my development application doesn't work with Mixed-Mode.
>
Subscribe to:
Posts (Atom)