Re: SQL Server client components - What is this?
- From: "Bob" <86c6c2e6-2146512712@xxxxxxxxxxxxxx>
- Date: Thu, 21 Jun 2007 11:36:32 -0400
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: Adams Qu [MSFT]
- 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]
- SQL Server client components - What is this?
- Prev by Date: using Client network utility on sql server 2005
- Next by Date: RE: Non-admin Citrix users cannot connect to SQL Server
- 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