Quantcast
Channel: SQL Server Setup & Upgrade Forum
Viewing all 7701 articles
Browse latest View live

SQL Server Native Client won't install - want to purge the machine of possible conflicts

$
0
0

SQL Server Express and native client just do not work together on my machine.

win7 64bit

SQL Server Express 2012  SP1 (64 bit) installs--- but it does not seem to actually install Native Client.
SQLEXPRWT_x64_ENU.exe

SQL Native client 2012 (64 bit) says that it installs, but it does not add the DLL's or create the proper directories on the machine
 ENU\x64\sqlncli.msi 

I feel like i have wasted a week on this and have had enough.

Everything is uninstalled, where now we wish to clean the machine totally of any and all old SQL related  - code , directories, registry - whatever to have a fresh install,

~~~~~

Is there a list of items that would help to ensure a clean non conflict install? In the image below I see a conflict, however As far as the uninstall directory is concerned no other SQL server exists. -- How do you approach  totally removing all related items that are  lingering somewhere?






MS Sql2012 along side MS Sql 2008 installation error - 2349

$
0
0

Hi Guys,

hoping someone can assist me here. Trying to install SQL 2012 sp1 on a server which currently has MS Sql2008r2 installed. I've read this can be done, however keep getting the same error: 2349 happens during Install_SQlsupport_katmairtm_cpu64.action:installfiles.copyingnew files. Below is my error log, thanks in advanced!

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2068051667
  Start time:                    2013-01-25 11:19:52
  End time:                      2013-01-25 11:48:10
  Requested action:              Install

Setup completed with required actions for features.
Troubleshooting information for those features:
  Next step for Adv_SSMS:        Use the following information to resolve the error, and then try the setup process again.
  Next step for Conn:            Use the following information to resolve the error, and then try the setup process again.
  Next step for BC:              Use the following information to resolve the error, and then try the setup process again.
  Next step for SSMS:            Use the following information to resolve the error, and then try the setup process again.
  Next step for BIDS:            Use the following information to resolve the error, and then try the setup process again.
  Next step for SQLEngine:       Use the following information to resolve the error, and then try the setup process again.
  Next step for Replication:     Use the following information to resolve the error, and then try the setup process again.
  Next step for IS:              Use the following information to resolve the error, and then try the setup process again.
  Next step for AS:              Use the following information to resolve the error, and then try the setup process again.


Machine Properties:
  Machine name:                  TABAPPSERVER2
  Machine processor count:       8
  OS version:                    Windows Server 2008
  OS service pack:               Service Pack 2
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x64
  Process architecture:          64 Bit
  OS clustered:                  No

Product features discovered:
  Product              Instance             Instance ID                    Feature                                 Language             Edition              Version         Clustered 
  SQL Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Database Engine Services                 1033                Standard Edition     10.0.1600.22    No        
  SQL Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            SQL Server Replication                   1033                Standard Edition     10.0.1600.22    No        
  SQL Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Full-Text and Semantic Extractions for Search 1033                 Standard Edition     10.0.1600.22    No        
  SQL Server 2008      MSSQLSERVER          MSAS10.MSSQLSERVER             Analysis Services                        1033                Standard Edition     10.0.1600.22    No        
  SQL Server 2008      MSSQLSERVER          MSRS10.MSSQLSERVER             Reporting Services - Native              1033                Standard Edition     10.0.1600.22    No        
  SQL Server 2008                                                          Management Tools - Basic                1033                 Standard Edition     10.0.1600.22    No        
  SQL Server 2008                                                          Management Tools - Complete             1033                 Standard Edition     10.0.1600.22    No        
  SQL Server 2008                                                          Client Tools Connectivity               1033                 Standard Edition     10.0.1600.22    No        
  SQL Server 2008                                                          Client Tools Backwards Compatibility    1033                 Standard Edition     10.0.1600.22    No        
  SQL Server 2008                                                          Client Tools SDK                        1033                 Standard Edition     10.0.1600.22    No        
  SQL Server 2008                                                          Integration Services                    1033                 Standard Edition     10.0.1600.22    No        

Package properties:
  Description:                   Microsoft SQL Server 2012 Service Pack 1
  ProductName:                   SQL Server 2012
  Type:                          RTM
  Version:                       11
  SPLevel:                       0
  Installation location:         G:\x64\setup\
  Installation edition:          Standard

Product Update Status:
  None discovered.

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      false
  AGTSVCACCOUNT:                 OFFICE\Administrator
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Automatic
  ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER12\OLAP\Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER12\OLAP\Config
  ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER12\OLAP\Data
  ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER12\OLAP\Log
  ASPROVIDERMSOLAP:              1
  ASSERVERMODE:                  MULTIDIMENSIONAL
  ASSVCACCOUNT:                  OFFICE\Administrator
  ASSVCPASSWORD:                 *****
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            OFFICE\Administrator
  ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER12\OLAP\Temp
  BROWSERSVCSTARTUPTYPE:         Automatic
  CLTCTLRNAME:                   <empty>
  CLTRESULTDIR:                  <empty>
  CLTSTARTUPTYPE:                0
  CLTSVCACCOUNT:                 <empty>
  CLTSVCPASSWORD:                <empty>
  CLTWORKINGDIR:                 <empty>
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130125_111854\ConfigurationFile.ini
  CTLRSTARTUPTYPE:               0
  CTLRSVCACCOUNT:                <empty>
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     <empty>
  ENABLERANU:                    false
  ENU:                           true
  ERRORREPORTING:                false
  FEATURES:                      SQLENGINE, REPLICATION, AS, BIDS, CONN, IS, BC, SSMS, ADV_SSMS
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTSQLSERVERLICENSETERMS:  true
  INDICATEPROGRESS:              false
  INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
  INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
  INSTALLSQLDATADIR:             <empty>
  INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
  INSTANCEID:                    MSSQLSERVER12
  INSTANCENAME:                  MSSQLSERVER12
  ISSVCACCOUNT:                  OFFICE\Administrator
  ISSVCPASSWORD:                 *****
  ISSVCSTARTUPTYPE:              Automatic
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  NPENABLED:                     0
  PID:                           *****
  QUIET:                         false
  QUIETSIMPLE:                   false
  ROLE:                          <empty>
  RSINSTALLMODE:                 DefaultNativeMode
  RSSHPINSTALLMODE:              DefaultSharePointMode
  RSSVCACCOUNT:                  <empty>
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         <empty>
  SECURITYMODE:                  <empty>
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 OFFICE\Administrator
  SQLSVCPASSWORD:                *****
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           OFFICE\Administrator
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBLOGDIR:               <empty>
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SQMREPORTING:                  false
  TCPENABLED:                    1
  UIMODE:                        Normal
  UpdateEnabled:                 true
  UpdateSource:                  MU
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130125_111854\ConfigurationFile.ini

Detailed results:
  Feature:                       Management Tools - Complete
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server 2008 Setup Support Files
  Component error code:          2349
  Component log file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130125_111854\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             The installer has encountered an unexpected error. The error code is 2349. Copy resumed with different info.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.0&EvtType=SqlSupport.msi%40InstallFiles%402349

  Feature:                       Client Tools Connectivity
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server 2008 Setup Support Files
  Component error code:          2349
  Component log file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130125_111854\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             The installer has encountered an unexpected error. The error code is 2349. Copy resumed with different info.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.0&EvtType=SqlSupport.msi%40InstallFiles%402349

  Feature:                       Client Tools Backwards Compatibility
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server 2008 Setup Support Files
  Component error code:          2349
  Component log file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130125_111854\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             The installer has encountered an unexpected error. The error code is 2349. Copy resumed with different info.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.0&EvtType=SqlSupport.msi%40InstallFiles%402349

  Feature:                       Management Tools - Basic
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server 2008 Setup Support Files
  Component error code:          2349
  Component log file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130125_111854\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             The installer has encountered an unexpected error. The error code is 2349. Copy resumed with different info.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.0&EvtType=SqlSupport.msi%40InstallFiles%402349

  Feature:                       SQL Server Data Tools
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server 2008 Setup Support Files
  Component error code:          2349
  Component log file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130125_111854\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             The installer has encountered an unexpected error. The error code is 2349. Copy resumed with different info.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.0&EvtType=SqlSupport.msi%40InstallFiles%402349

  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server 2008 Setup Support Files
  Component error code:          2349
  Component log file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130125_111854\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             The installer has encountered an unexpected error. The error code is 2349. Copy resumed with different info.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.0&EvtType=SqlSupport.msi%40InstallFiles%402349

  Feature:                       SQL Server Replication
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server 2008 Setup Support Files
  Component error code:          2349
  Component log file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130125_111854\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             The installer has encountered an unexpected error. The error code is 2349. Copy resumed with different info.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.0&EvtType=SqlSupport.msi%40InstallFiles%402349

  Feature:                       Integration Services
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server 2008 Setup Support Files
  Component error code:          2349
  Component log file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130125_111854\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             The installer has encountered an unexpected error. The error code is 2349. Copy resumed with different info.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.0&EvtType=SqlSupport.msi%40InstallFiles%402349

  Feature:                       Analysis Services
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server 2008 Setup Support Files
  Component error code:          2349
  Component log file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130125_111854\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             The installer has encountered an unexpected error. The error code is 2349. Copy resumed with different info.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.0&EvtType=SqlSupport.msi%40InstallFiles%402349

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130125_111854\SystemConfigurationCheck_Report.htm

Problem installing SQL Server 2012 SP1: "managed sql server installer has stopped working"

$
0
0

Hello,

I have a big problem.

I just downloaded SQL Server 2012 SP1 and I only want to install SSMS. The installer always crashes with an error message "managed sql server installer has stopped working".

I already tried all solutions from Google for this problem but nothing works.

Can someone help me plase?

My System: Window 8 Pro with Visual Studio 2012.

Thanks

Sven


Unable to install Microsoft SQL Server 2008 R2

$
0
0

It is showing error: Attempted to perform unauthorized operation. So was unable to install

Database Engine

Replication


TITLE: Microsoft SQL Server 2008 R2 Setup
------------------------------

The following error has occurred:

Attempted to perform an unauthorized operation.

Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1&EvtType=0x6121810A%25400x92D13C14

------------------------------
BUTTONS:

&Retry
Cancel
------------------------------

Log File

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):           -2068119551
  Exit facility code:            1211
  Exit error code:               1
  Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
  Start time:                    2013-01-25 10:59:08
  End time:                      2013-01-25 11:13:30
  Requested action:              Install
  Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130125_105747\Detail.txt
  Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.1600.1%26EvtType%3d0x6121810A%400x92D13C14

Machine Properties:
  Machine name:                  VARUNGUPTA-PC
  Machine processor count:       2
  OS version:                    Windows Vista
  OS service pack:               Service Pack 2
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x86
  Process architecture:          32 Bit
  OS clustered:                  No

Product features discovered:
  Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered
  Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             Database Engine Services                 1033                 Express Edition      10.3.5500.0     No       
  Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             SQL Server Replication                   1033                 Express Edition      10.3.5500.0     No       

Package properties:
  Description:                   SQL Server Database Services 2008 R2
  ProductName:                   SQL Server 2008 R2
  Type:                          RTM
  Version:                       10
  SPLevel:                       0
  Installation location:         d:\a716bfc2c0347dcd1c0fc7fcedc92a06\x86\setup\
  Installation edition:          EXPRESS_ADVANCED

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      True
  AGTSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Disabled
  ASBACKUPDIR:                   Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   Config
  ASDATADIR:                     Data
  ASDOMAINGROUP:                 <empty>
  ASLOGDIR:                      Log
  ASPROVIDERMSOLAP:              1
  ASSVCACCOUNT:                  <empty>
  ASSVCPASSWORD:                 *****
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            <empty>
  ASTEMPDIR:                     Temp
  BROWSERSVCSTARTUPTYPE:         Disabled
  CONFIGURATIONFILE:            
  CUSOURCE:                     
  ENABLERANU:                    True
  ENU:                           True
  ERRORREPORTING:                True
  FARMACCOUNT:                   <empty>
  FARMADMINPORT:                 0
  FARMPASSWORD:                  *****
  FEATURES:                      SQLENGINE,REPLICATION,SSMS
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 *****
  HELP:                          False
  IACCEPTSQLSERVERLICENSETERMS:  False
  INDICATEPROGRESS:              False
  INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
  INSTALLSHAREDWOWDIR:           C:\Program Files\Microsoft SQL Server\
  INSTALLSQLDATADIR:             <empty>
  INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
  INSTANCEID:                    MSSQLSERVER
  INSTANCENAME:                  MSSQLSERVER
  ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
  ISSVCPASSWORD:                 *****
  ISSVCSTARTUPTYPE:              Automatic
  NPENABLED:                     0
  PASSPHRASE:                    *****
  PCUSOURCE:                    
  PID:                           *****
  QUIET:                         False
  QUIETSIMPLE:                   False
  ROLE:                          AllFeatures_WithDefaults
  RSINSTALLMODE:                 FilesOnlyMode
  RSSVCACCOUNT:                  NT AUTHORITY\NETWORK SERVICE
  RSSVCPASSWORD:                 *****
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         *****
  SECURITYMODE:                  <empty>
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  Latin1_General_CI_AI
  SQLSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
  SQLSVCPASSWORD:                *****
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           VarunGupta-PC\Varun Gupta
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBLOGDIR:               <empty>
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SQMREPORTING:                  True
  TCPENABLED:                    0
  UIMODE:                        AutoAdvance
  X86:                           False

  Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130125_105747\ConfigurationFile.ini

Detailed results:
  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  MSI status:                    Passed
  Configuration status:          Passed

  Feature:                       SQL Server Replication
  Status:                        Failed: see logs for details
  MSI status:                    Passed
  Configuration status:          Passed

  Feature:                       Management Tools - Basic
  Status:                        Passed
  MSI status:                    Passed
  Configuration status:          Passed

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130125_105747\SystemConfigurationCheck_Report.htm

Can't install KB2716440. Installer cannot find my SQL Server instance

$
0
0

I have SQL Server 2008 R2 SP1 installed (I'm at 10.50.2500). Trying to apply the KB2716440-patch.

However, when I get to step three, "Select Features" I can't select anything. If i click "Select All" and try to proceed I get the following error:

[Error Message]
There are no SQL Server instances or shared features that can be updated on this computer.
================================================================================

There is definitely a SQL Server instance on the server and as far as I can tell, the patch has not been applied.

Installing BIDS

$
0
0

I have laptop having windows 7 OS

I want to learn SSIS and SSRS.I have no Visual studio , SQL Server installed on my machine.Please let me know what all is required to be installed.

SQL Server 2012 Domain Service Accounts

$
0
0

Hi,

I am using virtual box and have created a VM for a Domain Controller, a SQL Server and Sharepoint. The DC is up and running fine. I have the SQL Server server itself added to the domain. The issue I am having is assigning the service accounts during SQL installation. The machine recognizes the accounts and I have verified the passwords(and changed them 3 times) and are strong passwords. No matter what I do I get a list of errors:

The network address is invalid.

The SQL Server service account login or password is not valid. Use SQL Server Configuration Manager to update the service account.

The credentials you provided for the Analysis Services service are invalid. To continue, provide a valid account and password for the Analysis Services service.

...I get the same message as above for SSIS and SSRS.

I am totally confused at this point. Can I used the default 2012 issues and change them afterwards using Config MGR?

Thanks in advance for your help.

Dave

2005 Instance Starts in Single User Mode through Cluster Manager After Failed SP4 Install Attempt

$
0
0

I support a two node cluster running on Windows Server 2003 (x86) hosting 8 SQL Server 2005 instances. I upgraded a new instance to SP4 today, but the installation froze. Logs showed that the installation had completed successfully so after 2-hours, I kill the installer, and I attempted to bring the engine service online through cluster manager. The engine service wouldn't start and the service shows in cluster manager as being in a failed state.

When I try to bring the engine service online through cluster manager, the service never shows online and after a few moments again appears failed. If I start the service manually using the following, it starts fine:

net start "Machine\Foo"

But, when started like this, it doesn't show as online in cluster manager.

It appears that when started thru cluster manager, the instance comes online in single user mode. Once started some process connects to the instance, and as result, cluster manager's "alive" pollers can't connect, cause a failover which fails (that's another story), and the instance stays in a failed state.

I've confirmed that the startup parameters for the instance don't include a "-m". I've verfiied the startup parameters for the instance in the registry. Why is the cluster starting in single user mode when started from cluster manager?

ERRORLOG

2013-01-25 18:47:35.92 Server      Microsoft SQL Server 2005 - 9.00.5000.00 (Intel X86)
 Dec 10 2010 10:56:29
 Copyright (c) 1988-2005 Microsoft Corporation
 Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

(c) 2005 Microsoft Corporation.
All rights reserved.
Server process ID is 6140.
Authentication mode is MIXED.
Logging SQL Server messages in file 'L:\Microsoft SQL Server\MSSQL.8\MSSQL\LOG\ERRORLOG'.
This instance of SQL Server last reported using a process ID of 3564 at 1/25/2013 6:39:43 PM (local) 1/25/2013 11:39:43 PM (UTC). This is an informational message only; no user action is required.
Registry startup parameters:
  -d L:\Microsoft SQL Server\MSSQL.8\MSSQL\DATA\master.mdf
  -e L:\Microsoft SQL Server\MSSQL.8\MSSQL\LOG\ERRORLOG
  -l L:\Microsoft SQL Server\MSSQL.8\MSSQL\DATA\mastlog.ldf
SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
Detected 16 CPUs. This is an informational message; no user action is required.
Set AWE Enabled to 1 in the configuration parameters to allow use of more memory.
Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
Lock partitioning is enabled.  This is an informational message only. No user action is required.
Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
Database mirroring has been enabled on this instance of SQL Server.
Starting up database 'master'.
Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
SQL Trace ID 1 was started by login "sa".
Starting up database 'mssqlsystemresource'.
The resource database build version is 9.00.5000. This is an informational message only. No user action is required.
Server name is 'Machine\Foo'. This is an informational message only. No user action is required.
Starting up database 'model'.
The NETBIOS name of the local node that is running the server is 'NodeName'. This is an informational message only. No user action is required.
Clearing tempdb database.
A self-generated certificate was successfully loaded for encryption.
Server is listening on [ 192.168.0.1 <ipv4> 1860].
Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\Foo ].
Server local connection provider is ready to accept connection on [ \\.\pipe\$$\Machine\MSSQL$Foo\sql\query ].
Starting up database 'tempdb'.
The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x2098, state: 15. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
SQL Server is now ready for client connections. This is an informational message; no user action is required.
Starting up database 'DB3'.
Starting up database 'DB1'.
Starting up database 'DB2'.
Starting up database 'msdb'.
The Service Broker protocol transport is disabled or not configured.
The Database Mirroring protocol transport is disabled or not configured.
Error: 18456, Severity: 14, State: 11.
Login failed for user 'domain\srvaccount'. [CLIENT: 192.168.0.1]
...
Error: 18456, Severity: 14, State: 11.
Login failed for user 'domain\srvaccount'. [CLIENT: 192.168.0.1]
Analysis of database 'DB3' (7) is 100% complete (approximately 0 seconds remain). This is an informational message only. No user action is required.
CHECKDB for database 'DB3' finished without errors on 2012-12-13 18:01:36.530 (local time). This is an informational message only; no user action is required.
CHECKDB for database 'DB1' finished without errors on 2012-12-13 18:01:36.890 (local time). This is an informational message only; no user action is required.
Error: 18456, Severity: 14, State: 11.
Login failed for user 'domain\srvaccount'. [CLIENT: 192.168.0.1]
Error: 18456, Severity: 14, State: 11.
Login failed for user 'domain\srvaccount'. [CLIENT: 192.168.0.1]
Error: 18456, Severity: 14, State: 11.
Login failed for user 'domain\srvaccount'. [CLIENT: 192.168.0.1]
CHECKDB for database 'DB2' finished without errors on 2012-12-13 18:01:38.013 (local time). This is an informational message only; no user action is required.
Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.
Recovery is complete. This is an informational message only. No user action is required.
Error: 18456, Severity: 14, State: 11.
Login failed for user 'domain\srvaccount'. [CLIENT: 192.168.0.1]
....
Error: 18456, Severity: 14, State: 11.
Login failed for user 'domain\srvaccount'. [CLIENT: 192.168.0.1]
Service Broker manager has shut down.
SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.


Adam


Installing sql server 2008 Enterprise on Windows 7 Home Premium

$
0
0

Hi ,

I have installed server 2008 Enterprise on  Windows 7 Home Premium (64 Bit) but it failled.Later I tried to install

sql server 2008 service pack 1  but getting below error message.Can I installl sql server 2008 enterprise on windows 7 home premium?

sql server service failed to start after start windows 7

$
0
0
I installed SQL SERVER 2012 Enterprise. Everytime, I start windows, i should start sql server service . How to sql server service work fine?

SQL 2012 silent installation error 0x84B40002: '' is not a valid value for setting 'ACTION'

$
0
0

I am trying to install SQL 2012 and 2012 SP1 using powershell.

ACTION has been set to "Install"in the config file, but still I keep on getting this error.

'<null or empty string>' is not a valid value for setting 'ACTION'
Error Code 0x84B40002.

PS command: Start-Process "\\path\setup.exe" -ArgumentList "/CONFIGURATIONFILE=\\path\PriyankTest\AllFeatures.ini "  -WindowStyle Minimized -Wait


Error 2727 when installing Service Pack 2 on SQL Server 2008 R2 instance

$
0
0

Hello,

I am trying to install Service Pack 2 on SQL Server 2008 R2 cluster instance, but the following error message is registered in the SqlBrowser_Cpu32_1.log:

MSI (s) (C4:84) [14:42:00:240]: Note: 1: 2727 2: SqlInstanceInstall_32
MSI (s) (C4:84) [14:42:01:475]: Product: Microsoft SQL Server Browser -- Error 2727. The installer has encountered an unexpected error. The error code is 2727. The directory entry 'SqlInstanceInstall_32' does not exist in the Directory table.

Error 2727. The installer has encountered an unexpected error. The error code is 2727. The directory entry 'SqlInstanceInstall_32' does not exist in the Directory table.

Could anyone please help me with this issue?

I have already verified and there are no missing MSI/MSP files. Besides, I have searched and I have not discovered any information about how this issue can be solved.

Please I need your help!

Best regards,

Roberto

Trouble with installing SQL management studios

$
0
0
Im trying to install SQL Management Studio on windows 7 but I keep getting an error saying it can not found or see Microsoft Native Client but when I check in my programs I do have it, any suggestions? I have SQL server 2008 and was trying to install Management Studio 2008 express and my OS is Windows 7 Pro with service pack 1.

URGENT : SQL 2012 WEB SERVER - Install fails on Windows 2012 Server

$
0
0

Hi All

I am not able to install Sql Server 2012 on a virtualized (HyperV) Windows 2012 Server

It says "The SQL Server licence agreement cannot be located for the selected edition, WEB

This could be a result of corrupted media or the edition being unsupported by the media

Error code 0x858C001B"

The binaries are from an ISO downloaded from MSDN.

I had decompress all the files but no issue...

Any idea please? 

Thanks

E. Leite


Ernesto Leite Architecte .NET


NEED HELP: NOT ABLE TO INSTALL SQLSERVER 2000

$
0
0

NOT ABLE TO INSTALL SQLSERVER 2000 AND THIS ERROR COMES .

i am telling what is the message comes

"setup failed to configure the server.Refer to the server error log and C:\Windows\sqlstp.log for more information"

and log few last steps are 

19:57:08 StatsGenerate returned: 2
19:57:08 StatsGenerate (0xc0200805,0x1,0xf000000,0x200,1033,303,0x0,0x1,0,0,0
19:57:08 StatsGenerate -1,faizyab)
19:57:08 Installation Failed.

I WANT TO KNOW WHERE IS THE PROBLEM AND WHY DOES THIS ERROR OCCURS? AND HOW I CAN REMOVE IT ..


Cluster Installation of SQL 2008 R2: IP Address x.x.x.x is already in use.

$
0
0

Installing a new SQL 2008 R2 cluster on Windows 2008 R2 boxes.  Installation goes through till the installation starts and then returns the following message.  The NIC I am using is on a separate VLAN for this SQL Server box and the IP address I am trying to add absolutely does NOT exist on the network already.

TITLE: SQL Server Setup failure.
------------------------------

SQL Server Setup has encountered the following error:

The IP Address '10.220.56.100' is already in use. To continue, specify a different IP address.

Error code 0x84B40000.

SQL2K8 SP1 Installation Fails with Inability to Start SQL Browser Service

$
0
0

After the interview ends, and the installation of SQL2K8 SP1 is well and truly underway, it hangs on "SQLBrowserConfigEngAction_install_startup_cpu64"

After about fifteen minutes it asked me if I'd like to retry the startup of the browser service.  I agreed, and the installation continued satifactorily.

On a subsequent installation on the same machine, I could not get past that problem.   I have included the relevant parts of detail.txt below.

The machine in question is a clustered SQL2K8 SP2 machine on which I must load 7 slipstreamed instances of SQL2K8 SP1.   I am adding a partner machine, as well, to create a five-node cluster.  That machine is almost identical hardware and it never has any problems.

To judge from the error messages, it looks as if I might somehow be installed a 32-bit instance from the multiple slip stream directories.  Could that happen?

Thanks for your suggestions.

2013-01-28
10:52:48 Slp: Error: Action "SqlBrowserConfigEngAction_install_Startup_Cpu64"
failed during execution.<o:p></o:p>

2013-01-28
10:52:48 Slp: Action "SqlEngineConfigAction_install_startup_Cpu64"
will return false due to the following conditions:<o:p></o:p>

2013-01-28
10:52:48 Slp: Condition "Feature dependency condition for action:
SqlEngineConfigAction_install_startup_Cpu64 The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 10 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.<o:p></o:p>

2013-01-28
10:52:48 Slp: Condition is false because the required feature
SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result<o:p></o:p>

2013-01-28
10:52:48 Slp: Error: Action
"SqlEngineConfigAction_install_startup_Cpu64" failed during
execution.<o:p></o:p>

2013-01-28
10:52:48 Slp: Action
"ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_Startup_postmsi"
will return false due to the following conditions:<o:p></o:p>

2013-01-28
10:52:48 Slp: Condition "Feature dependency condition for action:
ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_Startup_postmsi
The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64.
There are 2 dependant features. The feature is tested for results:
ValidateResult, Result." did not pass as it returned false and true was
expected.<o:p></o:p>

2013-01-28
10:52:48 Slp: Condition is false because the required feature
SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result<o:p></o:p>


How to find Licence/Product Key from installed SQL Server ?

Object reference not set to an instance of an object. Unable to finish the SQL 2012 installation on a VM Machine

$
0
0

Hi, My name is Leonard and I am studying SQL. I have downloaded the newest MS SQL 2012 and also MS 2012 Hyper-V. I have set a MS 2012 Hyper-V on a laptop with AMD Turion 64 X2 and 3G of RAM (Planing to add more to max at 8G).

Following the instructions in the free onlineAdministering Microsoft SQL Server 2012 Databases” Training Kit, I have set 6 virtual machines as instructed in the Training Kit. While the installation of the MS Server Core 2008 R2 SP1 completed with no problem, the same cannot be said for the SQL Server 2012 installation. I have encountered an error that I have not seen anyone address in any of the SQL web forums.

After running the unattended setup instruction (Setup.exe /qs /ACTION=Install /FEATURES=SQLEngine /INSTANCENAME=MSSQLSERVER /SQLSVCACCOUNT="Njowa\Pa$$worD>" /SQLSVCPASSWORD=" Pa$$worD” /SQLSYSADMINACCOUNTS="Njowa\lenny#4!@" /AGTSVCACCOUNT="NT AUTHORITY\Network Service" /IACCEPTSQLSERVERLICENSETERMS) this is what I get after a series SQL setup initiation windows popups then disappears.

The following error occurred:

Object reference not set to an instance of an object.

Error result: -2147467261

Result facility Code: 0

Result error Code: 16387

Please review the summary.txt log for further details

My question is: What instance of an object is not properly initialize in the Setup instructions

Upgrade from SQL Server 2008 R2 to SQL Server 2012 SP1 Failure

$
0
0

This problem is solved, but I wanted to share the solution in case anybody else was having trouble.

I tried to upgrade from SQL Server 2008 R2 SP1 to SQL Server 2012 SP1.  Unfortunately during the upgrade, I received two error messages:

"No mapping between account names and security IDs was done" <--I received this two or three times during the upgrade.

"Value cannot be null – Parameter Name: userGroupName" <--I received this once.

For each of these errors, I was forced to click "Cancel" but the installation would continue and eventually finish.  Most components would install correctly except for the critical ones:  The Database Engine and SSAS.

Fortunately my 2008 SQL instance was still functioning so I wasn't shut down (I ran another production day as is), but I still needed to upgrade to SQL 2012.

Running the upgrade again didn't work.  It would appear to work, but it didn't even try upgrading the database engine or SSAS.  Even uninstalling SQL 2012 and re-performing the upgrade would not work.

I came across this blog post:

http://blogs.msdn.com/b/baliles/archive/2012/04/27/how-to-fix-a-failed-sql-2005-2008-r2-or-2012-install-upgrade-mssqlserver-inactive.aspx

This gentleman described very well how to identify inactive instances and delete them.  I followed his steps and was able to uninstall SQL 2012 and re-upgrade, but I ran into the same problem again with the error messages.

After uninstalling SQL 2012 as described in the blog, I tried repairing my SQL 2008 R2 install.  The repair yielded the same error messages, and could not fix it.  Frustrating, but at least I could run a repair to see if the error was fixed or not rather than installing/uninstalling SQL 2012 over and over.

I ran into a number of posts describing this error and linking it to domain controllers run on SQL servers (not recommended).  During an emergency a couple of years back, one of our admins upgraded our SQL server to a DC for a week or so.  I removed it from being a DC after the emergency had passed, but I think this was still carrying some SID issues in it.

The solution:

1. After a failed upgrade, follow the blog post above to remove SQL 2012 inactive instances and return to SQL 2008.

2. Temporarily change any service accounts on the SQL server (Database Engine account, SQL Server Agent account, SSAS, etc. - I only had three) that are running.  These were domain accounts in my installation.  I temporarily changed them to use my account (with admin rights), then after applying, I immediately changed them back to their original accounts.

3. I ran the SQL repair tool again (control panel -> uninstall/change the SQL Server program and click "Repair") and had no problems.  I don't think repairing did anything, but it didn't hurt and when it ran without errors I knew I was ready for a SQL upgrade.

4. Run the SQL Server 2012 upgrade.

This worked for me.  I hope it can save someone else some time and money.


Viewing all 7701 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>