Quantcast
Channel: SQL Server Setup & Upgrade forum
Viewing all 7696 articles
Browse latest View live

I need help !

$
0
0
I installed mssql 2008 r2 using web platform 5.0 on windows 7. My issue is it did not offer to install both windows sysadmin and sa account only windows account. What are my options now ? I use a lot of remote connections to web servers and many times they only allow administrator accounts to login. I prefer a SA account anyhow.

DKB


"You do not have exclusive access..."

$
0
0

Upon opening an MSAccess database, I (and other users) get the error message "You do not have exclusive access to the database at this time. If you proceed...." . We actually have to acknowledge several of these messages to finally get to the main menu of the database, at which time it works fine. When only one user is using the database, the error doesn't appear.

The database is on a server, and has several users, all connected thru a network. All users open the same Access file to use the database. The database is split, with all of the tables being on SQL Server.

Further explanation of the error when it appears: "When attempting to open a database in Design View, or when trying to save design changes to a database object, you may encounter this error message. Access requires an exclusive lock on the database to make design changes on some object types. This error indicates that Access has not obtained an exclusive lock on the database...." {there is more in the explanation}

All this happens on opening the database - no design changes are underway, and the database is not opening in Design View. I have verified that none of the other users is open in exclusive mode. No objects are being updated (although data might be being changed). I am the only user that can get to the navigation pane, and I never do that while other users are on the system (I do it at night, when all users are absent). Is there some way that one of the forms or tables or queries has retained an opening that locks the db? What are some possibilities that might throw this error?Is it because of the update to Access 2013 (which occurred some time ago, but the problem has only arisen recently)?

Incidentally, on the same server, I have 3 other Access-SQLServer split databases, all with multiple users, all users using a single Access file in each db, none of which have this problem. The main difference between the problem database and the others is the heavy use of VBA instead of macros to perform actions – is there something in VBA that might cause the error?

I have seen solutions on some forums that indicate that giving each user their own copy of the front end database will resolve this – but that would be a monstrous task for me, since the databases are frequently modified with new reports, calculations and features.

Can you help me find the problem that throws this error?

Thank You!

Troubleshooting Recent Problems with the application

$
0
0

Hi everybody,

My colleague developer is saying that starting recently she is getting errors about losing connections from our VFP application. I think it may be related with one of the latest Windows Updates, I saw a recent thread on the topic but could not find it (if someone has a link to that thread, it would be great).

What should I do to help her out?

I am personally having BSOD after most recent Windows Updates. I'm working on that problem now using this link

http://www.howtogeek.com/222532/how-to-repair-corrupted-windows-system-files-with-the-sfc-and-dism-commands/ 


For every expert, there is an equal and opposite expert. - Becker's Law


My blog


My TechNet articles

SQL Server 2K8 and TLS 1.2

$
0
0

Hello all,
I have Windows 2k8 Server R2 Std

with SQL Server 2k8 Std installed.
All fully patched and updated, even optional patches.

I have installed the patch for TLS 1.2 to work for SQL Server (KB3144113), and the SQL Server service is running fine.  no issues.  So I assume since I disabled TLS 1.0 and 1.1 that it is working fine with TLS 1.2.

No I am using .NET Framework 4.5.2, so I installed the ADO.NET client rollup (KB3099845)
Check the registry and it reflects for .NET 4.5.2 version 4.5.52333

But I can no longer use SSMS to connect to the instance that is running on the server.
I Have verified that the registry keys that are needed are in place for both Client and Server to use TLS 1.2

I have another DB Server with the same OS and SQL Server installed on it, and it appears to be working fine.

Any ideas why I cannot connect to the SQL Server instance?
If you go to the KB3135244 page, under "Known Issues"
I am basically seeing a combination for Issue 1 and Issue 2.
When I attempt to login to the SQL Server instance using SSMS, I get the error that is in Issue 2.


Thank you for your time


SQL 2012 changing instance from Ent to Standard

$
0
0

Hi All,

I have downloaded & installed Enterprise instance of SQL 2012 (The bits were downloaded from MSDN) is there a way to convert this instance to standard without the loss of data or re installation of  the instance.

Please Suggest !

Thanks,

Pranay.

Installing additional node to existing SQL instance in server 2012R2 failover cluster hangs after credentials screen

$
0
0

I'm having trouble adding an additional SQL Server 2012 node on a Server 2012R2 failover cluster, but only for one instance.

Installing a new node succeeds, and installing the second node to a new instance succeeds, but the installer hangs indefinitely with a "please wait" at the "specify service accounts" screen.  The only way to exit/kill the installer is to use task manager to kill the ScenarioEngine process.  I've even let the installer stay in this "please wait" state for two straight days.  No network traffic, no open connections, and no processes appear in "wait state" that I can see.  Domain authentication is verified to be okay on both nodes of this failover cluster.

This particular instance was installed on the failover cluster when it only had one node (the second node was down and the cluster had only one node configured at the time).

The installer does see the existing failover cluster instance and all checks pass with the exception of one warning about the non-clustered DTC.

It doesn't matter what we enter for credentials on the service account screen.  Leaving all passwords blank or entering verified correct passwords gives the same result.  The actual service account the existing instance was installed with: SQL Full-Text filter daemon account is LocalSystem, and the SQL Server accounts use a specific domain user.

Again, adding a new instance using the same credentials succeeds and adding a second node to that instance succeeds.  I don't know what's unique about this particular existing instance that is causing the installer to lock up.

I've come across other people having this same issue, but the solutions they arrived at don't seem to my particular installation.

Is there an installation logfile/statefile that I can inspect or supply to this thread?

(submitted by Erik S, using MSDN role account)

SQL Server Express won't Upgrade from 2012 to 2014

$
0
0

The upgrade process fails telling me I require SQL Server 2012 Service Pack 1 or later is required, but I have it installed.

The image below shows the error and my Windows Update history with the update showing.

Unable to install SSMS SQL 2014 on windows 7 (vc_red.msi)

$
0
0

I encountered a problem installing (on windows 7) the SSMS from the Management Studio 2014 Express installer .

The installer is asking me to enter an alternate path for vc_red.msi.

I used the browser and selected the folder were vc_red.msi is actually located but it says it is not a valid installation package for the product Microsoft Visual C++ 2010 x64 redistributable - 10.0.40219

I was trying to follow the solution from a similar post, but had no success.

The post is: 

https://social.msdn.microsoft.com/Forums/en-US/d2d92984-1b47-454c-be36-29eb1f284e41/unable-to-install-sql-server-developer-2012-on-windows-7-vcredmsi?forum=sqlsetupandupgrade

I went to the registry and could not find a reference to VC_RED.MSI that had a network path. The entries I found had empty info.

I installed SP1 for Visual Studio 10 too and made no difference.

Please help.


Paulino


SQL Server 2008 Service Pack failed on cluster environment

$
0
0

Hi All,

In my environment we are planing to upgrade from SQL 2008 SP3 to SP4 but we getting error in Active\Passive cluster.

Any risks if we do not upgrade SQL to SP4 from SQL perspective(risks, outstanding issues with current version, vulnerabilities, etc )

Please provide your inputs on this.

MS provide to plans to us

Plan 1:- 

1.      If the current installation fails, then we will have to remove both the VC++ 2005 and VC++ 2010 components from the server.
2.      Restart the server.
3.      Install a standalone instance of SQL Server 2008 on the server.
4.      Install the Service Pack 4 on the intended clustered instance. Notice the results.

Plan 2:- 

5.      If the installation still fails, then we may need to reinstall the Operating system on the server.
6.      The same action applies to all the nodes in the cluster. 

Note:- I need help on this if any case Plan 1 fails how to do in Plan 2 on existing environment to do reinstall the Operating system please provide to me any information how to processed on PLAN 2.

Regards,

Anji

SQL Services - Built in account or different account

$
0
0

Hi 

Please let me know that as per best practices under which service account should sql services (database engine, agent, integration,reporting, analysis etc) should run 

1 Local System

2. Local Service

3. Network Service

4. Local Administrator Windows account

5. Domain admin account

Regards,

Nikhil P Desai

Error while applying SQL server 2008 SP4

$
0
0

Hi Friends,

I am trying to apply SQL server 2008 SP4 to my instance. I am getting below error after the "check files in use" tab and i am not able to progress further.

When i check in the setupbootstrap log details.txt

File "C:\Program Files\Microsoft SQL Server\100\COM\DISTRIB.exe" has been locked.
 Error: Action "GatherUserSettings" threw an exception during execution

Exception type: System.IndexOutOfRangeException
   Message: 
       Index was outside the bounds of the array.
    Stack: 
         at Microsoft.SqlServer.Configuration.InstallWizard.FilesInUseController.RunLockedFileCheckCompleted(Object sender, RunWorkerCompletedEventArgs e)
2016-03-09 04:32:47 Slp: Watson Bucket 1

I have transactional replication configured in my instances. How should i proceed further? Should i stop SQL server agent service and try patching.

If that is the solution, is it okay to take down SQL agent services before applying SP.

Thanks

Udhayan



cluster instance name already exists

$
0
0

I am trying to install SQL 2012 clustered services (first install of SQL on this MS Server 2012R2 cluster). The AD objects have already been created (Nodes, Cluster Alias, and SQL network name). This is a requirement of the network I work in. I do not have ability to create domain objects. I have successfully installed several other similar clusters on this network, both SQL 2012 and SQL 2014. In this case, however, I get an error:

sql server failover cluster instance name already exists clustered resource

Of course the network name exists, but it has in every other case as well.  I checked the AD listing, and there is only one domain object with that name, and it belongs to me.  Why then am I getting this error??

I have seen multiple listings of this same error, but nothing that will resolve my situation.

Problem cannot open SQL 2012 error exception has been thrown by the target of an invocation

$
0
0
i cannot fix this problem .. hmm.. please help me

How to restore SQL Server 2008 R2 databases on SQL Server 2012

$
0
0

Hi everybody,

After long installation process I was finally successful in installing SQL Server 2012. So, my first idea was to try installing out databases and testing our application against it. But I'm not sure how exactly should I restore the databases? Can you show me the script? I've tried creating the DB first, then selecting the backup of the database, but at that point SSMS 2012 hang up.


For every expert, there is an equal and opposite expert. - Becker's Law


My blog

Problems installing SQL Server 2014 - There was a failure to calculate the applicability of setting LICENSEPATH.

$
0
0

Hi,

After googling frantically for a solution to my problem I decided to try to get some help from here.

I upgraded from Windows 7 to Windows 10 when it came available and had some previous versions of SQL Server installed before but uninstalled them before upgrading to Windows 10. There was alot of traces of the old installations and after spending hours removing them using msiinv.exe and cleaning out the registry, there shouldn't be anything left.

Still I get the same error when trying to install SQL Server 2014:  There was a failure to calculate the applicability of setting LICENSEPATH.

This applies to both the standard and the express version. The standard version is run from an iso and the express version from a .exe file.

EDIT: I noticed that I have the same Culture ID problem as the OP in:

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/a8a52f80-764d-4a01-b60a-1c4c363d1150/error-while-trying-to-upgrade-sql-2008-sp2-to-sql-2012-there-was-a-failure-to-calculate-the

I live in Finland but everything apart from the timezone and keyboard settings are set to english. This can't be an issue since It's worked fine before with previous versions of Windows.

Below is the Summary.txt file from the Log. Notice that the log file says Windows 8 when I'm actually running Windows 10

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2057043966
  Exit facility code:            1380
  Exit error code:               2
  Exit message:                  There was a failure to calculate the applicability of setting LICENSEPATH.
  Start time:                    2015-11-13 11:49:44
  End time:                      2015-11-13 11:49:52
  Requested action:              InstallFailoverCluster
  Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.4100.1&EvtType=0x0BA02FC6%400x294A9FD9&EvtType=0x0BA02FC6%400x294A9FD9

Machine Properties:
  Machine name:                  ***********
  Machine processor count:       8
  OS version:                    Windows 8
  OS service pack:               
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x64
  Process architecture:          64 Bit
  OS clustered:                  No

Package properties:
  Description:                   Microsoft SQL Server 2014 
  ProductName:                   SQL Server 2014
  Type:                          RTM
  Version:                       12
  Installation location:         H:\x64\setup\
  Installation edition:          

  Slipstream:                    True

User Input Settings:
  ACTION:                        InstallFailoverCluster
  AGTDOMAINGROUP:                <empty>
  AGTSVCACCOUNT:                 <empty>
  AGTSVCPASSWORD:                <empty>
  ASBACKUPDIR:                   Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   Config
  ASDATADIR:                     Data
  ASLOGDIR:                      Log
  ASPROVIDERMSOLAP:              1
  ASSERVERMODE:                  MULTIDIMENSIONAL
  ASSVCACCOUNT:                  <empty>
  ASSVCPASSWORD:                 <empty>
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            <empty>
  ASTEMPDIR:                     Temp
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:             
  ENU:                           true
  ERRORREPORTING:                false
  FAILOVERCLUSTERDISKS:          <empty>
  FAILOVERCLUSTERGROUP:          
  FAILOVERCLUSTERIPADDRESSES:    <empty>
  FAILOVERCLUSTERNETWORKNAME:    <empty>
  FEATURES:                      
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTSQLSERVERLICENSETERMS:  false
  INDICATEPROGRESS:              false
  INSTALLSHAREDDIR:              <empty>
  INSTALLSHAREDWOWDIR:           <empty>
  INSTALLSQLDATADIR:             <empty>
  INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
  INSTANCEID:                    <empty>
  INSTANCENAME:                  <empty>
  ISSVCACCOUNT:                  NT AUTHORITY\Network Service
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  PID:                           *****
  QUIET:                         false
  QUIETSIMPLE:                   false
  RSINSTALLMODE:                 DefaultNativeMode
  RSSHPINSTALLMODE:              DefaultSharePointMode
  RSSVCACCOUNT:                  <empty>
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         <empty>
  SECURITYMODE:                  <empty>
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 <empty>
  SQLSVCPASSWORD:                <empty>
  SQLSYSADMINACCOUNTS:           <empty>
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBLOGDIR:               <empty>
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SQMREPORTING:                  false
  UIMODE:                        Normal
  UpdateEnabled:                 false
  UpdateSource:                  <empty>
  USEMICROSOFTUPDATE:            false
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20151113_114943\ConfigurationFile.ini

Rules with failures:

Global rules:

There are no scenario-specific rules.

Rules report file:               The rule result report file is not available.

Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented

Exception type: Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingApplicabilityException
    Message: 
        There was a failure to calculate the applicability of setting LICENSEPATH.
    HResult : 0x85640002
        FacilityCode : 1380 (564)
        ErrorCode : 2 (0002)
    Data: 
      SettingId = LICENSEPATH
      WatsonData = Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingApplicabilityException@2
      HelpLink.EvtType = 0x0BA02FC6@0x294A9FD9
      DisableWatson = true
    Stack: 
        at Microsoft.SqlServer.Chainer.Infrastructure.Setting.CalculateApplicability()
        at Microsoft.SqlServer.Configuration.BootstrapExtension.ValidateChainerSettingAction.ExecuteAction(String actionId)
        at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
    Inner exception type: Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingValueException
        Message: 
                There was a failure to calculate the default value of setting LICENSEPATH.
        HResult : 0x85640001
                FacilityCode : 1380 (564)
                ErrorCode : 1 (0001)
        Data: 
          SettingId = LICENSEPATH
          WatsonData = Microsoft.SqlServer.Chainer.Infrastructure.CalculateSettingValueException@1
        Stack: 
                at Microsoft.SqlServer.Chainer.Infrastructure.Setting`1.CalculateValue()
                at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.CallQueuedSubscriberDelegates()
                at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.Publish(Publisher publisher)
                at Microsoft.SqlServer.Chainer.Infrastructure.Setting.CalculateApplicability()
        Inner exception type: System.ArgumentException
            Message: 
                        Culture ID 3072 (0x0C00) is not a supported culture.
                        Parameter name: culture
            HResult : 0x80070057
            Stack: 
                        at System.Globalization.CultureInfo..ctor(Int32 culture, Boolean useUserOverride)
                        at System.Globalization.CultureTable.GetCultures(CultureTypes types)
                        at Microsoft.SqlServer.Configuration.SetupExtension.LcidUtilities.GetLangPackParentFolderForLcid(String lcid)
                        at Microsoft.SqlServer.Configuration.SetupExtension.LcidUtilities.GetLcidFolder(ServiceContainer context, String baseFolderFullPath)
                        at Microsoft.SqlServer.Configuration.SetupExtension.LicensePathSetting.DefaultValue()
                        at Microsoft.SqlServer.Deployment.PrioritizedPublishing.PublishingQueue.CallFunctionWhileAutosubscribing[T](SubscriberDelegate subscriberDelegate, Int32 priority, AutosubscribingFunctionDelegate`1 function)
                        at Microsoft.SqlServer.Chainer.Infrastructure.Setting`1.CalculateValue()




SQL Server 2008R2 instance upgrade problem

$
0
0

Hello,

Here is the thing

I have 2 sql servers. each has ent instance with AG configured(servers in a cluster but instances are not) and several non clustered sql2008r2 instances.

I need to patch those 2008r2 instances. If I use the wizard I have an error rule:Cluster_IsOnlineIfClustered

To workaround this I extracted sql2008r2sp2 in a folder and ran

Setup /SkipRules=Cluster_IsOnlineIfClustered /action=patch

But it failed. I can't patch any instance. I would like to place log file here but it's to big.

How to find main error in this huge log ? Thanks




Upgrading from SQL Server Enterprise Evaluation Edition to SQL Server Enterprise Edition

$
0
0

I currently have SQL Server 2014 Enterprise Evaluation Edition installed on a VM and am done with the evaluation. 

I now want to upgrade to SQL Server 2014 Enterprise Edition (Core Based) License. Does this require me to download the full setup file and running through a setup again or is it just a matter of applying a license key?

SQL 2016 Upgrade Advisor Install error

$
0
0

I am trying to install the SQL 2016 Upgrade Advisor on a Windows 2008 64 bit EE server with SP2 (Build 6002).  (not 2008R2)

The server has one instance of SQL 2008R2 Std Edition with SP3 (Build 10.50.6220.0).

The install proceeds through the "I accept ..." then when I click Next I immediately get a pop-up with the following text.

The installer has encountered an unexpected error installing this package.  This may indicate a problem with the package.  The error code is 2885.

I ran "misExec -?" and it returned Windows ® Installer. V 4.5.6002.19424 .

The same package installed fine on a Windows 2008R2 64 bit EE server.

How do I get the package installed on the Widows 2008 Server?


Ray

Cannot install database engine services, sql server replication and sql writer !!!!

$
0
0

Hi, I try to install SQL Server 2012 Express but I have this error (I try to uninstall and delete register key, try to change account for database engine to NT Authority\System, but reinstall still not working ) pls help :

Feature failure reason:
An error occurred for a dependency of the feature causing the setup process for the feature to fail.

Error details:
§ Error installing SQL Server Writer Component
The installer has encountered an unexpected error installing this package. This may indicate a problem with the package. The error code is 29559.
Error code: 29559
Log file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20160310_225904\SqlWriter_Cpu32_1.log
Visit http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=SqlWriter.msi%40Do_sqlServiceSidType_32%4029559 to get help on troubleshooting.

Here is the summary of setup bootstrap
Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2068024457
  Start time:                    2016-03-10 23:00:02
  End time:                      2016-03-10 23:03:10
  Requested action:              Install

Setup completed with required actions for features.
Troubleshooting information for those features:
  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 Writer:          Use the following information to resolve the error, and then try the setup process again.


Machine Properties:
  Machine name:                  NHAT-PC
  Machine processor count:       2
  OS version:                    Future Windows Version
  OS service pack:               
  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  Configured
  SQL Server 2012                                                          Management Tools - Basic                 1033                 Express Edition      11.2.5058.0     No         Yes       
  SQL Server 2012                                                          Management Tools - Complete              1033                 Express Edition      11.2.5058.0     No         Yes       
  SQL Server 2012                                                          Client Tools Connectivity                1033                 Express Edition      11.2.5058.0     No         Yes       
  SQL Server 2012                                                          Client Tools Backwards Compatibility     1033                 Express Edition      11.2.5058.0     No         Yes       
  SQL Server 2012                                                          Client Tools SDK                         1033                 Express Edition      11.2.5058.0     No         Yes       

Package properties:
  Description:                   Microsoft SQL Server 2012
  ProductName:                   SQL Server 2012
  Type:                          RTM
  Version:                       11
  Installation location:         E:\1885bc8762c587e3d8\x86\setup\
  Installation edition:          Express

  Slipstream:                    True
  SP Level                       2

Product Update Status:
  Success: KB 2958429

Product Updates Selected for Installation:
  Title:                         Service Pack 2
  Knowledge Based Article:       KB 2958429
  Version:                       11.2.5058.0
  Architecture:                  x86
  Language:                      1033

  Update Source:                 Slipstream


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
  ASLOGDIR:                      Log
  ASPROVIDERMSOLAP:              1
  ASSERVERMODE:                  MULTIDIMENSIONAL
  ASSVCACCOUNT:                  <empty>
  ASSVCPASSWORD:                 <empty>
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            <empty>
  ASTEMPDIR:                     Temp
  BROWSERSVCSTARTUPTYPE:         Automatic
  CLTCTLRNAME:                   <empty>
  CLTRESULTDIR:                  <empty>
  CLTSTARTUPTYPE:                0
  CLTSVCACCOUNT:                 <empty>
  CLTSVCPASSWORD:                <empty>
  CLTWORKINGDIR:                 <empty>
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:             
  CTLRSTARTUPTYPE:               0
  CTLRSVCACCOUNT:                <empty>
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     <empty>
  ENABLERANU:                    true
  ENU:                           true
  ERRORREPORTING:                false
  FEATURES:                      SQLENGINE, REPLICATION
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTSQLSERVERLICENSETERMS:  true
  INDICATEPROGRESS:              false
  INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
  INSTALLSHAREDWOWDIR:           <empty>
  INSTALLSQLDATADIR:             <empty>
  INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
  INSTANCEID:                    DQN
  INSTANCENAME:                  DQN
  ISSVCACCOUNT:                  NT AUTHORITY\Network Service
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  NPENABLED:                     0
  PID:                           *****
  QUIET:                         false
  QUIETSIMPLE:                   false
  ROLE:                          AllFeatures_WithDefaults
  RSINSTALLMODE:                 DefaultNativeMode
  RSSHPINSTALLMODE:              DefaultSharePointMode
  RSSVCACCOUNT:                  <empty>
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         *****
  SECURITYMODE:                  SQL
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 NT AUTHORITY\SYSTEM
  SQLSVCPASSWORD:                *****
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           NHAT-PC\nhat
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBLOGDIR:               <empty>
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SQMREPORTING:                  false
  TCPENABLED:                    0
  UIMODE:                        AutoAdvance
  UpdateEnabled:                 true
  UpdateSource:                  Slipstream
  X86:                           false

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

Detailed results:
  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 Writer Component
  Component error code:          29559
  Component log file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20160310_225904\SqlWriter_Cpu32_1.log
  Error description:             The installer has encountered an unexpected error installing this package. This may indicate a problem with the package. The error code is 29559.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=SqlWriter.msi%40Do_sqlServiceSidType_32%4029559

  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 Writer Component
  Component error code:          29559
  Component log file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20160310_225904\SqlWriter_Cpu32_1.log
  Error description:             The installer has encountered an unexpected error installing this package. This may indicate a problem with the package. The error code is 29559.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=SqlWriter.msi%40Do_sqlServiceSidType_32%4029559

  Feature:                       SQL Writer
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Writer Component
  Component error code:          29559
  Component log file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20160310_225904\SqlWriter_Cpu32_1.log
  Error description:             The installer has encountered an unexpected error installing this package. This may indicate a problem with the package. The error code is 29559.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=SqlWriter.msi%40Do_sqlServiceSidType_32%4029559

Rules with failures:

Global rules:

Scenario specific rules:

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

SQL Management Studio 2014 - Installation failure with Exit code (Decimal) : -2068709375

$
0
0

I am attempting to perform an unattended installation of SQL Management Studio 2014 on aWindows 7 SP1 x64 operating system. I am using the extracted installation media to achieve this and using thesetup.exe (as highlighted below).

The command-line used is:

setup.exe /Q /IACCEPTSQLSERVERLICENSETERMS /CONFIGURATIONFILE="<path to ConfigurationFile.ini>"

The contents of the ConfigurationFile.ini is as follows:

***************************************************

;SQL Server 2014 Configuration File
[OPTIONS]

; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter. 

ACTION="Install"

; Detailed help for command line argument ROLE has not been defined yet. 

ROLE="AllFeatures_WithDefaults"

; Use the /ENU parameter to install the English version of SQL Server on your localized Windows operating system. 

ENU="True"

; Parameter that controls the user interface behavior. Valid values are Normal for the full UI,AutoAdvance for a simplied UI, and EnableUIOnServerCore for bypassing Server Core setup GUI block. 

; UIMODE="Normal"

; Setup will not display any user interface. 

QUIET="True"

; Setup will display progress only, without any user interaction. 

QUIETSIMPLE="False"

; Specify whether SQL Server Setup should discover and include product updates. The valid values are True and False or 1 and 0. By default SQL Server Setup will include updates that are found. 

UpdateEnabled="True"

; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature. 

ERRORREPORTING="False"

; If this parameter is provided, then this computer will use Microsoft Update to check for updates. 

USEMICROSOFTUPDATE="True"

; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, MDS, and Tools. The SQL feature will install the Database Engine, Replication, Full-Text, and Data Quality Services (DQS) server. The Tools feature will install Management Tools, Books online components, SQL Server Data Tools, and other shared components. 

FEATURES=CONN,BC,SDK,SSMS,ADV_SSMS,SNAC_SDK

; Specify the location where SQL Server Setup will obtain product updates. The valid values are "MU" to search Microsoft Update, a valid folder path, a relative path such as .\MyUpdates or a UNC share. By default SQL Server Setup will search Microsoft Update or a Windows Update service through the Window Server Update Services. 

UpdateSource="MU"

; Displays the command line parameters usage 

HELP="False"

; Specifies that the detailed Setup log should be piped to the console. 

INDICATEPROGRESS="False"

; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system. 

X86="False"

; Specify the root installation directory for shared components.  This directory remains unchanged after shared components are already installed. 

INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server"

; Specify the root installation directory for the WOW64 shared components.  This directory remains unchanged after WOW64 shared components are already installed. 

INSTALLSHAREDWOWDIR="C:\Program Files (x86)\Microsoft SQL Server"

; Specify that SQL Server feature usage data can be collected and sent to Microsoft. Specify 1 or True to enable and 0 or False to disable this feature. 

SQMREPORTING="False"

; Specify the installation directory. 

INSTANCEDIR="C:\Program Files\Microsoft SQL Server"

***************************************************

The installation initiates and then exits shortly. I see the following in the logs:

Please help.

Viewing all 7696 articles
Browse latest View live


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