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

Do you mean you installed SQL Server + components, then after it was
installed, you ran the native client setup separately? If so, where did you
get the native client setup file, and why do you need to install it
separately? (Client connectivity components should have been installed as a
part of setup.)

If SQL Server is now installed, you can tell if it is 32 bit or not in at
least two ways:

1) if it is the only instance on the server, you will find a sqlservr.exe
somewhere under C:\Program Files (x86)\ for 32-bit, or C:\Program Files\ for
64-bit.

2) when you connect to the instance using Management Studio, you can tell
whether it is 32-bit or 64-bit by using SELECT @@VERSION; for 32-bit, this
will contain X86, otherwise X64.

A




On 6/15/08 7:55 PM, in article
3FC69A6D-3482-42C4-A634-FE4AD538FA41@xxxxxxxxxxxxx, "soccerwiz13"
<soccerwiz13@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

I meant SQL Server 2005.

"soccerwiz13" wrote:

I'm trying to install SQL Server 2008 on Windows Server 2008 x64 bit. I
installed the components, but when I try to install the native client, I get
the error message "This Microsoft SQL Server Native Client package is not
supported on the current processor type." I have a quad-core processor. I
am installing SQL Server 2005 Standard Edition, but I'm not sure if it is 32
bit or 64 bit. It came with the Microsoft Action Subscription pack, and
doesn't list whether it is the 64 or 32 bit version.

Is there a way I can tell whether I have the 32 bit or 64 bit version?
Also, do I need to install WOW64 on SQL server 2008 in order to get it to
work?

.

Relevant Pages

  • MSDE 2000 SP4 install gets to very end then rolls it all back
    ... On most machines my msde install goes fine. ... exuisting SQL server. ... Starting custom action SaveSqlServerServiceStates() ... Action start 14:23:53: RegisterClassInfo. ...
    (microsoft.public.sqlserver.setup)
  • Re: Critical Alert Update - W32.Slammer
    ... The .net SDK 1.0 sp1 comes with a very basic SQL Server engine for testing ... >> Microsoft SQL Desktop ... >>>cumulative SQL security patch, is completely safe from ... >> may install SQL ...
    (microsoft.public.security)
  • RE: SBS 2003 SP1 Upgrade - MSDE 2000 Service Pack 4 did not instal
    ... registry keys of the Microsoft SQL server and mail to me for analyze. ... This newsgroup only focuses on SBS technical issues. ... SBS 2003 SP1 Upgrade - MSDE 2000 Service Pack 4 did not install ...
    (microsoft.public.windows.server.sbs)
  • Re: Installed VS 2005 want to Manage SQL 2005 Server
    ... Microsoft SQL Server Management Studio 9.00.3042.00 ... Microsoft Analysis Services Client Tools 2005.090.3042.00 ... If you later install a more recent service pack, this service pack will be uninstalled automatically. ... How to uninstall SQL Server Management Studio ...
    (microsoft.public.sqlserver.setup)
  • RE: SQL Server Express on SBS2003 standard
    ... This newsgroup only focuses on SBS technical issues. ... you may want to contact Microsoft CSS directly. ... After you applied the SBS 2003 SP1 successfully, you can install the ... SQL Server Express on SBS. ...
    (microsoft.public.windows.server.sbs)
Loading