Re: SQL Server Native Client is not supported on the current proce

I ran the SQL Configuration manager and my machine had no instances running.
I also looked in servers and no services for SQL existed.

I then ran the install for SQL Server 2008 CTP that came in November 2007.
It installed an instance of SQL Server correctly. However, it failed to
install the Client Tools and SQl Server Books online. The error message I am
getting now it:

Setup has detected SQL Server 2005 Client Components on the computer where
you are installing SQL Server 2008. SQL Server 2008 installation is not
supported side-by-side with SQL Server 2005 Client Components. You must
either install SQL Server 2008 Client Components on a different computer or
uninstall SQL Server 2005 Client Components before installing SQL Server 2008
Client Components.

However, I have uninstalled all SQL 2005 components. Do I need to remove
certain files? Any ideas?

"Aaron Bertrand [SQL Server MVP]" wrote:


I did install SQL Server + components, but no instance of SQL 2005 was
installed.

Did you review the error logs? How exactly are you verifying that "no
instance of SQL 2005 was installed"?

I looked in my program files and I have files in both Program
Files (x86) and Program Files.

Yes, both of these folders should be present (in most cases) on x64. The
important part is, where did you find the specific file, sqlservr.exe, if at
all?

I had two warning during install. One was
that IIS was not running (although IIS 7 was running) and the other was an
issue with reporting services. Would these warnings cause the instance of
SQL Server to not install?

No, they would simply affect reporting services. Could you try a much more
simple install, e.g. just the database engine and client connectivity
components. That is, once you have explained how you have verified that no
instance is already installed, and we have helped you figure out whether
that is accurate or not.


.

Relevant Pages

  • Re: Trying to Move Group - SQL Instance Wont Start
    ... You can do a maintenance install and add the new nodes. ... "maintaining a failover cluster" for recovery from failure scenario 1. ... Senior SQL Infrastructure Consultant ... Microsoft SQL Server MVP ...
    (microsoft.public.sqlserver.clustering)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... While attempting to install SP4, it comes up immediately after I ... to be on one of the nodes that can bring SQL Server online and apply SP3a, ...
    (microsoft.public.sqlserver.clustering)
  • Re: Any help here???
    ... Well, for starters, I believe MDAC is unnecessary for .NET applications - as ... ADO.NET has its own SQL Server provider for data access. ... > trust me - all that's been done here was to install SP2 or upgrade of XP ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Rebuild the node in the failover cluster. ... Scenario 1" in SQL Server 2000 Books Online. ... This setup process updates to SP4 only the binaries on the new ...
    (microsoft.public.sqlserver.clustering)
Loading