Retiring a server w/sql 2008 r2. New will have sql 2017. MS tells me the cals in the 2008 sql are "not compatible", even if I buy the 2017 edition that uses cals rather than cores. They're just licenses for Pete's sake. Seems like straight up "we just want more money". makes as much sense as saying if I buy a new car I'd have to abandon my driveway and build a new one. Anybody know of any real reason other than just to get more money?
↧
wanting to move sql cals 2008 to 2017
↧
Configure SQL Server 2017 Dev edition behave like Standard one
Hi
We need to have testing/dev environment to behave exactly like production one.
Is it possible to configure SQL Server 2017 dev edition to behave like Standard one? (in terms of cpu/threads usage etc)
Thank you
↧
↧
SS Express - grant other users access
I am a BI person so I can use a DB, but setting up and configuring - not so much (last time I created a DB was DB2 UDB on NT). I'm learning but looking for aquick start if anyone can help:
I have SS 2017 Express installed on a machine on my network. I need to grant other users on the same domain access to this instance. What is the quickest way to configure this?
Thanks.
↧
SQL SERVER (MSSQLSERVER) service does not start after CU14 for SQL Server 2016 SP1
Hello,
I have recently installed the CU14 for SQL Server 2016 SP1 from the following URL:
https://support.microsoft.com/en-us/help/3177312/sql-server-2016-build-versions
However, the update was installed with some errors, due to which it was observed that the MSSQLSERVER service could not be started. As a result, I decided to uninstall the update from Control Panel. The update could be uninstalled successfully and the MSSQLSERVER service became functional as before. In order to attain surety of my action, I considered reinstalling the update, but got the same results - inability to start the SQL Serer (MSSQLSERVER) service. This time, the update could not be uninstalled completely even on several attempts, and my SQL Server service remains dysfunctional. A zipped file of the logs of all the actions can be accessed here:
https://drive.google.com/open?id=1j4SLaFEVal-1ths4TC3Q_KBBCslbeVtQ
Kindly help me get my SQL Server service up and running at the earliest.
Thank you.
↧
Can't change UI Language of SQL Server Management Studio 17.1 to English
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
↧
↧
SQL Server Installation on Local PC per Client
Hello, I have a POS Application with MS SQL Server back end. We have a client that usually having problem with internet, mostly those on remote areas, their main server is on Sydney, and their sub branches are on the remote areas of Australia where the internet really is bad, and currently, when this happens, their operation will be very messy because they will sell manually (by paper invoices, receipts, etc)
I want to design a countermeasure for this by creating a Local POS which use Local Database, (per client PC), and sync the data when its online again, (or stay to connect locally if they want to but the end of the day, it will be synced to the main database). My question is, by this setup, will there be any issues with the MS SQL License?
Thank you
↧
Microsoft SQL 2017 Std
I have bought the license for SQL 2017 STD and want to downgrade same on SQL 2016 Std. please share the link from where i can download the correct media file.
↧
can I skip SP2, SP3 and install SP4?
Does the order in which fixes are installed matter?
Can you skip the Service Pack?
SQL Server 2012 SP1 can I skip SP2, SP3 and install SP4?
greetings
↧
SSMS 18 fails to install
Hi,
When trying to install SSMS 18 English version, the installation stops at once with "SSMS can only be upgraded by installing the package of the matching language".
At the same time SSMS 17.9.1 English version is installed with no problem.
How do i install SSMS 18?
↧
↧
Unable to install SQL Server (setup.exe). Exit code (Decimal): -2068119551
I've never installed server software before, so maybe I'm doing something wrong. I've tried to install the SQL Server 2017 without admin privileges and with them, to no avail. Can you help me?
↧
SQL Server 2016 (Enterprise Edition) SP2/CU6 Fails
SQL Server 2016 (Enterprise Edition) SP2/CU6 Install Failed. Error Code: 1642
Installation Succeeded On:
Full Test and Semantic Extractions for Search, R Services(In-Database),
SQL Server Replication, Database Engine Services
Installation Failed On:
Distributed Replay Controller, Integration Services, Reporting Services(SharePoint),
Reporting Services(Native), Analysis Services
Log File Error Message:
=== Verbose logging started: 4/28/2019 6:24:31 Build type: SHIP UNICODE 5.00.9600.00 Calling process: E:\6f6103bd891bf837eb82d10da71fb538\x64\ScenarioEngine.exe ===MSI (c) (CC:7C) [06:24:31:735]: Resetting cached policy values
MSI (c) (CC:7C) [06:24:31:735]: Machine policy value 'Debug' is 0
MSI (c) (CC:7C) [06:24:31:735]: ******* RunEngine:
******* Product: {57846DA8-8B5D-4466-B850-E8CDFC94046C}
******* Action:
******* CommandLine: **********
MSI (c) (CC:7C) [06:24:31:735]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (CC:7C) [06:24:31:735]: Grabbed execution mutex.
MSI (c) (CC:7C) [06:24:31:735]: Cloaking enabled.
MSI (c) (CC:7C) [06:24:31:735]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (CC:7C) [06:24:31:735]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (2C:4C) [06:24:31:735]: Running installation inside multi-package transaction {57846DA8-8B5D-4466-B850-E8CDFC94046C}
MSI (s) (2C:4C) [06:24:31:735]: Grabbed execution mutex.
MSI (s) (2C:30) [06:24:31:735]: Resetting cached policy values
MSI (s) (2C:30) [06:24:31:735]: Machine policy value 'Debug' is 0
MSI (s) (2C:30) [06:24:31:735]: ******* RunEngine:
******* Product: {57846DA8-8B5D-4466-B850-E8CDFC94046C}
******* Action:
******* CommandLine: **********
MSI (s) (2C:30) [06:24:31:735]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (2C:30) [06:24:31:735]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
MSI (s) (2C:30) [06:24:31:735]: SRSetRestorePoint skipped for this transaction.
MSI (s) (2C:30) [06:24:31:735]: End dialog not enabled
MSI (s) (2C:30) [06:24:31:735]: Original package ==> C:\Windows\Installer\1842ef5.msi
MSI (s) (2C:30) [06:24:31:735]: Package we're running from ==> C:\Windows\Installer\1842ef5.msi
MSI (s) (2C:30) [06:24:31:735]: APPCOMPAT: Uninstall Flags override found.
MSI (s) (2C:30) [06:24:31:735]: APPCOMPAT: Uninstall VersionNT override found.
MSI (s) (2C:30) [06:24:31:735]: APPCOMPAT: Uninstall ServicePackLevel override found.
MSI (s) (2C:30) [06:24:31:735]: APPCOMPAT: looking for appcompat database entry with ProductCode '{57846DA8-8B5D-4466-B850-E8CDFC94046C}'.
MSI (s) (2C:30) [06:24:31:735]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (2C:30) [06:24:31:751]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
MSI (s) (2C:30) [06:24:31:751]: File will have security applied from OpCode.
MSI (s) (2C:30) [06:24:31:751]: Original patch ==> E:\6f6103bd891bf837eb82d10da71fb538\x64\setup\sql_common_core_msi\sql_common_core.msp
MSI (s) (2C:30) [06:24:31:751]: Patch we're running from ==> C:\Windows\Installer\49e70.msp
MSI (s) (2C:30) [06:24:31:751]: Opening existing patch 'C:\Windows\Installer\89322.msp'.
MSI (s) (2C:30) [06:24:31:751]: SequencePatches starts. Product code: {57846DA8-8B5D-4466-B850-E8CDFC94046C}, Product version: 13.0.1601.5, Upgrade code: {F2F6463E-EE2A-4C0B-B399-F550C887354A}, Product language 1033
MSI (s) (2C:30) [06:24:31:751]: PATCH SEQUENCER: verifying the applicability of QFE patch E:\6f6103bd891bf837eb82d10da71fb538\x64\setup\sql_common_core_msi\sql_common_core.msp against product code: {57846DA8-8B5D-4466-B850-E8CDFC94046C},
product version: 13.0.1601.5, product language 1033 and upgrade code: {F2F6463E-EE2A-4C0B-B399-F550C887354A}
MSI (s) (2C:30) [06:24:31:751]: PATCH SEQUENCER: QFE patch E:\6f6103bd891bf837eb82d10da71fb538\x64\setup\sql_common_core_msi\sql_common_core.msp is not applicable.
MSI (s) (2C:30) [06:24:31:751]: SequencePatches returns success.
MSI (s) (2C:30) [06:24:31:751]: Final Patch Application Order:
MSI (s) (2C:30) [06:24:31:751]: Other Patches:
MSI (s) (2C:30) [06:24:31:751]: Unknown\Absent: {D20E0888-BDCC-40E9-8EA7-3293D389DCC0} - E:\6f6103bd891bf837eb82d10da71fb538\x64\setup\sql_common_core_msi\sql_common_core.msp
MSI (s) (2C:30) [06:24:31:751]: Product: SQL Server 2016 Common Files - Update '{D20E0888-BDCC-40E9-8EA7-3293D389DCC0}' could not be installed. Error code 1642.
Additional information is available in the log file C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20190428_062233\MSSQLSERVER\sql_common_core_Cpu64_1.log.
MSI (s) (2C:30) [06:24:31:751]: Windows Installer installed an update. Product Name: SQL Server 2016 Common Files. Product Version: 13.0.1601.5. Product Language: 1033. Manufacturer: Microsoft Corporation.
Update Name: {D20E0888-BDCC-40E9-8EA7-3293D389DCC0}. Installation success or error status: 1642.
MSI (s) (2C:30) [06:24:31:751]: Note: 1: 1708
MSI (s) (2C:30) [06:24:31:751]: Product: SQL Server 2016 Common Files -- Installation failed.
MSI (s) (2C:30) [06:24:31:751]: Windows Installer installed the product. Product Name: SQL Server 2016 Common Files. Product Version: 13.0.1601.5. Product Language: 1033. Manufacturer: Microsoft Corporation.
Installation success or error status: 1642.
MSI (s) (2C:30) [06:24:31:751]: Attempting to delete file C:\Windows\Installer\49e70.msp
MSI (s) (2C:30) [06:24:31:751]: MainEngineThread is returning 1642
MSI (s) (2C:4C) [06:24:31:751]: No System Restore sequence number for this installation.
The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists
on your computer and that you have the correct upgrade.
C:\Windows\Installer\1842ef5.msi
MSI (s) (2C:4C) [06:24:31:751]: User policy value 'DisableRollback' is 0
MSI (s) (2C:4C) [06:24:31:751]: Machine policy value 'DisableRollback' is 0
MSI (s) (2C:4C) [06:24:31:751]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (2C:4C) [06:24:31:751]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (2C:4C) [06:24:31:751]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (2C:4C) [06:24:31:751]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (CC:7C) [06:24:31:751]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (CC:7C) [06:24:31:751]: MainEngineThread is returning 1642
=== Verbose logging stopped: 4/28/2019 6:24:31 ===
↧
SQL Server 2016 (Enterprise Edition) SP2/CU6 Fails
SQL Server 2016 (Enterprise Edition) SP2/CU6 Fails (SQl is installed on windows server 2012R2)
I am currently on SP2/CU4 and was attempting to upgrade to SP2/CU6 but it Fails
Installation Failed On:
- Distributed Replay Controller - Integration Services - Reporting Services-SharePoint
- Reporting Services - Native - Analysis Services
Installation Succeeded On:
- DataBase Engine Services - SQL Server Replication
- R Services - Full-Text and Semantic Extractions for Search
Log File Error Message:
=== Verbose logging started: 4/28/2019 6:24:31 Build type: SHIP UNICODE 5.00.9600.00 Calling process: E:\6f6103bd891bf837eb82d10da71fb538\x64\ScenarioEngine.exe ===MSI (c) (CC:7C) [06:24:31:735]: Resetting cached policy values
MSI (c) (CC:7C) [06:24:31:735]: Machine policy value 'Debug' is 0
MSI (c) (CC:7C) [06:24:31:735]: ******* RunEngine:
******* Product: {57846DA8-8B5D-4466-B850-E8CDFC94046C}
******* Action:
******* CommandLine: **********
MSI (c) (CC:7C) [06:24:31:735]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (CC:7C) [06:24:31:735]: Grabbed execution mutex.
MSI (c) (CC:7C) [06:24:31:735]: Cloaking enabled.
MSI (c) (CC:7C) [06:24:31:735]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (CC:7C) [06:24:31:735]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (2C:4C) [06:24:31:735]: Running installation inside multi-package transaction {57846DA8-8B5D-4466-B850-E8CDFC94046C}
MSI (s) (2C:4C) [06:24:31:735]: Grabbed execution mutex.
MSI (s) (2C:30) [06:24:31:735]: Resetting cached policy values
MSI (s) (2C:30) [06:24:31:735]: Machine policy value 'Debug' is 0
MSI (s) (2C:30) [06:24:31:735]: ******* RunEngine:
******* Product: {57846DA8-8B5D-4466-B850-E8CDFC94046C}
******* Action:
******* CommandLine: **********
MSI (s) (2C:30) [06:24:31:735]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (2C:30) [06:24:31:735]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
MSI (s) (2C:30) [06:24:31:735]: SRSetRestorePoint skipped for this transaction.
MSI (s) (2C:30) [06:24:31:735]: End dialog not enabled
MSI (s) (2C:30) [06:24:31:735]: Original package ==> C:\Windows\Installer\1842ef5.msi
MSI (s) (2C:30) [06:24:31:735]: Package we're running from ==> C:\Windows\Installer\1842ef5.msi
MSI (s) (2C:30) [06:24:31:735]: APPCOMPAT: Uninstall Flags override found.
MSI (s) (2C:30) [06:24:31:735]: APPCOMPAT: Uninstall VersionNT override found.
MSI (s) (2C:30) [06:24:31:735]: APPCOMPAT: Uninstall ServicePackLevel override found.
MSI (s) (2C:30) [06:24:31:735]: APPCOMPAT: looking for appcompat database entry with ProductCode '{57846DA8-8B5D-4466-B850-E8CDFC94046C}'.
MSI (s) (2C:30) [06:24:31:735]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (2C:30) [06:24:31:751]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
MSI (s) (2C:30) [06:24:31:751]: File will have security applied from OpCode.
MSI (s) (2C:30) [06:24:31:751]: Original patch ==> E:\6f6103bd891bf837eb82d10da71fb538\x64\setup\sql_common_core_msi\sql_common_core.msp
MSI (s) (2C:30) [06:24:31:751]: Patch we're running from ==> C:\Windows\Installer\49e70.msp
MSI (s) (2C:30) [06:24:31:751]: Opening existing patch 'C:\Windows\Installer\89322.msp'.
MSI (s) (2C:30) [06:24:31:751]: SequencePatches starts. Product code: {57846DA8-8B5D-4466-B850-E8CDFC94046C}, Product version: 13.0.1601.5, Upgrade code: {F2F6463E-EE2A-4C0B-B399-F550C887354A}, Product language 1033
MSI (s) (2C:30) [06:24:31:751]: PATCH SEQUENCER: verifying the applicability of QFE patch E:\6f6103bd891bf837eb82d10da71fb538\x64\setup\sql_common_core_msi\sql_common_core.msp against product code: {57846DA8-8B5D-4466-B850-E8CDFC94046C},
product version: 13.0.1601.5, product language 1033 and upgrade code: {F2F6463E-EE2A-4C0B-B399-F550C887354A}
MSI (s) (2C:30) [06:24:31:751]: PATCH SEQUENCER: QFE patch E:\6f6103bd891bf837eb82d10da71fb538\x64\setup\sql_common_core_msi\sql_common_core.msp is not applicable.
MSI (s) (2C:30) [06:24:31:751]: SequencePatches returns success.
MSI (s) (2C:30) [06:24:31:751]: Final Patch Application Order:
MSI (s) (2C:30) [06:24:31:751]: Other Patches:
MSI (s) (2C:30) [06:24:31:751]: Unknown\Absent: {D20E0888-BDCC-40E9-8EA7-3293D389DCC0} - E:\6f6103bd891bf837eb82d10da71fb538\x64\setup\sql_common_core_msi\sql_common_core.msp
MSI (s) (2C:30) [06:24:31:751]: Product: SQL Server 2016 Common Files - Update '{D20E0888-BDCC-40E9-8EA7-3293D389DCC0}' could not be installed. Error code 1642.
Additional information is available in the log file C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20190428_062233\MSSQLSERVER\sql_common_core_Cpu64_1.log.
MSI (s) (2C:30) [06:24:31:751]: Windows Installer installed an update. Product Name: SQL Server 2016 Common Files. Product Version: 13.0.1601.5. Product Language: 1033. Manufacturer: Microsoft Corporation.
Update Name: {D20E0888-BDCC-40E9-8EA7-3293D389DCC0}. Installation success or error status: 1642.
MSI (s) (2C:30) [06:24:31:751]: Note: 1: 1708
MSI (s) (2C:30) [06:24:31:751]: Product: SQL Server 2016 Common Files -- Installation failed.
MSI (s) (2C:30) [06:24:31:751]: Windows Installer installed the product. Product Name: SQL Server 2016 Common Files. Product Version: 13.0.1601.5. Product Language: 1033. Manufacturer: Microsoft Corporation.
Installation success or error status: 1642.
MSI (s) (2C:30) [06:24:31:751]: Attempting to delete file C:\Windows\Installer\49e70.msp
MSI (s) (2C:30) [06:24:31:751]: MainEngineThread is returning 1642
MSI (s) (2C:4C) [06:24:31:751]: No System Restore sequence number for this installation.
The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists
on your computer and that you have the correct upgrade.
C:\Windows\Installer\1842ef5.msi
MSI (s) (2C:4C) [06:24:31:751]: User policy value 'DisableRollback' is 0
MSI (s) (2C:4C) [06:24:31:751]: Machine policy value 'DisableRollback' is 0
MSI (s) (2C:4C) [06:24:31:751]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (2C:4C) [06:24:31:751]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (2C:4C) [06:24:31:751]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (2C:4C) [06:24:31:751]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (CC:7C) [06:24:31:751]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (CC:7C) [06:24:31:751]: MainEngineThread is returning 1642
=== Verbose logging stopped: 4/28/2019 6:24:31 ===
↧
Creating database object list
Hi. I am DBA of SQL Server 2014. I am working on creating documents that show list of table, view, function, and stored procedure under specific schema on user database. I am looking for easy way to list them up such as
running query etc. Any advice will be gratefully appreciated.
↧
↧
SQL License Quary.
we have purchase SQL 2014 two license for 4 core server.Kindly confirm that we download the SQL 2014 enterprises per core software from VLSC portal.it will cover all 4 core for server hardware.or we required to follow any other step for cover the 4 core server hardware.
Kindly confirm thatSQL Server 2014 Enterprise Edition – Per Core . when downloaded and install will cover all 4 core for server hardware.
↧
[SOLVED] A MOF syntax error occured, installing SQL Server 2012 Advanced Express 64 bit edition
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.
↧
SQL Server service models - GDR and CU branches
Referencing KB articles 4047327 and 935897:
I recently applied SQL Server 2016 SP2 and CU6 and I understand that it is necessary to manually apply a CU to a baseline in order for future CU's to become applicable... But it is unclear whether or not I will have to manually install SP3 and its first CU when that comes out if I want to once again be on the CU branch of the service model for that baseline...
Will SP3 be automatically applicable when released and reset me to the GDR baseline or will I have to manually reset the baseline once it is released since I am now on the CU branch of the servicing model....
↧
Looking for sql 2019 odbc and mssql-tool rpm binaries.
Hi All,
I am installing sql server 2019offline on Red hat Linux 7.5.I am looking for .rpm files for odbc and mssql-too fro sql 2019.But,after searching a lot in google, I can see only the below are the latest files which are available currently as per https://packages.microsoft.com/rhel/7.3/prod/.
mssql-tools-17.3.0.1-1.x86_64.rpm
msodbcsql17-17.3.1.1-1.x86_64.rpm
Can some one help me if mssql-tools are released for new version and please provide the location for downloading the same.
Your help would be appreciated.
↧
↧
Page file confusion
Page file confusion
I’m planning to create couple of virtual machines based on Windows Server 2019 (host Windows Serer 2012 R2). One of main will be MS SQL with 128GB RAM – it will be replicated to second site using Hyper-V Replica.
For few hours I’m trying to find advise how to correctly configure page file on the VM (host is clear – just leave it as automatic), and found many contradicting answers. Perhaps somebody can advise something. I found following:
- Disable completely page file as you have enough RAM and you don’t need it
- Set page file as 1.5xRAM, even if it is huge
- Set page file as 1.5x(Total machine RAM – RAM allocated for SQL)
- Set page file as automatic
- Place page file on OS drive as it won’t be used to much so it can be replicated without any issues.
- Place page file on dedicated drive to make sure it won’t se much bandwidth during replication.
All arguments which I read about above are reasonable but I have no idea what really should I chose.
↧
SQL Server Management Studio 18, interface broken
Hello, im having the next problem with SSMS v18, i installed and it works but when i make a select or do anything, the UI brokes and then everything loks like this:
Does enyone have any solution???
Ing. Irwin Romero Rodriguez.
↧
Failed setup installation in database engine service and other services sql server 2017
I just trying to install sql server 2017 and i getting failed installing Database Engine and SQL Server Replication, this is the summary log:
Overall summary:Final result: Failed: see details below
Exit code (Decimal): -2068052377
Start time: 2019-05-03 23:30:24
End time: 2019-05-03 23:35:36
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.
Machine Properties:
Machine name: EVVNNXX
Machine processor count: 4
OS version: Microsoft Windows 10 Home Single Language (10.0.17134)
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered Configured
Package properties:
Description: Microsoft SQL Server 2017
ProductName: SQL Server 2017
Type: RTM
Version: 14
SPLevel: 0
Installation location: C:\SQLServer2017Media\Express_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: TABULAR
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTELSVCACCT: <empty>
ASTELSVCPASSWORD: <empty>
ASTELSVCSTARTUPTYPE: 0
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
EXTSVCACCOUNT: <empty>
EXTSVCPASSWORD: <empty>
FEATURES: SQLENGINE, REPLICATION
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTPYTHONLICENSETERMS: false
IACCEPTROPENLICENSETERMS: 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
ISMASTERSVCACCOUNT: NT AUTHORITY\Network Service
ISMASTERSVCPASSWORD: <empty>
ISMASTERSVCPORT: 8391
ISMASTERSVCSSLCERTCN: <empty>
ISMASTERSVCSTARTUPTYPE: Automatic
ISMASTERSVCTHUMBPRINT: <empty>
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
ISTELSVCACCT: <empty>
ISTELSVCPASSWORD: <empty>
ISTELSVCSTARTUPTYPE: 0
ISWORKERSVCACCOUNT: NT AUTHORITY\Network Service
ISWORKERSVCCERT: <empty>
ISWORKERSVCMASTER: <empty>
ISWORKERSVCPASSWORD: <empty>
ISWORKERSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
MRCACHEDIRECTORY:
NPENABLED: 0
PBDMSSVCACCOUNT: <empty>
PBDMSSVCPASSWORD: <empty>
PBDMSSVCSTARTUPTYPE: 0
PBENGSVCACCOUNT: <empty>
PBENGSVCPASSWORD: <empty>
PBENGSVCSTARTUPTYPE: 0
PBPORTRANGE: <empty>
PBSCALEOUT: false
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$SQLEXPRESS
SQLSVCINSTANTFILEINIT: true
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: EVVNNXX\ASUS
SQLTELSVCACCT: NT Service\SQLTELEMETRY$SQLEXPRESS
SQLTELSVCPASSWORD: <empty>
SQLTELSVCSTARTUPTYPE: Automatic
SQLTEMPDBDIR: <empty>
SQLTEMPDBFILECOUNT: 1
SQLTEMPDBFILEGROWTH: 64
SQLTEMPDBFILESIZE: 8
SQLTEMPDBLOGDIR: <empty>
SQLTEMPDBLOGFILEGROWTH: 64
SQLTEMPDBLOGFILESIZE: 8
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SUPPRESSPRIVACYSTATEMENTNOTICE: false
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
USEMICROSOFTUPDATE: false
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190503_233023\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed
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 Database Engine Services Instance Features
Component error code: 1639
Component log file: C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190503_233023\sql_engine_core_inst_Cpu64_1.log
Error description: Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
Error help link: https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=sql_engine_core_inst.msi%400x162A16FE%400x1639
Feature: SQL Server Replication
Status: Failed
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 Database Engine Services Instance Features
Component error code: 1639
Component log file: C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190503_233023\sql_engine_core_inst_Cpu64_1.log
Error description: Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
Error help link: https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=sql_engine_core_inst.msi%400x162A16FE%400x1639
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190503_233023\SystemConfigurationCheck_Report.htm
↧