Hi,

I need to install SQL Server client components (as Symantec calls it) so as
to access my SQL Server 2005. Where do I find the SQL Server client
components installation code? Is this on the SQL Server 2005? Maybe the
install menu item " Run the SQL Native Client Installation Wizard"?

If it is that, my CD is 64-bit and I need one for 32-bit. Do I have to
download an entire 32-bit SQL Server 2005 installation CD to install it?

Thanks!

---
Bob

Dear Bob,

Thank you for posting here.

The SQL Server Client tools are also stored in the SQL Server installation
media. If you need to install 32 bit SQL Server client component, we need
to use the 32 bit 32-bit to install 32 bit 32 bit client tools, or we can
download and install the SQL Server 2005 Express Edition Management Studio
(free), which can be downloaded from the following download link:

Microsoft SQL Server Management Studio Express
http://www.microsoft.com/downloads/d...5AE-4BD1-4E3D-
94B8-5A0F62BF7796&displaylang=en

For your reference, to install SQL Server 2005 Client Tools only from the
SQL Server installation CD, we can use the following command:

1. Insert the SQL Server 2005 installation media into the disk drive.
2. Run the following command from the command prompt:

Start /wait <CD or DVD Drive>\servers\setup.exe /qb
INSTANCENAME=<InstanceName>
ADDLOCAL=SQL_DTS,Client_Components,Connectivity,SQ L_Tools90,SQL_WarehouseDev
Workbench,SQLXML,Tools_Legacy,SQL_Documentation,SQ L_BooksOnline
PIDKEY=<pidkey value with no "-"> SAPWD=<StrongPassword>

NOTE: Installations from CD media are split into \servers and \tools
folders. Installations from CD must specify the \servers or \tools folder
in the path to Setup.exe. Installations from DVD media are on a single
disk. Installations from DVD should not include the \servers or \tools
folder in the path to Setup.exe.

For more information on how to install SQL Server 2005 from the Command
Prompt, please refer to the following website:

How to: Install SQL Server 2005 from the Command Prompt
http://technet.microsoft.com/en-us/l...9(SQL.90).aspx

Have a nice day!

Best regards,

Adams Qu, MCSE 2000, MCDBA
Microsoft Online Support

Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------

Hi Adams,

Thanks for reply!

I tried the second option first and that didnt' solve my problem. I tried
the first option second, and still no go.

btw the first option only takes up 60MB of hard drive space whereas the
second option takes up 650MB.

I don't think my problem is a Microsoft one as either option finds my remote
SQL Server just fine.

It is probably beyond the scope of this forum, but here's the problem I am
having.

I installed Symantec AntiVirus Corporate Edition on Windows Server 2003. I'm
now trying to install the Reporting Server component and have it use my SQL
Server 2005 named instance.
Per the Symantec instructions, when I get to the installation dialog where
it asks about the database, I select "Install Reporting Server using a
database server on this machine".

Note that this is the same response for an existing SQL server or to have
Symantec install MSDE instead.

The problem is the install doesn't seem to find my SQL Server 2005 named
instance and trys to install MSDE.

Another Symantec option is to "Install Reporting Server using a database
server on another machine" (which is why I started this post because I
needed "SQL Server client components" to do so).

This second option with Symantec at least trys to find the SQL Sever via a
server alias that I created using the
Client Network Utility - cliconfg.exe, but it still fails to find the SQL
Server.



I have no problem with Microsoft SQL Server Management Studio Express
finding the server alias however.



Symantec also requires that SQL Server 2005 be SP1 or greater (I'm at SP2).
Also, authentication must be configured for Mixed Mode (which it wasn't), so
I changed it from Windows Authentication mode to SQL Server and Windows
Authentication mode (and rebooted even though it was probably not
necessary). It also uses the SQL "sa" account, so I rekeyed that password
as I don't know how to tell what it was. It doesn't want the default
instance; but I don't think I have one as when I installed SQL Server, I
keyed in instance "ComputerCreate" instead. It also requires SQL Server
Browser service to be running and I can see it is.



So, I'm at a loss (other than letting it install MSDE, which I hope will
work!).



Thanks again!



Bob.

Dear Bob,

Thank you for your reply.

I understand that we are able to use the Microsoft SQL Server Management
Studio to connect to the SQL Sever named instance successfully but the
Symantec program still cannot find the SQL Sever named instance.

According to the information given, Symantec AntiVirus may use different
protocol or driver to connect to the SQL Server instance. At this stage, I
suggest we first contact the Symantec Support Professional to confirm the
following points:

1. Which driver (E.X: SQL Native Client, OLE DB, etc) is used by Symantec
AntiVirus to connect to SQL Server.
2. Please also confirm which protocol is used by the Symantec AntiVirus
such as TCP, Named Pipe, etc.

At the same time, it is also recommended that we use the SQLcmd utility to
test the current connection issue. For your information, SQLcmd will use
SQL native client as its connection driver. If we failed to use the SQLcmd
to connect to the remote server, the problem can be caused by the protocol
configuration of the SQL Native client. Please refer to the following steps
to test the issue.

1. Click Start, click Run, type cmd, and then click OK
2. At the command prompt, type the following command, and then press ENTER.


sqlcmd -S tcp:<computer name>\<instance name>,<port number> -U<Username>
-P<password>

3. Please check if we can successfully connect to the instance of SQL
Server 2005 by using sqlcmd

For more information regarding the sqlcmd, please visit the following link
in the SQL Server 2005 BookOnline

How to: Connect to the Database Engine Using sqlcmd.exe
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/74b0fb71-7f8e-4171-9431-d075
28532524.htm

If any error is received, please confirm with me the extract error message.
Thank you for your cooperation.

Have a nice day!

Best regards,

Adams Qu, MCSE, MCDBA, MCTS
Microsoft Online Support

Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------

Dear Bob,

I would like to check how things are going. Did you have the chance to try
the troubleshooting steps? If you have any other questions, please do not
hesitate to let me know. I look forward to your further updates.

Have a nice day!

Best regards,

Adams Qu, MCSE, MCDBA, MCTS
Microsoft Online Support

Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.



--------------------
<ucmiynBtHHA.4888 (AT) TK2MSFTNGP02 (DOT) phx.gbl>

Hi Adams,
I am dealing with a related issue -

1. I have SQL server 2005 Standard Edition.
2. I am trying to install the SQL server 2005 Client from this CD on my
laptop.
3. The laptop has "Windows Vista Home Premium" OS on it, and has the AMD
Turion 64 Mobile Technology MK-36 processor.

The installation wizard runs fine and goes through the whole installation
process. Once the installation is done, I dont see the SQL client in my
Program Files.

Can you please help me with this issue?

thanks much.
Ankur.

"Adams Qu [MSFT]" <v-adamqu (AT) online (DOT) microsoft.com> wrote

Hi Ankur,

If all you want is the client, why not just download the free Microsoft SQL
Server Management Studio Express?

It only takes 60MB compared to the 650MB that you may have ended up with.

I presume you have a remote SQL server that you wish to connect to?

Bob.

Yes, I just want to connect to a remote SQL server.

Unfortunately, the website for studio express does not mention Vista as a
supported OS
(http://www.microsoft.com/downloads/d...isplaylang=en).

Is there a workaround to make it work on Vista?

thanks
ankur.


"Bob" <86c6c2e6-2146512712 (AT) news (DOT) postalias> wrote

Here you go...

http://www.microsoft.com/downloads/d...displaylang=en


Bob.

Hello,

Thank you for your reply and sharing your information.

Yes. We can attempt to install Microsoft SQL Server 2005 Express Edition on
the Windows Vista machine free of charge.

For 64-bit platforms (x64 and EMT64 only), we need to first download and
install the 64-bit version of Microsoft .NET Framework 2.0 before
installing Microsoft SQL Server 2005 Express Edition

Microsoft .NET Framework Version 2.0 Redistributable Package (x64)
http://www.microsoft.com/downloads/d...000-acf8-4fa1-
affb-40e78d788b00&DisplayLang=en

Bob, I am also glad to hear that we are able to reinstall the SQL Server
default instance successfully (in another post named "How to: Uninstalling
an existing instance of SQL Sever 2005"). I also understand that you will
now attempt to install the Symantec Anti-Virus Reporting Server which
always failed to install previously.

If the installation procedure still fails, please first contact the
Symantec support professional and help me confirm the following information:

1. Which driver (E.X: SQL Native Client, OLE DB, etc) is used by Symantec
Anti-Virus to connect to SQL Server.
2. Please also confirm which protocol is used by the Symantec Anti-Virus
such as TCP, Named Pipe, etc.

Please also use the SQLcmd to test the protocol of the SQL Native client.

1. Click Start, click Run, type cmd, and then click OK
2. At the command prompt, type the following command, and then press ENTER.

sqlcmd -S tcp:<computer name>\<instance name>,<port number> -U<Username>
-P<password>

3. Please check if we can successfully connect to the instance of SQL
Server 2005 by using sqlcmd

I will continue to monitor this post. Please don't hesitate to let me know
if there is any update regarding this issue.

Have a nice day!

Best regards,

Adams Qu, MCSE, MCDBA, MCTS
Microsoft Online Support

Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
<ucmiynBtHHA.4888 (AT) TK2MSFTNGP02 (DOT) phx.gbl>
<LFFHa$KtHHA.2312 (AT) TK2MSFTNGHUB02 (DOT) phx.gbl>
<FNuCk7FuHHA.2220 (AT) TK2MSFTNGHUB02 (DOT) phx.gbl>
<92C16D6F-EA31-41F3-8BC7-F2984E7BF382 (AT) microsoft (DOT) com>
<eVcBG4OuHHA.3364 (AT) TK2MSFTNGP02 (DOT) phx.gbl>
<A03C356B-6354-4E87-8481-6A517A5DB3E3 (AT) microsoft (DOT) com>
B542-4A4B869C2FF1&displaylang=en