Re: Setup stalling

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Stan White [MS] (stanwh_at_microsoft.com)
Date: 06/08/04 

Date: Tue, 8 Jun 2004 13:06:49 -0700

>From your description, it does not look like the service account really is a
member of the local administrators group on the SQL Server.
Try connecting to the admin$ share on the SQL Server while logged in with
the service account.
If the service account is a local admin on the SQL Server then it is already
a SQL admin by default.

Try using a different account to install with besides the service account -
a user account with admin rights to the site server and SQL server.
Then grant SMS rights to a user account and add to the SMS admins local
group.
If you don't use another account for setup then you'll have no rights in the
UI as a regular user and will need to log on with the service account to
grant them.
It's not really recommended to use the service account for administration. 

-- 
-- 
Stan [MSFT]
--
--
This posting is provided "AS IS" with no warranties, and confers no rights.
--
--
"virusflashfx" <anonymous@discussions.microsoft.com> wrote in message 
news:08C36FE3-FF2F-4D12-ACBE-40D24938124C@microsoft.com...
>I have SMS 2003 running on W2K3 server (Box A) and SQL 2000 server (Box B) 
>in an AD environment in Standard Security mode. We are not extending the 
>schema for AD. I am currently logged into Box A as the account I am going 
>to use as the SMS Service Account (it also has system rights on Box A). 
>This account has local admin rights on the SQL Server. After working out 
>some problems with the SQL account rights (I didnt give this service 
>account rights to the database, duh!), I was able to get past the "system 
>evaluation stage", but now I simply get a SMS setup window that sits with 
>only a Setup Progress window saying "Waiting for the Windows user account 
>database to be synchronized" and it sits for over 2 hours doing nothing. 
>FYI  I am using Windows authentication for the SQL connection and the SMS 
>Provider is the SMS Site Server. The account I am using as the SMS Service 
>account as the
>
> Can someone shed some light as to what I might not have configured 
> properly? I am going to reinstall SQL again, but any other suggestions on 
> improper settings?

Relevant Pages

  • Re: 2005 Enterprise sp 2 install fails - 11009
    ... Q...Was your SQL Server service account a domain administrator account? ...
    (microsoft.public.sqlserver.setup)
  • Re: Help with Software/Hardware decision....
    ... SQL server on DC question has two aspects such as performance and security. ... the computer running SQL Server as a domain controller will work (and it ... MSSQLServer service must run within the security context of an NT account. ... This configuration lets users assign permissions and rights to a service by ...
    (microsoft.public.windows.server.networking)
  • Re: Scheduling a simple local package wont stick
    ... the FTP is just the first part of this package I wish to accomplish. ... group does not need to be, and on my servers is not, a SQL Server sysadmin. ... it is not obvious to me which account you are running under ... The rights you need to check are not SQL Server rights, ...
    (microsoft.public.sqlserver.dts)
  • Re: SQL windows account
    ... > Can the account to run SQL server belong to USER group or ... >>SQL Service account absoloutely does NOT have ... >>Jasper Smith (SQL Server MVP) ... >>> I happened to be a box and DB admin and i have a local ...
    (microsoft.public.sqlserver.security)
  • Re: ASP.NET - SQL Server does not exist or access denied
    ... Make sure that the account is set up with "Log on as a Service" and "Log on as ... Make sure you've looked at your machine.config file as well (Windows ... ensure it would have no rights as a user), then set it up with the "log on" ... > a "SQL Server does not exist or access denied" error. ...
    (microsoft.public.sqlserver.security)