Re: SQL Server client components - What is this?
- From: v-adamqu@xxxxxxxxxxxxxxxxxxxx (Adams Qu [MSFT])
- Date: Wed, 27 Jun 2007 02:00:02 GMT
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.
--------------------
| X-Tomcat-ID: 118184173
| References: <O2izq92sHHA.1408@xxxxxxxxxxxxxxxxxxxx>
<WflIU78sHHA.2116@xxxxxxxxxxxxxxxxxxxxxx>
<ucmiynBtHHA.4888@xxxxxxxxxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: v-adamqu@xxxxxxxxxxxxxxxxxxxx (Adams Qu [MSFT])
| Organization: Microsoft
| Date: Fri, 22 Jun 2007 09:28:57 GMT
| Subject: Re: SQL Server client components - What is this?
| X-Tomcat-NG: microsoft.public.sqlserver.clients
| Message-ID: <LFFHa$KtHHA.2312@xxxxxxxxxxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.sqlserver.clients
| Lines: 144
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.clients:500
| NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
|
| 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.
|
| --------------------
| | From: "Bob" <86c6c2e6-2146512712@xxxxxxxxxxxxxx>
| | References: <O2izq92sHHA.1408@xxxxxxxxxxxxxxxxxxxx>
| <WflIU78sHHA.2116@xxxxxxxxxxxxxxxxxxxxxx>
| | Subject: Re: SQL Server client components - What is this?
| | Date: Thu, 21 Jun 2007 11:36:32 -0400
| | Lines: 69
| | X-Priority: 3
| | X-MSMail-Priority: Normal
| | X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
| | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
| | X-RFC2646: Format=Flowed; Original
| | Message-ID: <ucmiynBtHHA.4888@xxxxxxxxxxxxxxxxxxxx>
| | Newsgroups: microsoft.public.sqlserver.clients
| | NNTP-Posting-Host: 24-151-85-011.dhcp.nwtn.ct.charter.com 24.151.85.11
| | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
| | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.clients:498
| | X-Tomcat-NG: microsoft.public.sqlserver.clients
| |
| | 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.
| |
| |
| |
|
|
.
- Follow-Ups:
- Re: SQL Server client components - What is this?
- From: Ankur Rawat
- Re: SQL Server client components - What is this?
- References:
- SQL Server client components - What is this?
- From: Bob
- RE: SQL Server client components - What is this?
- From: Adams Qu [MSFT]
- Re: SQL Server client components - What is this?
- From: Bob
- Re: SQL Server client components - What is this?
- From: Adams Qu [MSFT]
- SQL Server client components - What is this?
- Prev by Date: Re: Server IP Address.
- Next by Date: Visual Studio 2005
- Previous by thread: Re: SQL Server client components - What is this?
- Next by thread: Re: SQL Server client components - What is this?
- Index(es):
Relevant Pages
|
Loading
