.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Top 5 Contributors of the Month
Easy Web
Imran Ghani
Post New Web Links

SQL Server Native Client install fails during prerequisites

Posted By:      Posted Date: September 15, 2010    Points: 0   Category :SharePoint
 
Hi I'm trying to install sharepoint 2010 on a new windows 2k8r2 which is a member server on our domain. The server is fully updated. The SQL Server native client installation fails. This is the entry in the error log;   2010-09-15 08:57:26 - Beginning download of Microsoft SQL Server 2008 Native Client 2010-09-15 08:57:26 - http://go.microsoft.com/fwlink/?LinkID=160387 2010-09-15 08:57:28 - Size of download of "Microsoft SQL Server 2008 Native Client" in bytes is "8073728" 2010-09-15 08:57:28 - Download of "Microsoft SQL Server 2008 Native Client" completed successfully 2010-09-15 08:57:28 - Installing Microsoft SQL Server 2008 Native Client 2010-09-15 08:57:28 - "C:\Windows\system32\msiexec.exe" /i "C:\Users\myadmin\AppData\Local\Temp\SQLCF11.tmp.msi" /quiet /norestart 2010-09-15 08:57:28 - Install process returned (0X660=1632) 2010-09-15 08:57:28 - [In HRESULT format] (0X80070660=-2147023264)   If I run the SQL native client installer manually I get the following error; The installer has encountered an unexpected error. The error code is 2755. Server returned unexpected error 1632 attempting to install package.   Any ideas why this is happening? I've had a quick google and can't see anything for SQL Native Client for that error code. Thanks   Olly


View Complete Post


More Related Resource Links

SQL-DMO Install on SQL Server 2005 Express Client

  
I am installing a Client side SQL 2005 Express that needs SQL-DMO. The Client computer does not have SQL Server 2005 Express installed. I have installed all the MDAC and .Net 2.0. The command line I'm using to try and install the SQL-DMO and XML modules is: SQLEXPR_ADV ADDLOCAL=Tools_Legacy,SQLXML I get a message something like 'SQL Server 2005 Version does not support this install option.' How do I get SQL-DMO installed on a SQL Server 2005 Express Client computer?

SQL Server 2008 R2 fails after Windows XP Pro SP3 install

  
We recently encountered an issue with SQL Server 2008 R2 failing to run after the upgrade from Windows XP Pro SP2 to SP3. This was tested and reproduced (with varying results) on more than one computer. Steps to reproduce this. On a Windows XP Pro machine with Service Pack 2 installed, install SQL Server 2008 R2. Next upgrade Windows to Service Pack 3. Now upon opening SSMS or trying to start the SQL server service you receive the following message: "This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem". In some instances reinstalling/repairing SQL Server 2008 R2 does fix the issue.  In other cases the installer crashes and you need to use msizap to clean it up before you can reinstall.  In other cases you do not receive any errors at all. After testing in multiple virtual machines it looks like the cleaner the Windows install the more likely you are to run into this issue.  On machines with most or all windows updates (prior to SP3) installed you do not necessarily even get the failure.  On machines with just Windows XP Pro SP2 installed with no additional updates you get the failure every time. Obviously the SQL Server 2008 R2 prerequisites are installed in all cases in order to be able to install SQL server to begin with. Any help with this would be appre

Install SQL Server2005 Error:[Native Client]Encryption not supported on the client

  
Product: Microsoft SQL Server 2005 -- Error 29515. SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Encryption not supported on the client. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.

SQL Server allowing access with NATIVE CLIENT Protocols are disabled.

  
I have disabled all client protocols from SQL Server Configuration Manager -> Sql Native Client configuration -> Client Protocols.Still I am able to access sql server with all client protocols disabled. Why ?Also I stopped the SQL Server Services and restarted it again. Then also the system is allowing me to connect with all the client protocol disabled.

SQL server 2005 SP2 KB921896 fails to install

  
Machine Specs: Windows XP SP3 Over 104GB HDD space available   When running the SP2 update I get "ngen.exe - Application Error" "The application failed to initialize properly (oxc0000005) Click ok.... Hit Ok it pops up a second time, hit Ok a small unexpected error message box pops up with no error code   I have tried a complete reinstall of SQL server 2005, I've tried stopping and restarting SQL services.   Reviewing the HotFix log... It fails when it attempts to pause the ngen queue 09/02/2010 09:00:29.984 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0 09/02/2010 09:00:30.609 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0 09/02/2010 09:00:30.609 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0 09/02/2010 09:00:30.609 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0 09/02/2010 09:00:30.609 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0 09/02/2010 09:00:30.609 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0 09/02/2010 09:00:30.609 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0 09/02/2010 09:00:30.640 Locked file: Checking for locked files 09/02/2010 09:00:30.906 Locked file: C:\WINDOWS\system32\sqlncli.dll (MSSQLSERVER

SQL Server Native Client is substitute of WDAC (MDAC)?

  
Forking this subquestion from my question Does SQL Server clients use (WDAC, MDAC) and when? Having read msdn article  SQL Server 2008 R2 Native Client Programming I could not understand: Is SQL Server Native Client (SSNC) intended to be used as advanced substitute for MDAC (currently renamed as WDAC)? what one could have understood from th? article... Except that this article tells: "The SQL Server Native Client ODBC driver is always used in conjunction with the ODBC Driver Manager supplied with Windows DAC" From one side it sounds that SQL Server Native Client (SSNC) provide the same functionalities that MDAC (WDAC) and more being "a stand-alone data access API,". From the other side, it is written that SSNC is dependent on MDAC(WDAC) components (drivers, dll) and vice versa. So, why 2 parallel, having essentially the same functionalities, data access structure duplicates?

Should I move ODBC Apps from the SQL Server driviver to SQL Server Native Client 10.0

  
I have a suite of applications written for SQL Server 2000 in Access 2000 and Access 2007 and running under Access 2007 (12.0.6423,1000 SP2 MSO 12.0.6425.1000) via ODBC with the SQL Server ODBC driver (2000.85.1132.00) under Windows XP Professional (2002 SP3).  I have maintained all the data modules in Access 2000 format so that they can be accessed by SQL Server 2008 if required and am gradully upgrading the data modules to SQL Server.  The server they are connected to is Microsoft SQL Server Standard Edition (10.0.2531.0 running on a 32-bit Wndows Server 2008 Standard (SP2).  As a security improvement I intend to move a number of the applications to the server itself.  My choice of driver for ODBC is between SQL Server (6.00.6002.18005) and SQL Server Native Client 10.0 (2007.100.2531.00).  I have yet to discover any differences in application behavior or performance between the two interfaces My assumption is that I will have have fewer problems if I configure the ODBC links using the SQL Server driver.  However, I was wondering if there is a reason to gradually move them over to the SQL Server Native Client 10.0 driver. Thanks, Harry

SQL Server 2005 Standard edition install fails; An instance with the same name.../

  

Good Morning

I am trying to install SQL Server 2005 onto Windows Server 2003 Small Business Edition. Previously SQL Server 2000 from the SBE disk was installed, automatic updates are enabled.

I have selected the default instance and everything I try results in the error:

An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.

Log file says;

--------------------------------------------------------------------------------
Machine         : ISAINTERNET
Product         : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install         : Failed
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_ISAINTERNET_SQL.log
Last Action     : DetectInstanceClash
Error String    : An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.
Error Number    : 28086
--------------------------------------------------------------------------------

Ian Smith


SQL Server 2008 R2 Setup fails to install properly

  

Hello, I am not able to install 2008 R2 on my laptop. I have 2005 and 2008 installed previously. It says in one of the attached screenshots that the OLAP service cannot be started. I have attached the errors in screenshots and also my summary log, please advise thank you.

Edit: I am able to manually startup the SQL 2008 R2 service, and can login as "sa" without a password... but strangely I did select mix mode authentication and did supply a password during the installation wizard too..

 

Overall summary:
  Final result:                  SQL Server installation failed. To continue, investigate the

reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server

Setup.
  Exit code (Decimal):           -733426222
  Exit facility code:         &nbs

Silent install of SQL Server 2005 fails when SQL Server 2008 is installed

  

We currently install SQL Server 2005 Express silently during our installation, using the following switches

/qn ADDLOCAL=all REBOOT=ReallySuppress DISABLENETWORKPROTOCOLS=2 SQLAUTOSTART=1 SECURITYMODE=SQL SAPWD=123

We also attach a 2005-created database immediately after using the following command line (^ is a path concat operator in Installshield):

sqlcmd.exe -S .\\SQLEXPRESS -E -i \"" + svConfigPath ^ "SetupUapDB.sql\" -vmdfpath=\"" + svConfigPath ^ "UapCfg.mdf\" -vldfpath=\"" + svConfigPath ^ "UapCfg_log.ldf\" -o \"" + svConfigPath ^ "SqlCreateDB.txt\" -e

Note that we do not specify an instance name.  We ran into a situation where someone had installed SQL Server 2008 on a box using a default instance name and our install then failed.  I am considering 2 possible fixes, and have questions for both.

Fix #1: Specify an instance name.  Ideally this would install SQL Server 2005 Express side by side with SQL Server 2008, create a unique instance name and we'd be good to go right?  If yes, what is the accepted convention for specifying instance names?

Fix #2: Not sure if this is possible.  Can we detect if SQL Server 2008 is on the box, and if yes, apply our 2005 database to it instead?  In this case (tell me

sql server 2005 install on SBS2003 fails due to registry key permissions

  
I am posting this to hopefully help someone else that encounters the same issue in the future...


Server:  SBS 2003 Premium, with exchange and with all service packs/patches applied.
Server-name: NEWSERVER
Server migrated from: OLDSERVER
Important notes:
This server was migrated from another SBS 2003 on different HW following the instructions provided by microsoft.
The oldserver had exchange and sql 2005 installed on it.
The new server has Office Accounting 2005 installed, but I don't think that matters...

I am trying to install SQL 2005 from the SBS2003-R2 DVD onto the new server, and get the following error:

Error:
---
TITLE: Microsoft SQL Server 2005 Setup
------------------------------

SQL Server Setup failed to modify security permissions on registry key SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.2\MSSQLServer\SuperSocketNetLib for user Administrator. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that the registry key  exists on the destination drive.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=setup.rll&

bcp queryout using $PARTITION fails with Native Client error: Invalid Object $PARTITION

  

Using bcp queryout, in-line queries of the following form fail with the invalid object error on the $PARTITION keyword:

bcp "SELECT S.* FROM Support_Prod.ADSK.Session S INNER JOIN ##Session #S ON (S.SessionId = #S.SessionId AND S.LastInquiryId = #S.LastInquiryId AND $PARTITION.AdskInqPF(S.LastInquiryId) = $PARTITION.AdskInqPF(#S.LastInquiryId))" queryout I:\Data2\AdskBCPout\ADSK.Session.dat -fI:\Data2\AdskBCPout\ADSK.Session.format.xml -q -t\t -r\n -SINTDEVSQL1\DEV1 -T

Here, AdskInqPF is a well-formed partition function used to partition Support_Prod.ADSK.Session.  ##Session is a table of semi-joins derived from the former, but is not partitioned.  LastInquiryID is the partitioning key on the Session entity.

The resulting error is:

SQLState = S0002, NativeError = 208
Error = [Microsoft][SQL Server Native Client 10.0][SQL Server]Invalid object name '$partition.AdskInqPF'.
SQLState = S0002, NativeError = 208
Error = [Microsoft][SQL Server Native Client 10.0][SQL Server]Invalid object name '$partition.AdskInqPF'.
SQLState = 37000, NativeError = 8180
Error = [Microsoft][SQL Server Native Client 10.0][SQL Server]Statement(s) could not be prepared.

The platform is SQL Server 2008 SP1 and the bcp is

BCP - Bulk Copy Program for Microsoft SQL Server.
Copyright (C) Microsoft Corporation. A

Install fails wth SQL Server 2008 Enterprise on Windows Server 2008 R2

  

I have a new server onto which I have installed Windows Server 2008 R2 Enterprise. I have not been successful at installing SQL Server 2008 Enterprise on it. After many attempts, I continue to get the following error message:

        Microsoft .NET Framework 3.5 installation has failed.
        SQL Server 2008 setup requires .NET Framework 3.5 to be installed.


Some notes:

  • I got my copies of Windows Server 2008 R2 and SQL Server 2008 Enterprise through my MSDN subscription.
  • Upon first installing WinServer2008 R2, I notice that the .NET Framework 3.5.1 is not installed and is not available as a feature to add through the Programs and Features control panel.
  • Upon first installing WinServer2008 R2, Server Manag

SQL Server 2005 Management Studio error and cannot re-install client tools too system.serviceModel e

  

Hi,

got some regular OS patches today and voila:

sql management studio error: appidpackage failed to open connection dialog

Have tried to re-install client tools:

F:\>start /wait \setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

Success
The following error occurred:
Configuration system failed to initialize

Error result: -2068774911
Result facility code: 1201
Result error code: 1

Please review the summary.txt log for further details
The following error occurred:
Configuration system failed to initialize

Error result: -2068774911
Result facility code: 1201
Result error code: 1

Please review the summary.txt log for further details

Unhandled Exception: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastru
ctureException: Configuration system failed to initialize ---> System.Configurat
ion.ConfigurationErrorsException: Configuration system failed to initialize --->
 System.Configuration.ConfigurationErrorsException: Unrecognized configuration s
ection system.serviceModel. (C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Confi
g\machine.config line 146)
   at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignor
eLocal)
   at System.Configuration.BaseC

SQL Server 2005 Management Studio error and cannot re-install client tools too system.serviceModel e

  

Hi,

got some regular OS patches today and voila:

sql management studio error: appidpackage failed to open connection dialog

Have tried to re-install client tools:

F:\>start /wait \setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

Success
The following error occurred:
Configuration system failed to initialize

Error result: -2068774911
Result facility code: 1201
Result error code: 1

Please review the summary.txt log for further details
The following error occurred:
Configuration system failed to initialize

Error result: -2068774911
Result facility code: 1201
Result error code: 1

Please review the summary.txt log for further details

Unhandled Exception: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastru
ctureException: Configuration system failed to initialize ---> System.Configurat
ion.ConfigurationErrorsException: Configuration system failed to initialize --->
 System.Configuration.ConfigurationErrorsException: Unrecognized configuration s
ection system.serviceModel. (C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Confi
g\machine.config line 146)
   at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignor
eLocal)
   at System.Configuration.BaseC

SQL Server Express R2 Database Engine fails to install on XP Home (SP3)

  

I have had multiple failed attempts at installing SQL Server 2008 R2 Express on an elderly but reliable machine running XP Home with SP3. 
The support files and management tools loaded OK when I de-selected the database engine.  I was installing as a user with administrator rights. 
I wanted to start the DB as a service following boot without a user logged on.

The failure appeared as a message a 'Library not registered' at stage Slp_Config_SQLEngine_ADHlpr_Cpu32.  I cancelled at this point (although in other attempts I let it run on with similar, unsuccessful results).

Other posts covering failed installation do not appear to cover the same problem.  If they do, I am afraid it is my limited understanding!

The summary log file is below and what I think are the relevant lines from the detail are given after. 

Can anyone help identify the cause and suggest what I need to do to rectify it?

Many thanks.

******************************************************************
Summary Log File
******************************************************************
Overall summary:
  Final result:                  User cancelled
  Exit code (Decimal):    

[Microsoft][SQL Server Native Client 10.0]Shared Memory Provider: Timeout error [258]

  

Hello All,

I am using MS SQL SERVER 2008. Im making an application which queries trillion of records. Im using PHP as scripting language. For those functions , which query database and 200 (approximately) rows of DB are returned, everything works fine. But if I query database and a large recordset should be returned, the following error is thrown:

Array ( [0] => Array ( [0] => 08S01 [SQLSTATE] => 08S01 [1] => 258

=> 258 [2] => [Microsoft][SQL Server Native Client 10.0]Shared Memory Provider: Timeout error [258]. [message] => [Microsoft][SQL Server Native Client 10.0]Shared Memory Provider: Timeout error [258]. ) [1] => Array ( [0] => 08S01 [SQLSTATE] => 08S01 [1] => 258
=> 258 [2] => [Microsoft][SQL Server Native Client 10.0]Communication link failure [message] => [Microsoft][SQL Server Native Client 10.0]Communication link failure ) [2] => Array ( [0] => 08S01 [SQLSTATE] => 08S01 [1] => -2147467259
=> -2147467259 [2] => [Microsoft][SQL Server Native Client 10.0]Communication link failure [message] => [Microsoft][SQL Server Native Client 10.0]Communication link failure ) )

If I see the error log it shows:

2010-10-17 12:32:38.88 Logon       Error: 18456, Severity: 14, State: 8.

2010-10-17 12

Categories: 
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend