Lỗi edition wow64 platform failed sql server 2023 năm 2024

We have 2 node sql cluster with standard editon so how do we upgrade from standard to enterprise edtion.

↧

↧

Unable to install SP3 for SQL Server 2012

December 8, 2016, 4:08 am

We've a set of Azure SQL Server 2012 R2 Datacenter 64-bit edition VMs in cluster already with SP2 (KB2958429). However, while trying to install SP3 (KB3072779), the installation wizard standstill during stopping of MSSQLSERVER services and closes, from Setup Bootstrap Logs, here is the error information:

Overall summary: Final result: The patch installer has failed to update the following instance: MSSQLSERVER. To determine the reason for failure, review the log files. Exit code (Decimal): -2068709375 Start time: 2016-12-08 11:36:48 End time: 2016-12-08 11:40:05 Requested action: Patch

Instance MSSQLSERVER overall summary: Final result: The patch installer has failed to update the shared features. To determine the reason for failure, review the log files. Exit code (Decimal): -2068709375 Exit facility code: 1202 Exit error code: 1 Exit message: The NT service 'MSSQLSERVER' could not be stopped. Start time: 2016-12-08 11:37:56 End time: 2016-12-08 11:40:02 Requested action: Patch

And here is the error information available from Detail.txt from this location: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20161208_113558

(01) 2016-12-08 11:37:56 Slp: The following NT service was in a running state prior to patch action: ReportServer (01) 2016-12-08 11:37:56 Slp: Attempting to run patch request for instance: MSSQLSERVER (01) 2016-12-08 11:40:04 Slp: Error: Failed to run patch request for instance: MSSQLSERVER (exit code: -2068709375)

↧

Microsoft Server Licensing Question

December 10, 2016, 6:57 am

I have a app internal created in ASPx and another in PHP.

Both run on IIS under Windows 2012 and accessing a SQL Server.

Do we need to license to all users who have access to apps (SQL cals)?.

Login/user is performed on a screen to access a local SQL table, is not Active Directory authentication.

Only enter the user in IIS, right?

Thanks!

↧

SQL Server Developer Edition

December 11, 2016, 2:17 pm

Hi Experts,

What I understand is that SQL Server developer edition 2014 and 2016 is free of cost from 1st April 2016. In this case if I do a side by side upgrade of an existing environment or build a new environment for Developer 2014 and 2016, I will not be requiring a license for it.

Thanks

↧

SQL Server 2016 install fails.

December 11, 2016, 1:39 am

I have been trying to install the developer edition of SQL Server 2016 and I get the generic error (below - see logs). Interesting I had the same issue on this same laptop (ACER Aspire R3-471TG) with RC2 of SQL Server 2016, however RC3 installed without issue. I did post about this RC2 issue (see https://social.msdn.microsoft.com/Forums/sqlserver/en-US/73f84ce8-7c69-41e1-832c-8a5828dd0fd7/rc2-install-errors?forum=SQLServer2016Preview).

I have found some stuff on account privileges which has a similar error, but this is not the error in this case.

FYI - I have tried installing maybe 6 times today with different settings and running as admin as well. A generic MS response I suggest would not be helpful. Please note RC3 was running without issue up until yesterday.

Feature: Database Engine Services 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, uninstall this feature, and then run the setup process again. Component name: SQL Server Database Engine Services Instance Features Component error code: -2147467261 Error description: Object reference not set to an instance of an object.

Looking at the detailed logs I get

(01) 2016-12-11 19:10:56 Slp: Sco: Attempting to dispose script (01) 2016-12-11 19:10:56 Slp: Sco: Attempting to disconnect script (01) 2016-12-11 19:10:56 Slp: Current SqlServer Connection closed... (01) 2016-12-11 19:10:56 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC. (01) 2016-12-11 19:10:56 Slp: Object reference not set to an instance of an object. (01) 2016-12-11 19:10:56 Slp: The configuration failure category of current exception is ConfigurationFailure (01) 2016-12-11 19:10:56 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC.

↧

↧

What is the best practice for CPU usage for SQL Server?

December 12, 2016, 12:41 am

We migerate to a new server for our SQL Servers. We are using SQL 2012 SP 3.

What should be the goal for the average usage of CPU?

↧

Can we install Microsoft SQL Server 2016 Evaluation on Windows 8/8.1 ?

December 12, 2016, 1:08 am

Can we install Microsoft SQL Server 2016 Evaluation on Windows 8/8.1 ?

Already checked it @ https://msdn.microsoft.com/en-in/library/ms143506.aspx, but no information available for Evaluation Version.

Shashank Verma

↧

Installation of SQL Server 2014 on Windows 10

December 12, 2016, 5:30 am

I am using Windows 10 Anniversary edition and when I go to install sql server 2014 windows asks if I want to install the program, I say yes, and I get a brief flash of a window, then nothing.

.net framework 3.5 and 4.6 are both installed on this computer. Why won't the program install?

↧

Upgrade from SQL Server 2005 SP4 to SQL Server 2008 R2 SP3 fails

December 12, 2016, 8:39 am

Tried to do an in-place upgrade as above on a production server on 12/3/2016 with a slipstreamed 2008 R2 Standard installer, but only the Setup support and SQL Writer were updated. A similar upgrade on a test server on 11/17/2016 with the same installer worked flawlessly and upgraded all features. Both servers only have/had a single default instance of SQL Server 2005.

From what I can decipher from the logs for each attempt, it appears the production server upgrade did not have an instance id specified in the generated configuration file when it got to the rules evaluation, even though it appears to have detected all of the installed components and the existing instance correctly. The upgrade screen on the production server also only presented a grayed out incomplete Feature List.

Would appreciate any feedback on what caused this, and how I can get the upgrade on the production server to process correctly.

↧

↧

Column Level Encryption in sql server 2014 ( not in sql 2016 please)

December 13, 2016, 1:51 am

Hi Team,

Can some one help me to understand that is column level encryption available in sql server 2014 ( i know it is there in sql 2016) , IF so can you please share me the best link to understand how to perform column level encryption in sql 2014 .

awaiting for your reply

thank you

hemadri

↧

SQL Server was unable to communicate with the LaunchPad service

December 13, 2016, 11:35 am

I am unable to run R scripts in SQL Server 2016 Service Pack 1 on Windows 10.

When I run:

exec sp_execute_external_script @language =N'R', @script=N'OutputDataSet<-InputDataSet', @input_data_1 =N'select 1 as hello' with result sets (([hello] int not null)); go

I get the message

Msg 39011, Level 16, State 1, Line 1 SQL Server was unable to communicate with the LaunchPad service. Please verify the configuration of the service. Msg 11536, Level 16, State 1, Line 1 EXECUTE statement failed because its WITH RESULT SETS clause specified 1 result set(s), but the statement only sent 0 result set(s) at run time.

Both Windows Services and SQL Server Configuration Manager report that Launchpad is running.

"Exec sp_configure 'external scripts enabled'" reports 1

The SQLRUserGroup has log-on privileges.

John Kane

↧

Extract MSI for SQL Server Management Studio 2016 (v16.5)

November 8, 2016, 3:10 pm

Does anyone know how to extract the MSI file from the latest version of the SQL Server Management Studio, version 16.5? I like to use that file as the detection method when building an Application on SCCM. The built-in "layout" command doesn't extract the files like I was expecting:

SSMS-Setup-ENU.exe /Layout C:\Temp

↧

SQL Server 2000\2005 compatibility with Active Directory 2012

September 8, 2014, 3:05 pm

Hi All,

We are currently using Active Directory 2003 and will be upgrading to AD 2012. I'm trying to determine if there is any known compatibility issues when running older versions of SQL Server (2000 and 2005) when upgrading to AD 2012. I've read forums from when others went from AD 2003 to AD 2008 and didn't experience any issues. We have the newer versions of SQL but I'm not too concerned about these. Any advice would be greatly appreciated? Has anyone been through this process.

Thanks,

↧

↧

While installing SQL Server 2014, in the Global Rules I get Edition WOW64 platform - failed

December 14, 2016, 6:03 pm

While installing SQL Server 2014, in the Global Rules I get Edition WOW64 platform - failed.

Text from Detail file is "Slp: Current 32 bit setup package does not contain 64 bit MSIs, Marking check for WOW Supported32bitSetup as failed"

I tried running set up from extracted folder as administrator still it did not work.

I am using windows 7 O/S. MySql is also installed - can that be the cause?

Please suggest solution.

↧

MS SQL Server 2016 Install/Change

December 14, 2016, 11:30 am

I have tried to install versions of MS SQL Server (2012 and also 2016) and they all fail with the same error - cannot find/open database handle. I would like to uninstall all these failed installations and try again from a clean slate. I would also like to uninstall VS 2013 as I only use VS 2015. No matter what I try nothing will uninstall. I am using VS 2015 - are there links to VS2015 that are stopping these other products uninstalling or installing correctly. Many other people seem to have the same problem. The processes outlined in the various threads on the subject are so intricate that I can see why they don't work. There should be some sort of "clean up" program/wizard.

Regards

JDR

↧

Change in compatibility level from 90 to 110 leading to excessive blocking

December 14, 2016, 11:55 pm

Hi,

We have a machine running on Windows Server 2008 R2 64-bit Standard Edition SP1. On it we have aSQL Server 2008 R2 Standard Edition SP3 instance. This instance has a database running with compatibility level 90. to upgrade the database, we installed another instance ofSQL Server 2012 Standard Edition SP3. We then restored the database backup from 2008R2 to 2012 instance and change the compatibility level to 110. This led to excessive blocking even in testing phase. When the compatibility was changed back to 90, issue got resolved. Please advice with possible reason and workaround as we need to change it to 110.

Thanks in advance.

↧

SQL2k16

December 15, 2016, 7:13 am

Hi there,

I'd like to raise a VM with a version of SQL2k16 different of this one:

Microsoft SQL Server 2016 (RTM-GDR) (KB3194716) - 13.0.1722.0 (X64) Sep 26 2016 13:17:23 Copyright (c) Microsoft Corporation Enterprise Evaluation Edition (64-bit) on Windows 10 Pro 6.3 <X64> (Build 14393: )

if possible can you share the link with me?

Thanks in advance for your comments

↧

↧

SQL CAL requirements

December 15, 2016, 10:21 am

Can you please help me with the below customer question!!

Do we need SQL CALs when used as a Databse for Biztalk setup ?

In this scenario the SQL will only be used to have BizTalk working as “sql technology”. There will be no data transferred from the sql out to the users/devices.

So for this SQL installation (which only supports to have the biz talk working) will it be enough to only have SQL server license (not SQL Core)?

We believe its a ase of multiplexing and will still require CALs. Can you please confirm

↧

Slipstream CU1 in SQL 2014SP1

July 1, 2015, 8:37 am

Hello,

Trying to slipstream CU1 to SQL2014SP1 (enterprise iso downloaded from microsoft). Files were extracted from iso and copied to UNC share. SQLServer2014-KB3067839-x64.exe downloaded and copied into "Updates" folder within the main folder of the same UNC path.

Started

Setup.exe /ACTION=Install /UPDATEENABLED=TRUE /UPDATESOURCE=UNCPath\Updates

Used the gui to setup configurationfile.ini file

edited the ini file to comment UIMODE

Notes:

UpdateEnabled is set to True in the ini file as well as the source points to UNC path

FEATURES=SQLENGINE,CONN,SSMS,ADV_SSMS

created cmd file:

@echo off @if [%1]==[] (SET /P sqlpwd=Enter service account password:) ELSE (SET sqlpwd=%1) @if [%2]==[] (SET /P sapwd=Enter sa password:) ELSE (SET sapwd=%2)

%~dp0Setup.exe /ACTION=Install /CONFIGURATIONFILE=%~dp0ConfigurationFileVDI.INI /SQLSVCPASSWORD="%sqlpwd%" /AGTSVCPASSWORD="%sqlpwd%" /SAPWD=%sapwd% /QS /IACCEPTSQLSERVERLICENSETERMS

Tried many different combinations, changing action to upgrade, copying sources locally instead of UNC path, run as administrator, specifying options on the command line instead of the ini file and they all failed with the same error 1642. The same batch file succeeds as soon as updateenabled is changed to false but the instance is SP1 not CU1. Using the GUI also fails with the same error when updateenabled is selected

Work around is to deploy the CU1 as next step in the batch file:

%~dp0Updates\SQLServer2014-KB3067839-x64.exe /ACTION=PATCH /ALLINSTANCES /IACCEPTSQLSERVERLICENSETERMS /QUIETSIMPLE

This works just fine, but I was trying to create a source where future updates can be copied to Updates share when approved. Any help or direction would be appreciated.

Errors reported in bootstrap log:

Final result: Failed: see details below Exit code (Decimal): -2068052374

Requested action: Install

....

Product Updates Selected for Installation: Title: Microsoft SQL Server 2014 with SP1 Knowledge Based Article: KB 3058865 Version: 12.1.4100.0 Architecture: x64 Language: 1033

Title: Hotfix Pack Knowledge Based Article: KB 3067839 Version: 12.1.4416.0 Architecture: x64 Language: All

Update Source: Slipstream

....

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 Common Files Component error code: 1642 Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150701_091833\sql_common_core_Cpu64_1.log Error description: 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. Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.4416.0&EvtType=sql_common_core.msi%400x162A16FE%400x1642

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 Common Files Component error code: 1642 Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150701_091833\sql_common_core_Cpu64_1.log Error description: 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. Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.4416.0&EvtType=sql_common_core.msi%400x162A16FE%400x1642

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 Common Files Component error code: 1642 Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150701_091833\sql_common_core_Cpu64_1.log Error description: 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. Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.4416.0&EvtType=sql_common_core.msi%400x162A16FE%400x1642

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 Common Files Component error code: 1642 Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150701_091833\sql_common_core_Cpu64_1.log Error description: 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. Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.4416.0&EvtType=sql_common_core.msi%400x162A16FE%400x1642

C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150701_091833\sql_common_core_Cpu64_1.log

MSI (s) (B4:30) [09:21:44:866]: Product: SQL Server 2014 Common Files - Update '{91E61CBF-5FEA-4F9B-A696-EA4A1259225F}' could not be installed. Error code 1642. Additional information is available in the log file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150701_091833\sql_common_core_Cpu64_1.log.

MSI (s) (B4:30) [09:21:44:868]: Windows Installer installed an update. Product Name: SQL Server 2014 Common Files. Product Version: 12.0.2000.8. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: {91E61CBF-5FEA-4F9B-A696-EA4A1259225F}. Installation success or error status: 1642.

MSI (s) (B4:30) [09:21:44:869]: Note: 1: 1708 MSI (s) (B4:30) [09:21:44:869]: Product: SQL Server 2014 Common Files -- Installation failed.

MSI (s) (B4:30) [09:21:44:869]: Windows Installer installed the product. Product Name: SQL Server 2014 Common Files. Product Version: 12.0.2000.8. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1642.

MSI (s) (B4:30) [09:21:44:899]: Attempting to delete file C:\Windows\Installer\9b31570.msp MSI (s) (B4:30) [09:21:44:916]: MainEngineThread is returning 1642 MSI (s) (B4:C4) [09:21:44:916]: 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.

...

MSI (c) (E4:6C) [09:21:44:920]: MainEngineThread is returning 1642

Thanks for looking,

G

↧

Holla guys

December 15, 2016, 10:54 pm

Holla guys. I want install Microsof SQ server 2014 to my Laptop. but I have a problem "SqlSetupBootstrapper.dll has Missing. try reinstall....."