Cannot Install Workstation Components - Missing Management Studio

Hello,

I have installed SQL Server 2K5 Developer Edition x64, when viewing the option under Start -> All Programs -> Microsoft SQL Server 2005, I do not have the option for Management Studio.

When I attempt to install workstation components I get a message claiming the components I am attempting to install are already installed on the machine and the install will not let me continue.

Any help would be appreciated.

Thanks,

CC

-

Further details, I installed SQL Server after .Net 2K5.

Once I removed all SQL Server components, then re-installed SQL Server 2K5 all appropriate tools were present.

CC

-

|||

While installing , to get tools, you need to select Workstation components from the same window where you sleect Services. If the services are already installed, then go to Control Pannel -- Add/Remove Prorgamm -- Sql server -- Change/Remove -- choose Change and select the Workstation components. It will install only Components. If you are not installed any services, then Install the services and worksation components ...

Madhu

|||

Thanks Madhu,

I resolved the issue prior to you posting by removing SQL Server and SQL Express (installed via .Net 2005 Install). Upon re-installing SQL Server 2005 Dev I was able to access SSMS. I will keep this in mind if I experience this behavior again

Thanks again,

CC

-

Cannot get AD groups to work in SQL 2k5

I'm trying to get Active Directory groups to work in SQL Server 2k5 so my
users can log in with windows authentication. So I've set up the group in
AD, added the domain users to it, added the group to MS SQL security users,
and assigned a default database to the group. For some odd reason my users
are not able to log in though; I can quickly check this by trying to set up
a
ODBC connection System DSN.
The odd part about this is that if I add a domain user to MS SQL, they have
no problem logging into the database. Understandably I want to avoid adding
each and every user to my database, therefore the use of AD groups that is i
f
they would work.I would expect users to be able to connect via group membership. Do you see
the group members listed when you execute xp_logininfo? Does the group show
as the permission path for a specific user?
EXEC xp_logininfo
@.acctname = 'MyDomain\MyGroup',
@.option = 'members'
EXEC xp_logininfo
@.acctname = 'MyDomain\MyGroupMember'
Hope this helps.
Dan Guzman
SQL Server MVP
"Chandler Chao" <ChandlerChao@.discussions.microsoft.com> wrote in message
news:A2720F69-543C-4DF4-8079-56ACA8776D51@.microsoft.com...
> I'm trying to get Active Directory groups to work in SQL Server 2k5 so my
> users can log in with windows authentication. So I've set up the group in
> AD, added the domain users to it, added the group to MS SQL security
> users,
> and assigned a default database to the group. For some odd reason my
> users
> are not able to log in though; I can quickly check this by trying to set
> up a
> ODBC connection System DSN.
> The odd part about this is that if I add a domain user to MS SQL, they
> have
> no problem logging into the database. Understandably I want to avoid
> adding
> each and every user to my database, therefore the use of AD groups that is
> if
> they would work.|||I was just able to get this working with a some help from this NG.
My SQL Server is configured for Mixed authentication.
I set up my AD groups and added users.
I added logins for each AD group in SQL Server.
I added database users for each AD group and assigned permissions to
objects.
Hope this helps..
Michael
"Chandler Chao" <ChandlerChao@.discussions.microsoft.com> wrote in message
news:A2720F69-543C-4DF4-8079-56ACA8776D51@.microsoft.com...
> I'm trying to get Active Directory groups to work in SQL Server 2k5 so my
> users can log in with windows authentication. So I've set up the group in
> AD, added the domain users to it, added the group to MS SQL security
> users,
> and assigned a default database to the group. For some odd reason my
> users
> are not able to log in though; I can quickly check this by trying to set
> up a
> ODBC connection System DSN.
> The odd part about this is that if I add a domain user to MS SQL, they
> have
> no problem logging into the database. Understandably I want to avoid
> adding
> each and every user to my database, therefore the use of AD groups that is
> if
> they would work.