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

Consistency validation for SQL Server registry keys

$
0
0

I cannot get past this support rule when I attempt to install SQL Server 2008 RC0.  When I attempt to drill into the failure the popup states "The SQL Server registry keys from a prior installation cannot be modified.  To continue, see SQL Server Setup documentation about how to fix registry keys."

 

First off, why would the SQL Server 2008 RC0 install attempt to modify registry keys from a prior installation if I am attempting to install it side-by-side with a prior install of SQL Server 2005 Developer Edition?  

 

Second, can anyone point me to the SQL Server Setup documentation that walks me through how to go about fixing these registry keys?

 

Any help would be greatly appreciated.  Thanks in advance for your help.

 

Wendell G

   


SQL Server 2008R2 Installation is failing

$
0
0

SQL Server 2008R2 Installation is failing with below error, Please advise to troubleshoot the issue.

Problem signature:
  Problem Event Name: BEX64
  Application Name: setup100.exe
  Application Version: 10.50.1600.1
  Application Timestamp: 4bb6742c
  Fault Module Name: MSVCR80.dll
  Fault Module Version: 8.0.50727.6195
  Fault Module Timestamp: 4dcdd833
  Exception Offset: 000000000001da44
  Exception Code: c000000d
  Exception Data: 0000000000000000
  OS Version: 6.1.7601.2.1.0.274.10
  Locale ID: 1033
  Additional Information 1: e26e
  Additional Information 2: e26e8dde6754e3fdd78d21957d8e6ab6
  Additional Information 3: 1efb
  Additional Information 4: 1efb4b37e67d75efd9f63531396f8184
Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt


Vinai Kumar Gandla


SQL Server 2019 CTP 2.0 - Polybase with SAP HANA

$
0
0

Hello, 

We are considering a pilot of SQL Server 2019 CTP 2.0.  <g class="gr_ gr_191 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins replaceWithoutSep" data-gr-id="191" id="191">One</g> the biggest things we want to test with this pilot is the extended Polybase functionality with other data sources, such as Oracle and SAP HANA.  Does anyone know or have experience with the following and can provide me feedback:

  • Does SQL 2019 CTP2.0 Polybase connect to SAP HANA?
  • Are there any potential issues connecting to an SAP HANA instance that is running on SAP Cloud?
  • Has anyone connected SQL 2019 CTP 2.0 Polybase to an Oracle SAP ECC 6.0 database?  Any problems or feedback?

Any information would be greatly appreciated!

Thanks,

Kent

[SOLVED] A MOF syntax error occured, installing SQL Server 2012 Advanced Express 64 bit edition

$
0
0

I'm trying to install SQL server on my windows 7 workstation and got this error:

A MOF syntax error occured.

I looked in the SQL setup bootstrap folder and found the detail.txt. It says:

(01) 2015-11-29 19:23:58 Slp: Installing WMI Provider
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to open registry subkey 
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\110
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to get registry value SharedCode
(01) 2015-11-29 19:23:58 Slp: SharedDirPath is C:\Program Files (x86)\Microsoft SQL Server\110\Shared\
(01) 2015-11-29 19:23:58 Slp: Attempting to install MOF/MFL file for WMI Provider C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to install MOF file
(01) 2015-11-29 19:23:58 Slp: Running: C:\Windows\system32\WBEM\mofcomp.exe "C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof"
(10) 2015-11-29 19:23:59 Slp: Microsoft (R) MOF Compiler Version 6.1.7600.16385
(10) 2015-11-29 19:23:59 Slp: Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
(10) 2015-11-29 19:24:00 Slp: Parsing MOF file: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof
(10) 2015-11-29 19:24:00 Slp: MOF file has been successfully parsed
(10) 2015-11-29 19:24:00 Slp: Storing data in the repository...
(10) 2015-11-29 19:24:03 Slp: An error occurred while processing item 10 defined on lines 73 - 79 in file C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof:
(10) 2015-11-29 19:24:03 Slp: Compiler returned error 0x80070005Error Number: 0x80070005, Facility: Win32
(10) 2015-11-29 19:24:03 Slp: Description: Access is denied.
(10) 2015-11-29 19:24:03 Slp: 
(01) 2015-11-29 19:24:03 Slp: Sco: Compile operation for mof file C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof failed. Exit code 3
(01) 2015-11-29 19:24:03 Slp: Configuration action failed for feature CommonFiles during timing ConfigNonRC and scenario ConfigNonRC.
(01) 2015-11-29 19:24:03 Slp: A MOF syntax error occurred.
(01) 2015-11-29 19:24:03 Slp: The configuration failure category of current exception is ConfigurationFailure
(01) 2015-11-29 19:24:03 Slp: Configuration action failed for feature CommonFiles during timing ConfigNonRC and scenario ConfigNonRC.
(01) 2015-11-29 19:24:04 Slp: Microsoft.SqlServer.Configuration.Sco.ScoException: A MOF syntax error occurred.
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof()
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.Install_ConfigWMIProvider(Dictionary`2 actionData)
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.Install_PostMSI(Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.InstallImpl(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
(01) 2015-11-29 19:24:04 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2015-11-29 19:24:04 Slp: Inner exceptions are being indented
(01) 2015-11-29 19:24:04 Slp: 
(01) 2015-11-29 19:24:04 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
(01) 2015-11-29 19:24:04 Slp:     Message: 
(01) 2015-11-29 19:24:04 Slp:         A MOF syntax error occurred.
(01) 2015-11-29 19:24:04 Slp:     HResult : 0x84bb0001
(01) 2015-11-29 19:24:04 Slp:         FacilityCode : 1211 (4bb)
(01) 2015-11-29 19:24:04 Slp:         ErrorCode : 1 (0001)
(01) 2015-11-29 19:24:04 Slp:     Data: 
(01) 2015-11-29 19:24:04 Slp:       SQL.Setup.FailureCategory = ConfigurationFailure
(01) 2015-11-29 19:24:04 Slp:       WatsonConfigActionData = INSTALL@CONFIGNONRC@COMMONFILES
(01) 2015-11-29 19:24:04 Slp:       WatsonExceptionFeatureIdsActionData = System.String[]
(01) 2015-11-29 19:24:04 Slp:     Stack: 
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof()
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.Install_ConfigWMIProvider(Dictionary`2 actionData)
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.Install_PostMSI(Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.InstallImpl(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
(01) 2015-11-29 19:24:04 Slp: Watson Bucket 1 
 Original Parameter Values 

(01) 2015-11-29 19:24:04 Slp: Parameter 0 : SQL Server 2012@RTM@ 

(01) 2015-11-29 19:24:04 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof 

(01) 2015-11-29 19:24:04 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof 

(01) 2015-11-29 19:24:04 Slp: Parameter 3 : Microsoft.SqlServer.Configuration.Sco.ScoException@1211@1 

(01) 2015-11-29 19:24:04 Slp: Parameter 4 : Microsoft.SqlServer.Configuration.Sco.ScoException@1211@1 

(01) 2015-11-29 19:24:04 Slp: Parameter 5 : Slp_Config_Install_Core_WMI_Provider 

(01) 2015-11-29 19:24:04 Slp: Parameter 6 : INSTALL@CONFIGNONRC@COMMONFILES 

(01) 2015-11-29 19:24:04 Slp: 
 Final Parameter Values 

(01) 2015-11-29 19:24:04 Slp: Parameter 0 : SQL Server 2012@RTM@ 

(01) 2015-11-29 19:24:04 Slp: Parameter 1 : 0xA60E3551 

(01) 2015-11-29 19:24:04 Slp: Parameter 2 : 0xA60E3551 

(01) 2015-11-29 19:24:04 Slp: Parameter 3 : 0xD3BEBD98@1211@1 

(01) 2015-11-29 19:24:04 Slp: Parameter 4 : 0xD3BEBD98@1211@1 

(01) 2015-11-29 19:24:04 Slp: Parameter 5 : Slp_Config_Install_Core_WMI_Provider 

(01) 2015-11-29 19:24:04 Slp: Parameter 6 : 0x4E91350D 

(01) 2015-11-29 19:24:06 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
(01) 2015-11-29 19:24:12 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2015-11-29 19:24:13 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
(01) 2015-11-29 19:24:13 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
(01) 2015-11-29 19:24:13 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2015-11-29 19:24:13 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
(01) 2015-11-29 19:24:50 Slp: A MOF syntax error occurred.
(01) 2015-11-29 19:24:50 Slp: Watson bucket for exception based failure has been created
(01) 2015-11-29 19:38:42 Slp: Error: Action "Slp_Config_Install_Core_WMI_Provider_Cpu64" failed during execution.
(01) 2015-11-29 19:38:42 Slp: Completed Action: Slp_Config_Install_Core_WMI_Provider_Cpu64, returned False

How do I rectify this? Grateful for your advice.


A MOF syntax error occured, installing SQL Server 2008 r2 32 bit edition

$
0
0
Can you help me to solve the issue

sql server backup how to verify, your backup is correct and not corrupted

$
0
0
I am go to take adhoc sql full backup, before application upgrade 

BACKUP DATABASE testdb TO DISK = 'C:\testdb.BAK' WITH STATS,

DESCRIPTION = 'Full backup for AdventureWorks' GO


How do you I know, my backup is not corrupted, and will work after repair sql database, incase if required sorry I dont have environment to test it. 

Do i need to do consistency check or readability check before take backup, if yes, how can i do that in Tsql?



Connecting to the Listner in an AG

$
0
0

Hi!

I've just built a 2 node Azure 2016 HA always on cluster and its all working except for 1 thing. I can connect via ssms to both instances using the instance names, but the listener name (AG-TmProd) does not connect... 

Im not sure what I've missed..  Any ideas?

Thanks,

Zoe

Want to upgrade SQL Server 2012 to SQL Server 2017

$
0
0

We have SQL Server 2012 Standard License, Now we need to upgrade it to SQL Server 2017. Is it possible ??


Database Backup BLOCKSIZE Parameter

$
0
0

Dear Sir

In order  to imroving backup performance i am using MAXTRANSFERSIZE,BUFFERCOUNT  and  BLOCKSIZE parameter in below Command. w.r.t it I have 2 question.

1. If I run below command than these parameter value ( MAXTRANSFERSIZE,BUFFERCOUNT  and  BLOCKSIZE ) will used for this session only. It will not impact on other job/Server?

2.  Where I can see BLOCKSIZE value. Is it realy work. I mean can we change BLOCKSIZE for particular session as mention below.

DBCC TRACEON (3605,-1)
DBCC TRACEON (3213,-1)

BACKUP DATABASE [TST_DB] TO
DISK = 'D:\DBA\back1.bak',
DISK = 'D:\DBA\OSAK\back2.bak',
DISK = 'D:\DBA\OSAK\back3.bak',
DISK = 'D:\DBA\OSAK\back4.bak',
DISK = 'D:\DBA\OSAK\back5.bak'
with name = 'Backup_ABC', NOINIT,

MAXTRANSFERSIZE = 2097152,
BUFFERCOUNT = 50,
BLOCKSIZE = 8192,

NOSKIP, NOFORMAT   , COMPRESSION, STATS = 5
DBCC TRACEOFF(3605,-1)
DBCC TRACEOFF(3213,-1)

Please suggest me if there any other way to improve backup inconsistency.

Regards,

Deepak

SQL Server 2016 install fails due to Data Tier App Framework installed by SSMS 2017

$
0
0

Hello,

Trying to deploy SQL Server 2016 on a maschine that already has SQL Server Mgmt Studio 2017 (v14.0.17277.0) installed. This leads to an exception during installation: 

(01) 2018-10-12 13:25:04 Slp: Target package: "C:\WINDOWS\ccmcache\n\1033_ENU_LP\x64\setup\x86\DACFramework.msi"
(01) 2018-10-12 13:25:04 Slp: MSI Error: 0 A newer version of Microsoft SQL Server Data-Tier Application Framework is already installed.
(01) 2018-10-12 13:25:04 Slp: InstallPackage: MsiInstallProduct returned the result code 1603.

Indeed, the machine has SQL Server Data-Tier Application Framework x86 v14.0.4079.2 already installed during setup of SSMS 2017.

Reproduced this by: 

  • uninstalling SSMS 2017
  • uninstalling Data-Tier Application Framework
  • rebooting
  • installing SSMS 2017 again
  • > this brings back the data tier application framework v14

When I uninstall the framework and then retry setup for SQL Server 2016, the installation completes successfully.

This creates the following questions for me: 

  • is it generally not supported to install SQL Server 2016 when SSMS 2017 is already installed?
  • can I somehow prevent SSMS 2017 from installing Data Tier Application Framework?
  • can I tell SQL Server 2016 to ignore teh fact that a newer version of Data Tier Application Framework is already installed?

Upgrading From v2012 to v2017 Invalid Namespace

$
0
0

I'm trying to do an in-place upgrade from SQL Server 2012 to SQL Server 2017. The process appears to get almost to the end then errors out with 'Invalid namespace'.

The installer log file shows the error:

'Attempting to uninstall MOF file for namespace \\.\root\Microsoft\SQLServer\ReportServer\xxxxxx Management exception: InvalidNamespace encountered.'

Reporting Services is not installed on this server and I didn't select any option to insall it, so I don't know why this issue is coming up.

If I run Reporting Services Configuration Manager I get the error:

'Report Server WMI Provider error: Invalid namespace'.

I don't know how to get passed this. Can anyone help??

Thanks!

Location of system databases - thoughts?

$
0
0

Hi

I am currently doing a system audit on our SQL Server estate.

One thing that has provoked thinking is the location of the 3 system databases master, model and msdb.

All SQL instances have them currently on our C:\ drive.

I distinctly remember that other organisations I have worked for had system DBs strored on the SQL data drives or stored on their own LUNS - which got me thinking about a few questions:

  1. are there any advantages or disadvantages to having these system databses remaining on the same drive as the OS?
  2. if system databases are stored on the data drives (ie, the same drive as all/most of the other mdf files), will this impact on each other? If so, how much?
  3. are there any business cases where the best practice is to have these system databases on it's own drive space?

This is just a few questions to get a feel of other user's esxperiences on this matter.

Any comments would be appreciated.

Thanks in advance.

SQL Server Enterprise Core 2012

$
0
0

When trying to in stall SQL Sever Enterprise core 2012 on a Hyper-V VM running Microsoft server 2008 r2 Data Center I recieve a error 0x84B20001. First a box pops up and says "Please wait while Microsoft Server 2012 setup processes the current operation. Then a box pops up and says SQL Server setup failure.

The action type "ExecuteWorkflowAction" is not valid for the WorkflowIdentity element. The only valid action type is ExecuteWorkflowAction.

Error Code: 0x84B20001

What do I need to do to get past this error?

Trailing blanks in unique index

$
0
0

Hi!

I have migrated Oracle-tables to SQL Server using SSMA. First I did the migration to the master database and then I made the same migration to a new database I had created with default settings. The migration to the new database failed but the migration to the master database was ok.

The problem was an unique index violation. The column (varchar) had values with only trailing blanks that differs ("ABC" and "ABC "). As it was not a problem in the master database I presume it's a setting in the database, but I don't know which setting it is.

Where is the setting that makes SQL Server regard "ABC" and "ABC " as different values?

Unable to install SQL Server (setup.exe), VS Shell installation has failed with exit code 1638.

$
0
0

Detail:

(01) 2017-10-19 02:14:41 Slp: Log provider 'Microsoft.SqlServer.Chainer.Infrastructure.LogProviderFile' has been registered
(01) 2017-10-19 02:14:41 Slp: Log provider 'Microsoft.SqlServer.Chainer.Infrastructure.LogProviderConsole' has been registered
(01) 2017-10-19 02:14:41 Slp: Log provider 'Microsoft.SqlServer.Chainer.Infrastructure.LogProviderStatus' has been registered
(01) 2017-10-19 02:14:41 Slp: Reading XML resource 'Microsoft.SQL.Chainer.PackageData.Package.xml'
(01) 2017-10-19 02:14:41 Slp: Reading schema resource 'Microsoft.SQL.Chainer.Package.Package.xsd'
(01) 2017-10-19 02:14:41 Slp: Document 'Microsoft.SQL.Chainer.PackageData.Package.xml' validated with schema 'Microsoft.SQL.Chainer.Package.Package.xsd' has been successfuly loaded into datastore path '/Datastore/Package'
(01) 2017-10-19 02:14:41 Slp: ----------------------------------------------------------------------
(01) 2017-10-19 02:14:41 Slp: Running Action: ReadProductXML
(01) 2017-10-19 02:14:41 Slp: Reading XML resource 'Microsoft.SQL.Chainer.Product.Product.xml'
(01) 2017-10-19 02:14:41 Slp: Document 'Microsoft.SQL.Chainer.Product.Product.xml' validated with schema 'Microsoft.SQL.Chainer.Product.Product.xsd' has been successfuly loaded into datastore path '/Datastore/Product'
(01) 2017-10-19 02:14:41 Slp: Completed Action: ReadProductXML, returned True
(01) 2017-10-19 02:14:41 Slp: ----------------------------------------------------------------------
(01) 2017-10-19 02:14:41 Slp: Running Action: LoadExtensions
(01) 2017-10-19 02:14:42 Slp: Loading extension 'MSI' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.MsiExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'MSI' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'Config' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ConfigExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'Config' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'Common' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Chainer.ExtensionCommon.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'Common' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'SqlConfigBase' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.SqlConfigBase.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'SqlConfigBase' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'Slp' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.SetupExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'Slp' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'RulesEngine' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.RulesEngineExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'RulesEngine' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'WorkflowData' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Chainer.WorkflowData.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'WorkflowData' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'SlpConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.SlpExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'SlpConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'Clst' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.Cluster.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'Clst' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'AgentConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.AgentExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'AgentConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'SqlPowershellConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.PowershellExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'SqlPowershellConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'SSISConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.SSISExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'SSISConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ISMasterConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ISMasterExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ISMasterConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ISWorkerConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ISWorkerExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ISWorkerConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'DReplayConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.DistributedReplayExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'DReplayConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ASConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ASExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ASConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ReplConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.Repl_ConfigExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ReplConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ManagementToolsConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ManagementToolsExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ManagementToolsConfig' version '14.0.1000.169' loaded
(01) 2017-10-19 02:14:42 Slp: Loading extension 'ManagementToolsAdvancedConfig' from file 'C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\.\Microsoft.SqlServer.Configuration.ManagementToolsExtension.dll'
(01) 2017-10-19 02:14:42 Slp: Extension 'ManagementToolsAdvancedConfig' version '14.0.1000.169' loaded


Cumulative Update 3 for SQL Server 2016 SP2 - Issue

$
0
0

https://support.microsoft.com/en-us/help/4458871/cumulative-update-3-for-sql-server-2016-sp2

This page says there's a problem with a fix in this release, but Microsoft doesn't tell us what the issue is or what we should be looking for.  Is there any other documentation that tells where this problem is, what to look for and if we need to back out this CU?   It just went into a couple of my production systems last night.

Can't change UI Language of SQL Server Management Studio 17.1 to English

$
0
0

Hi,

I do have installed the English Version of SQL Server 2016 and SQL Server Management Studio 17.1.  


How can I change the language to English?  As you can see, the DB menu in Object Explorer is in English, but the user interface still is in German.

When I use the link to install other languages. I get a link to http://go.microsoft.com/fwlink/?LinkId=558810&clcid=0x407 

This is completely  wrong, because it redirects me to install a "Microsoft Visual Studio 2015 Sprachpaket" = Language Pack for VS2015.  Why I need to install a Language pack if I installed the English version: "SSMS-Setup-ENU.exe"

I do have Visual Studio 2017 English installed.  

It's very strange.

Regards,

Arash


ODBC Driver 17 for SQL Server not working from MacOS and Ubuntu

$
0
0

Hi guys,

I am getting the following error when trying to connect to my DB from Mac OS and Ubuntu using ODBC Driver 17 for SQL Server. I have tried FreeTDS and it is working. For some reason

cnxn = pyodbc.connect('DSN=TEST_DSN;UID='+username+';PWD='+ password)


pyodbc.InterfaceError: ('28000', "[28000] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Login failed for user 'DOMAIN\USER'. (18456) (SQLDriverConnect)")

I get the same issue when using isql:

isql TEST_DSN DOMAIN\\USER **** -v
[28000][unixODBC][Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Login failed for user 'DOMAIN\USER'.
[ISQL]ERROR: Could not SQLConnect

Here is my configurations:

odbc.ini

[TEST_DSN]
Driver          = ODBC Driver 17 for SQL Server
Server          = MYSERVER
Database        = MYDB
Port            = 1433

odbcinst.ini

[ODBC Driver 17 for SQL Server]
Description=Microsoft ODBC Driver 17 for SQL Server
Driver=/usr/local/lib/libmsodbcsql.17.dylib
UsageCount=1

If I replace the line Driver=/usr/local/lib/libmsodbcsql.17.dylib to point to FreeTDS (Driver=/usr/local/lib/libtdsodbc.so) everything works fine.

Can you please point me to the issue here?

Regards,


Unable to connect to another machines default instance.

$
0
0

Hi ,


I am trying to set-up my own lab for working on some projects which require some testing before implementing any changes.
So i installed two Vm machine (server 2012 ) with Sql server 2016  and tried to connect sql instance of other 2nd machine from machine 1 and vice versa.
Before posting this here , i checked several articles and forum but nothing really helped .

I have already followed below steps:

1.Checked if services is up(SQL + browser).
2.Checked if Sql remote connected is allowed.
3.1433 and 1434 are listening.
4.Named pipeline and TCP\IP is enabled.
5.Added the ports 1434 and 1433 on firewall.
6.Added sql server and sql browser on firewall exception.
7.Disabled the firewall.
8.As both machines have same ip ,i pinged the IPv6 (one's ip on other machine)it gave the destination host unreachable.(i believe here is the culprit but unable to resolve )
Ran command [netsh interface ipv6 show neighbors] on machines and it showed the ipv6 of other machine.


It gave me the hint that there is problem with ipv6 but i am unable to resolve it
9.Using the correct machine name as the instance is default and used the instance name too to connect. 
10.Restarted the machine after making changes.
11. Checked sql default port (it is 1433).
12.Tried windows and sql authentication both to establish connection.

Below is the error that i see while connecting to others machine instance.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)
------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=67&LinkId=20476

------------------------------
Error Number: 67
Severity: 20
State: 0
The network name cannot be found.

I am not getting much on Error Number: 67.Any help on this will be appreciated.


Regards



Windows Update Failed

$
0
0

I had bunch of updates for my windows update, everything else updated but one update keeps failing.

Microsoft SQL Server 2008 Service Pack 4 (KB2979596)

I get the following error

Error(s) found;

Code 84B30002 Windows Update encountered and unknown error.

I tried looking online error for that help but couldn't find it. Please help

Viewing all 7701 articles
Browse latest View live


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