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

microsoft.net framework unhandled exception has ocuured in your application

$
0
0

if you click continue, the application will ignore this error and attempt to continue. if you click quit, the application will close immediately.

Problem1:

This message occurs whe im installing sql server 2012 in my system (windows server 2012)

problem 2:

i installed windows server  2012 in my system. after i found wi-fi symbol is not coming. when i connect to lan internet is coming. but wi-fi is not coming. i clicked on w-lan in feauters. i done all the ways. please suggest any driver to me , so that i can install in my system.


Error installing SQL Server 2014 Database engine services Instance features

$
0
0

Hi.

I have been trying to install SQL Server 2014 with SP 1 under windows server essentials 2012. I have tried 32 and 64 bits versions (standard and express) both give me the same error 0x851A001A (wait on the database engine recovery handle failed) with the Database Engine Services.

I have followed some web recomendations, everyone with the unistall and install process: Change the user account, use administrative priviliges, with and without instance name. So far, same error arises at the end.

Could you please give me a hand on getting this solved.

P.S. In the same server I have already installed SQL Server 2008 R2.

Thanks, Joe.


José

New table - not opened in Table Designer

$
0
0

Hi,

I just installed SQL Management studio 2014 x86 on my computer. I downloaded it for free on the website.

I am using an Azure Database instance Server version V12.

Im trying to create a table but am unable to create it using the Table Designer.

It opens it by default as a query, and the Table Designer toolbar is grayed out.


Isn't it supported?

How to change the max size of an Azure SQL database

$
0
0

Hi, 

  It is a standard S0 tier database in Azure, upgraded from a basic tier database. So, it has max size of 2G. How can I change its max size to 10G?

Thanks,

Yuhang


www.dotnetideas.com

sql server

$
0
0
I really do not know when exactly  was the SQL teacher installed to us (students) sql server 2008 on our laptops. I t was about in the   last week of September 2015.  I again really do not know weather it was only sql server  2008 or 2008R2. I   somehow was able to copy it and install it on my desktop too. Now  again I wanted to try the new sql server 2012 and tried to install it on my desk top. In between my sql server on my desktop computer failed to connect. I am  out of sql server on my desktop to exercise  my study,  do practices & the get dreamed MDBA job. I am now in a mess. I do not have sufficient knowledge to get all of removed and start a new installed server on my desktop. Can any one help me how to solve this problem?

SQL Server 2014 service wont start start after updating sp1 (KB3058865, KB3075950, KB3094221)

$
0
0

Hi, my SQL Server 2014 is working fine in my server with WIndows 2012 until I installed new updates & service pack that was required for server hardening. 

I installed successfully SP1 KB 3058865 first then found out that the services wont start. After so many research for fix, i came with the 2 cu updates KB3075950, KB3094221 knowing that this could solve my problem but unfortunately its not.

I also tried changing the account of the services that many would suggest but its not working.

I tried replacing the master & maslog file but also failed.

I tried running it in single usermode and restore master db and etc.. also failed.

heres the log file:

016-02-01 15:21:21.83 Server      Microsoft SQL Server 2014 (SP1-CU3) (KB3094221) - 12.0.4427.24 (X64) 
Oct 10 2015 17:18:26 
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)

2016-02-01 15:21:21.84 Server      UTC adjustment: 8:00
2016-02-01 15:21:21.84 Server      (c) Microsoft Corporation.
2016-02-01 15:21:21.84 Server      All rights reserved.
2016-02-01 15:21:21.84 Server      Server process ID is 5128.
2016-02-01 15:21:21.86 Server      System Manufacturer: 'Microsoft Corporation', System Model: 'Virtual Machine'.
2016-02-01 15:21:21.86 Server      Authentication mode is MIXED.
2016-02-01 15:21:21.86 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2016-02-01 15:21:21.86 Server      The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
2016-02-01 15:21:21.86 Server      Registry startup parameters: 
-d C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2016-02-01 15:21:21.86 Server      Command Line Startup Parameters:
-s "MSSQLSERVER"
2016-02-01 15:21:22.27 Server      SQL Server detected 1 sockets with 1 cores per socket and 1 logical processors per socket, 1 total logical processors; using 1 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2016-02-01 15:21:22.27 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2016-02-01 15:21:22.28 Server      Detected 7999 MB of RAM. This is an informational message; no user action is required.
2016-02-01 15:21:22.28 Server      Using conventional memory in the memory manager.
2016-02-01 15:21:22.33 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2016-02-01 15:21:22.37 Server      This instance of SQL Server last reported using a process ID of 1600 at 2/1/2016 3:13:12 PM (local) 2/1/2016 7:13:12 AM (UTC). This is an informational message only; no user action is required.
2016-02-01 15:21:22.38 Server      The maximum number of dedicated administrator connections for this instance is '1'
2016-02-01 15:21:22.38 Server      Node configuration: node 0: CPU mask: 0x0000000000000001:0 Active CPU mask: 0x0000000000000001:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2016-02-01 15:21:22.40 Server      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.
2016-02-01 15:21:22.43 spid8s      Starting up database 'master'.
2016-02-01 15:21:22.49 Server      CLR version v4.0.30319 loaded.
2016-02-01 15:21:22.51 spid8s      8 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2016-02-01 15:21:22.61 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2016-02-01 15:21:22.62 spid8s      0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2016-02-01 15:21:22.62 spid8s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2016-02-01 15:21:22.79 spid8s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2016-02-01 15:21:22.80 spid8s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2016-02-01 15:21:22.88 spid8s      SQL Trace ID 1 was started by login "sa".
2016-02-01 15:21:23.28 spid8s      Server name is 'UATCASADB'. This is an informational message only. No user action is required.
2016-02-01 15:21:23.28 spid13s     A self-generated certificate was successfully loaded for encryption.
2016-02-01 15:21:23.33 spid13s     Server is listening on [ 'any' <ipv6> 1433].
2016-02-01 15:21:23.40 spid13s     Server is listening on [ 'any' <ipv4> 1433].
2016-02-01 15:21:23.44 spid13s     Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2016-02-01 15:21:23.44 spid13s     Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
2016-02-01 15:21:23.48 Server      Server is listening on [ ::1 <ipv6> 1434].
2016-02-01 15:21:23.49 Server      Server is listening on [ 127.0.0.1 <ipv4> 1434].
2016-02-01 15:21:23.49 Server      Dedicated admin connection support was established for listening locally on port 1434.
2016-02-01 15:21:23.49 Server      SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2016-02-01 15:21:23.60 spid14s     A new instance of the full-text filter daemon host process has been successfully started.
2016-02-01 15:21:23.71 Server      The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/UATCASADB.onenetworkbank.com.ph ] for the SQL Server service.
2016-02-01 15:21:23.72 Server      The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/UATCASADB.onenetworkbank.com.ph:1433 ] for the SQL Server service.
2016-02-01 15:21:23.97 spid17s     Starting up database 'msdb'.
2016-02-01 15:21:23.98 spid18s     Starting up database 'ReportServer'.
2016-02-01 15:21:23.98 spid19s     Starting up database 'ReportServerTempDB'.
2016-02-01 15:21:24.03 spid9s      Starting up database 'mssqlsystemresource'.
2016-02-01 15:21:24.08 spid9s      The resource database build version is 12.00.4427. This is an informational message only. No user action is required.
2016-02-01 15:21:24.11 Logon       Error: 18401, Severity: 14, State: 1.
2016-02-01 15:21:24.11 Logon       Login failed for user 'NT SERVICE\ReportServer'. Reason: Server is in script upgrade mode. Only administrator can connect at this time. [CLIENT: <local machine>]
2016-02-01 15:21:24.18 spid19s     1 transactions rolled forward in database 'ReportServerTempDB' (6:0). This is an informational message only. No user action is required.
2016-02-01 15:21:24.28 spid19s     0 transactions rolled back in database 'ReportServerTempDB' (6:0). This is an informational message only. No user action is required.
2016-02-01 15:21:24.44 spid17s     133 transactions rolled forward in database 'msdb' (4:0). This is an informational message only. No user action is required.
2016-02-01 15:21:24.73 spid17s     0 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.
2016-02-01 15:21:24.74 spid17s     Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
2016-02-01 15:21:24.79 spid9s      Starting up database 'model'.
2016-02-01 15:21:25.01 spid9s      Clearing tempdb database.
2016-02-01 15:21:25.94 spid9s      Starting up database 'tempdb'.
2016-02-01 15:21:26.12 spid20s     The Service Broker endpoint is in disabled or stopped state.
2016-02-01 15:21:26.12 spid20s     The Database Mirroring endpoint is in disabled or stopped state.
2016-02-01 15:21:26.15 spid20s     Service Broker manager has started.
2016-02-01 15:21:27.32 spid8s      Database 'master' is upgrading script 'msdb110_upgrade.sql' from level 201328592 to level 201331019.
2016-02-01 15:21:27.32 spid8s      ----------------------------------
2016-02-01 15:21:27.32 spid8s      Starting execution of PRE_MSDB.SQL
2016-02-01 15:21:27.32 spid8s      ----------------------------------
2016-02-01 15:21:28.36 spid8s      Setting database option COMPATIBILITY_LEVEL to 100 for database 'msdb'.
2016-02-01 15:21:28.56 spid8s      -----------------------------------------
2016-02-01 15:21:28.56 spid8s      Starting execution of PRE_SQLAGENT100.SQL
2016-02-01 15:21:28.56 spid8s      -----------------------------------------
2016-02-01 15:21:28.60 spid8s      Setting database option COMPATIBILITY_LEVEL to 120 for database 'msdb'.
2016-02-01 15:21:28.77 spid8s      Configuration option 'allow updates' changed from 1 to 1. Run the RECONFIGURE statement to install.
2016-02-01 15:21:28.77 spid8s      Configuration option 'allow updates' changed from 1 to 1. Run the RECONFIGURE statement to install.
2016-02-01 15:21:29.18 Logon       Error: 18401, Severity: 14, State: 1.
2016-02-01 15:21:29.18 Logon       Login failed for user 'NT SERVICE\ReportServer'. Reason: Server is in script upgrade mode. Only administrator can connect at this time. [CLIENT: <local machine>]
2016-02-01 15:21:31.84 spid8s      Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2016-02-01 15:21:31.86 spid8s      Using 'xpstar.dll' version '2014.120.4100' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2016-02-01 15:21:31.89 spid8s      DBCC TRACEOFF 1717, server process ID (SPID) 8. This is an informational message only; no user action is required.
2016-02-01 15:21:31.89 spid8s      DBCC execution completed. If DBCC printed error messages, contact your system administrator.
2016-02-01 15:21:31.90 spid8s       
2016-02-01 15:21:31.90 spid8s      Creating table temp_sysjobschedules
2016-02-01 15:21:32.20 spid8s       
2016-02-01 15:21:32.20 spid8s      Alter table sysdownloadlist...
2016-02-01 15:21:32.22 spid8s       
2016-02-01 15:21:32.22 spid8s      Alter table sysjobhistory...
2016-02-01 15:21:32.24 spid8s       
2016-02-01 15:21:32.24 spid8s      Alter table systargetservers...
2016-02-01 15:21:32.25 spid8s       
2016-02-01 15:21:32.25 spid8s      Alter table sysjobsteps...
2016-02-01 15:21:32.40 spid8s      Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
2016-02-01 15:21:32.40 spid8s      Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
2016-02-01 15:21:32.42 spid8s       
2016-02-01 15:21:32.42 spid8s      -----------------------------------------
2016-02-01 15:21:32.42 spid8s      Execution of PRE_SQLAGENT100.SQL complete
2016-02-01 15:21:32.42 spid8s      -----------------------------------------
2016-02-01 15:21:32.46 spid8s      DMF pre-upgrade steps...
2016-02-01 15:21:32.83 spid8s      DC pre-upgrade steps...
2016-02-01 15:21:32.83 spid8s      Check if Data collector config table exists...
2016-02-01 15:21:32.84 spid8s      Data Collector state before upgrade: 0
2016-02-01 15:21:32.84 spid8s      pre_dc100::Check if syscollector_collection_sets_internal table exists...
2016-02-01 15:21:32.84 spid8s      pre_dc100::Capturing Collection set status in temp table...
2016-02-01 15:21:33.05 spid8s      Deleting cached auto-generated T-SQL Data Collection packages from msdb...
2016-02-01 15:21:33.05 spid8s      End of DC pre-upgrade steps.
2016-02-01 15:21:33.05 spid8s      DAC pre-upgrade steps...
2016-02-01 15:21:33.06 spid8s      Starting DAC pre-upgrade steps ...
2016-02-01 15:21:33.06 spid8s      End of DAC pre-upgrade steps.
2016-02-01 15:21:33.06 spid8s      ----------------------------------
2016-02-01 15:21:33.06 spid8s      Starting execution of MSDB.SQL
2016-02-01 15:21:33.06 spid8s      ----------------------------------
2016-02-01 15:21:33.19 spid8s      Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2016-02-01 15:21:33.19 spid8s      Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2016-02-01 15:21:33.37 spid8s      Checking the size of MSDB...
2016-02-01 15:21:33.63 spid8s      Error: 8966, Severity: 16, State: 2.
2016-02-01 15:21:33.63 spid8s      Unable to read and latch page (1:56616) with latch type SH. Invalid page ID. failed.
2016-02-01 15:21:33.63 spid8s      Error: 8946, Severity: 16, State: 12.
2016-02-01 15:21:33.63 spid8s      Table error: Allocation page (1:56616) has invalid PFS_PAGE page header values. Type is 0. Check type, alloc unit ID and page ID on the page.
2016-02-01 15:21:33.63 spid8s      Error: 912, Severity: 21, State: 2.
2016-02-01 15:21:33.63 spid8s      Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 3601, state 5, severity 25. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
2016-02-01 15:21:33.64 spid8s      Error: 3417, Severity: 21, State: 3.
2016-02-01 15:21:33.64 spid8s      Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
2016-02-01 15:21:33.64 spid8s      SQL Server shutdown has been initiated
2016-02-01 15:21:33.64 spid8s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2016-02-01 15:21:34.70 spid8s      Error: 25725, Severity: 16, State: 1.
2016-02-01 15:21:34.70 spid8s      An error occurred while trying to flush all running Extended Event sessions.  Some events may be lost.
2016-02-01 15:21:34.71 spid13s     The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) [ MSSQLSvc/servername.urldomain ] for the SQL Server service. Error: 0x2af9, state: 61. Administrator should deregister this SPN manually to avoid client authentication errors.
2016-02-01 15:21:34.71 spid13s     The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) [ MSSQLSvc/servername.urldomain:1433 ] for the SQL Server service. Error: 0x2af9, state: 61. Administrator should deregister this SPN manually to avoid client authentication errors.

-----------------------------------------------------------------------------------------------

I would appreciate every help i can get. Thanks.



MS SQL restore missing data

$
0
0

Hi,

I have a database on DEV that I restored six months ago and now I would like to update with data from PROD.What will be best way to do it ?

I assume that i should use restore FULL on existing DEV database? Can someone describe mi full process, please?

Kind Regards,

M



SQL Server 2012 SP3 Extraction Fails

$
0
0

Hi,

I just did a new install of SQL Server 2012 Standard with SP2 (64 bit). I downloaded SP3 from Microsoft and when I install it during the extraction process get error "Extraction Failed: The operation was cancelled by the user".

I rebooted tried it again and it failed. I downloaded it again and the install had the same result.

Thanks in advance!


Recomended Instance Root Dir

$
0
0

Hello!

I´ve got a simple question about the sql server installation process. (SQL Server 2012 / 2014)

Is it recomemded to change the "instance root directory" to another drive than c:\ ?

It´s clear to seperate the data-files from c:\ - but when I change the "instance root directory",

then the Binaries from SQL Server move to that drive.

Thanx in advance!

Greetings

Karsten

Extended ASCII Settings

$
0
0

We have an sql server 2008 database that has been in service for nearly 3 years.  The users of the database are in the states.  Recently, we received some company name data that contained extended ASCII characters, such as, Ç (0xc7), Ã (0xc3), '.' (0xa0).  The database mangled the characters, including increasing the number of bytes.

What are the best practices for handling the extended ASCII?  Should they be converted to something close in regular ASCII, like C and A in the above example?  Or is there a setting that enables sql server to treat these extended characters correctly. If it's a setting, is it safe to apply and what is the best way to apply the steps.

Database Error When Running WordPress Site in Visual Studio

$
0
0

I've been trying to test/run/debug an existing Wordpress Site(which I didn't create) with Visual Studio for the last few days. I have added the php extensions. The debugger started working once I had added beta 8. However, I still can't run the site locally on my computer. 

As suggested by the php extension people, I downloaded mySQL. They suggested that I use a local version of mySQL for developing purposes instead of using the one that is on the live website. I then changed the wp-config.php file name in the hopes that this would force visual studio to reconfigure the WordPress site. No such luck. 

I added MySQL as a data source within the "Server Explorer" panel. I can see my computer as the server. I also added Message Queuing (MSMQ) as that had a red X next to it within the server's panel and from forums online, it seemed like this had something to do with passing data. There is no red X, but I still can't run the website locally. 

Right now, when I try to run the website in the browser, I get the words: Error Establishing a Database Connection. I can finally see the favicon in the browser, but I have no idea how it got there or why nothing else is showing up. 

If anyone could help me, I would really appreciate it. This is driving me crazy. 

Thanks,

Kelsey


Storage Server Changes To SQL2k5 User Databases

$
0
0

Hello,

We currently have a user database with the combined size of (including filegroups) of about 1.8 tb. SQL2k15 version. We want to first migrate the storage location to a new faster storage hardware before deciding to upgrade the SQL server version to SQL2k14. Here are my questions:

1. Our management wants to simply by consolidating the filegroups (15 total) into one .mdf file thinking that the higher performing new storage will compensate for performance degrading due to combination of filegroups into one .mdf file. Can this be done and if so, steps please. Of course, we will maintain separate drives for tempdb, templog, transaction logs and data (mdf) files. Basically, the goal is to take out the multiple filegroups.

2. Can we reduce the number of filegroups into say 5 instead of 15 (still allocate different drives) and if so, how can we merge some of the filegroups? Again, steps please.

Will greatly appreciate your early response.

Thanks.

Victor



VR3357

SQL server 2014 Install error: Missing dll

$
0
0

Hi everybody,

I am trying to install SQL Server 2014 on windows 10. Once the installer wizard starts installing, I get the following message:

There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.

I have already searched the web and tried every solution I could find (running as administator, changing the permissions for certain folders and re-installing). Any suggestions are welcome.

The last install log reports the following:

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2068052293
  Start time:                    2016-02-03 12:50:30
  End time:                      2016-02-03 12:52:43
  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 SDK:             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 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 SNAC:            Use the following information to resolve the error, and then try the setup process again.
  Next step for SNAC_SDK:        Use the following information to resolve the error, and then try the setup process again.


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

Product features discovered:
  Product              Instance             Instance ID                    Feature                                 Language             Edition              Version         Clustered  Configured

Package properties:
  Description:                   Microsoft SQL Server 2014 
  ProductName:                   SQL Server 2014
  Type:                          RTM
  Version:                       12
  SPLevel:                       0
  Installation location:         C:\Users\melchior\Documents\SQLEXPRWT_x64_ENU\x64\setup\
  Installation edition:          Express

Product Update Status:
  None discovered.

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:         Disabled
  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, CONN, BC, SDK, SSMS, ADV_SSMS, SNAC_SDK
  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:                    SQLEXPRESS
  INSTANCENAME:                  SQLEXPRESS
  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:                         <empty>
  SECURITYMODE:                  <empty>
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  Latin1_General_CI_AS
  SQLSVCACCOUNT:                 NT Service\MSSQL$SQLEXPRESS
  SQLSVCPASSWORD:                <empty>
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           MELCHIOR\melchior
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBLOGDIR:               <empty>
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SQMREPORTING:                  false
  TCPENABLED:                    0
  UIMODE:                        AutoAdvance
  UpdateEnabled:                 true
  UpdateSource:                  MU
  USEMICROSOFTUPDATE:            false
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160203_125029\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 Native Client Access Component
  Component error code:          1723
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160203_125029\sqlncli_Cpu64_1.log
  Error description:             There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723

  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 Native Client Access Component
  Component error code:          1723
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160203_125029\sqlncli_Cpu64_1.log
  Error description:             There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723

  Feature:                       Client Tools SDK
  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 Native Client Access Component
  Component error code:          1723
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160203_125029\sqlncli_Cpu64_1.log
  Error description:             There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723

  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 Native Client Access Component
  Component error code:          1723
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160203_125029\sqlncli_Cpu64_1.log
  Error description:             There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723

  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 Native Client Access Component
  Component error code:          1723
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160203_125029\sqlncli_Cpu64_1.log
  Error description:             There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723

  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 Native Client Access Component
  Component error code:          1723
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160203_125029\sqlncli_Cpu64_1.log
  Error description:             There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723

  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 Native Client Access Component
  Component error code:          1723
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160203_125029\sqlncli_Cpu64_1.log
  Error description:             There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723

  Feature:                       SQL Client Connectivity
  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 Native Client Access Component
  Component error code:          1723
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160203_125029\sqlncli_Cpu64_1.log
  Error description:             There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723

  Feature:                       SQL Client Connectivity SDK
  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 Native Client Access Component
  Component error code:          1723
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160203_125029\sqlncli_Cpu64_1.log
  Error description:             There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20160203_125029\SystemConfigurationCheck_Report.htm

Changing SQL Locale

$
0
0

We are testing san application to mimic multiple locales, like UK, Germany, US etc

Changing the OS locale is simple. How do I change the SQL locale to reflect different countries?

The difference in locale can be seen as below grid

Date   Format

Thousand   Separator

Decimal   Separator

Alignment

          M/D/YYYY

,

.

Right

DD/MM/YYYY

,

.

Right

DD/MM/YYYY

,

.

Left

DD/MM/YYYY

;

,

Right

DD/MM/YYYY

;

,

Right

DD.MM.YYYY

;

,

Right

DD.MM.YYYY

;

,

Right

YYYY/MM/DD

,

.

Right

YYYY/MM/DD

,

.

Right

YYYY-M-D

,

.

Right

D/MM/YYYY

,

.

Right

D/M/YYYY

,

.

Right

D-M-YYYY

;

,

Right

How do I repair connection error?

$
0
0

I'm running SQL Server 2014 Developer on a Windows 10 64-bit computer. Before to day all was good. Today none of my applications that use SQL Server can connect. Also I can't connect using the  Management Studio. I tried going to Program and Features and running a repair on "Microsoft SQL Server 2014 Setup (English), and that didn't help. Here's the error I get in the Management Studio.


SQL High availability WITHOUT domain???

$
0
0

Hi

Our single SQL server enterprise 2012 is on a workgroup.  There is no domain.

I would like to make the databases highly available.  (Database Mirroring, AlwaysOn, Clustering..)

What can I do considering the fact that I am on a workgroup and not a domain?  Do ALL of these options require active directory?

Have Solution Explorer list past Solutions when first opening SSMS

$
0
0

I created some scripts under a solution with a project and it works fine. But, when I first open up SSMS, the only listing in the Solution Window is the default new one. Is there a way, so that it will list my past solutions and projects to save me a couple of steps?

Thanks,

Paul

same shared storage used between multiple MS SQL FCIs

$
0
0

Hello,

I wonder if I can install multiple SQL 2012 FCIs on Windows Server 2012R2 using the same shared storage for all the FCIs? 

Is there a workaround or solution to overcome this

thanks in advance and regards, Thomas


kind regards, Thomas G. Apostolou

Sqlserver Services is taking almost 99% cpu and RAM.

$
0
0

Hello ,

I have multiple servers. In one of the servers sqlserver services almost taking 99% of CPU and least 6GB of RAM. Even we don't run any queries the situation is same. What might be the reason for this ?

any inputs appreciated.

Thanks in advance.

removing sql server from pc

$
0
0

I have  the following sql servers:  2008, 2008r, 2012 and 2014 installed unsuccessfully at different status. I was successfully using sql serer 2008r freely for a little less than 6 months. One day it stopped connecting. Since then I tried  itself & other  different editions to get  install & get connected. But none was   successful even in install and setup process. Now I wanted to totally  remove all of them and try it at fresh either free editions or by paying for the edition good for a student to be a DBA. can you help me get out of this problem and give me the best advice?

Viewing all 5760 articles
Browse latest View live


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