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

After applying the CU2: Unable to launch runtime for 'R' script. Please check the configuration of the 'R' runtime.

$
0
0

Hi,

After I install the CU2 for SQL Server 2016, I receive this message when I try to run an R script:

Msg 39021, Level 16, State 1, Line 1
Unable to launch runtime for 'R' script. Please check the configuration of the 'R' runtime.
Msg 39019, Level 16, State 1, Line 1
An external script error occurred:
Unable to launch the runtime. ErrorCode 0x80070057: 87(The parameter is incorrect.).
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.

before the update, everything worked fine.

what can I do?


Collation settings

$
0
0

Hi- The default collation settings on SQL server is set to Latin1_General_CI_AS. The SQL database instance has collation setting of "SQL_Latin1_General_CP1_CI_AS". Now the application team has requested that the collation settings for the SQL server be changed to the same as database setting to maintain the users, agent jobs etc that we have configured on the database.

In addition, we are going to have another SQL database with collation setting "Latin1_General_CI_AS". 

My query is if we set the default SQL server collation to "SQL_Latin1_General_CP1_CI_AS", will this have an impact to the other database with collation setting "Latin1_General_CI_AS".

Thank You!


How to generate health check report for SQL

Is there any way to install the product on Ubuntu 18.10?

$
0
0

Hi there,

I'm running Ubuntu 18.10 and was interesting to test the SQL Server 2017 in a secured intranet.

The cloud option is forbidden by company policies ;-(

I was really disappointed discovering that the only supported version is the 16.04

Is there any way to install the product on the 18.10?

TIA

Paolo

Download SSMS 17.9.1 english upgrade from non-english country

$
0
0

Hi, I'm trying to download the upgrade for SSMS in english, but it keeps downloading the italian version (I'm in Italy) and there aren't localized links for upgrade files (there are links only for the full installation file). I also changed the language at the bottom of the page but it keeps downloading italian version. This is very annoying because I think many people use english versions even in non-english countries.

I'm talking about this page https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-2017

What is the general Availability Date for SQL Server 2019?

$
0
0
What is the general Availability Date for SQL Server 2019?

Upgrading ~250 databases to SQL 2017 from SQL 2012.

$
0
0
Hello All,

I am looking to upgrade our SQL 2012 HADR Availability Group (3 servers) to SQL 2017. On a Test system all went well but a concern was found. I had 6 - 80 GB and 1 - 750 GB databases running. On failover after the upgrade it took approximately 10 minutes to upgrade the databases, not recover from choppy logs. The same amount of time was noticed on all three failovers. Our SaaS rows that will be upgraded contains ~250 databases and most are 300 GB - 1.5 TB. I extrapolated that it would take 18 hours just to failover three times. Does this seem right? An in-place/rolling upgrade is not my first choice and I am being asked to determine if we can make it work, 18 hours plus software upgrade is unacceptable.

Charlie

SQL query used in SP_WHO2

$
0
0

Hi

I need SQL query used in SP_WHO2. Actually i want to monitor for some programe name only.

Like i can put programe name in ('program1','program2') etc.

Regards,

Deepak

  


SQL Server 2014 Error code: 0x84B40002

$
0
0

Hi I would like to migrate to SQL Server 2014. When I start installation I have seen there is two instaces of sql Server and the by trying to repair then I have got error ( Error code: 0x84B40002). In services I can see two instances with two different names SQL and MSSQL. there is text file like log to get a details and I will copy it.

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2068578302
  Start time:                    2019-03-07 09:59:16
  End time:                      2019-03-07 10:03:11
  Requested action:              Repair

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:                  LOAPA2
  Machine processor count:       3
  OS version:                    Windows 8
  OS service pack:              
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x64
  Process architecture:          32 Bit
  OS clustered:                  No

Product features discovered:
  Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered  Configured
  SQL Server 2014      SQLEXPRESS           MSSQL12.SQLEXPRESS             Database Engine Services                 1033                 Express Edition      12.0.2000.8     No         Yes      
  SQL Server 2014      SQLEXPRESS           MSSQL12.SQLEXPRESS             SQL Server Replication                   1033                 Express Edition      12.0.2000.8     No         Yes      
  SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Database Engine Services                 1033                 Express Edition      12.0.2000.8     No         Yes      
  SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            SQL Server Replication                   1033                 Express Edition      12.0.2000.8     No         Yes      

Package properties:
  Description:                   Microsoft SQL Server 2014
  ProductName:                   SQL Server 2014
  Type:                          RTM
  Version:                       12
  SPLevel:                       0
  Installation location:         C:\Users\U46030\Downloads\SQLEXPR_x86_ENU\x86\setup\
  Installation edition:         

User Input Settings:
  ACTION:                        Repair
  AGTDOMAINGROUP:                <empty>
  AGTSVCACCOUNT:                 <empty>
  AGTSVCPASSWORD:                <empty>
  AGTSVCSTARTUPTYPE:             Manual
  ASCONFIGDIR:                   Config
  ASSVCACCOUNT:                  <empty>
  ASSVCPASSWORD:                 <empty>
  CLTSTARTUPTYPE:                0
  CLTSVCACCOUNT:                 <empty>
  CLTSVCPASSWORD:                <empty>
  CONFIGURATIONFILE:            
  CTLRSTARTUPTYPE:               0
  CTLRSVCACCOUNT:                <empty>
  CTLRSVCPASSWORD:               <empty>
  ENU:                           true
  FAILOVERCLUSTERGROUP:          <empty>
  FAILOVERCLUSTERNETWORKNAME:    <empty>
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTSQLSERVERLICENSETERMS:  false
  INDICATEPROGRESS:              false
  INSTANCENAME:                  MSSQLSERVER
  ISSVCACCOUNT:                  NT AUTHORITY\Network Service
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  QUIET:                         false
  QUIETSIMPLE:                   false
  SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
  SQLSVCPASSWORD:                <empty>
  UIMODE:                        AutoAdvance
  X86:                           true

  Configuration file:            C:\Program Files (x86)\Microsoft SQL Server\120\Setup Bootstrap\Log\20190307_095915\ConfigurationFile.ini

Detailed results:
  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, and then try the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x84B40002
  Error description:             The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
 

  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 Database Engine Services Instance Features
  Component error code:          0x84B40002
  Error description:             The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.

  Feature:                       SQL Browser
  Status:                        Passed

  Feature:                       SQL Writer
  Status:                        Passed

  Feature:                       SQL Client Connectivity
  Status:                        Passed

  Feature:                       SQL Client Connectivity SDK
  Status:                        Passed

  Feature:                       Setup Support Files
  Status:                        Passed

Rules with failures:

Global rules:

There are no scenario-specific rules.

Rules report file:               C:\Program Files (x86)\Microsoft SQL Server\120\Setup Bootstrap\Log\20190307_095915\SystemConfigurationCheck_Report.htm

The following warnings were encountered while configuring settings on your SQL Server.  These resources / settings were missing or invalid so default values were used in recreating the missing resources.  Please review to make sure they don’t require further customization for your applications:

The SQL Server Browser service was not found on the system. Setup will configure the service to log on as 'NT AUTHORITY\LOCAL SERVICE'.
The SQL Server Browser service was not found on the system. Setup will configure its startup type to 'Disabled'.
The SQL Server Browser service was not found on the system. Setup will configure the service to log on as 'NT AUTHORITY\LOCAL SERVICE'.
The SQL Server Browser service was not found on the system. Setup will configure its startup type to 'Disabled'.

SQL Server 2008 R2 on Windows Server 2012 R2

$
0
0

Hi,

I'm trying to understand why something happens so I will be able to explain it to my boss...

When I try to install SQL Server 2008 R2 on my Windows Server 2012 R2 machine I encounter with the following problem:
"Competability issue"
and this is the warning that I see in the eventvwr:
"The application (Microsoft SQL Server (2008 or 2008 R2), from vendor Microsoft) has the following problem:After SQl Server setup completes you will need to install Service Pack before running SQL Server on this version of Windows.
for SQL Server 2008, you will need to install service pack 3 (SP3
) or later
for SQL Server 2008 R2, you will need to install service pack 1 (SP1) or later

I need to know why SQL Server 2008 R2 RTM doesn't work on Windows Server 2012 R2 any more?
I know that it is not recommended to install 2008 R2 on 2012 R2 servers, and I know that SP and CU are importent but I need to answere on that particular issue...

Thank you.

Microsoft Command Line Utilities 15 for SQL Server installation failed

$
0
0

In a Windows Server 2016 Standard I installed Microsoft ODBC Driver 17 for SQL Server (msodbcsql_17.3.1.1_x64.msi)

After that, I tried to install Microsoft Command Line Utilities 15 for SQL Server but I have the error "Setup is missing an installation prerequisite: Microsoft ODBC Driver 17 for SQL Server".

But the driver are alredy installed.

The server need a reboot?

Sql Server install versions?

$
0
0

Hi all, we installed Sql Server 2016. However, I noticed after the install that "Microsoft Sql Server 2017" also shows in the list. Is this normal during an install? We've had some trouble during updates regarding version mismatches and I wondered if this could be part of the issue.


Error code 2233073688

$
0
0

Hi,

Trying to install SQL Server 2008R2 on Win 10 getting this error message + from log:

"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.

2019-03-10 12:30:12.90 spid7s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required."

Any idea why? Thanks!

SQL SERVER 2012 SP4 - Comptability with Dynamics AX 2012 R2

$
0
0

Hello everybody,

I would like to know if SQL Server 2012 SP4 is compatible with Dynamics AX 2012 R2 and which CU.

I didn't find any informations about it on MS Websites.

Thanks you.

Move to new AD group

$
0
0

Hi,

We are moving from one AD to another. How it will affect SQL installation and what are precautions and actions needs to be taken. One of the servers is SSRS server.

Thanks, Ashru


MCTS, http://asharafaliptb.wordpress.com


Cannot do anything on sql server installler

$
0
0

I got error value cannot be null parameter type : doc, it happen after i tried to uninstall my sql server by on midway the power went off.

after i tried to uninstall again i get that error, now whenever i want to repair, install different version or unistalling i always get that error

does anyone know how to fix it?

Can SQL Server 2012 SP4 be uninstalled?

$
0
0

Where can I find the "Documentation" that states Microsoft SQL 2012 SP4 can or cannot be uninstalled?

Change Control is demanding a rollback plan.

SSPI handshake failed with error code 0x8009030c

$
0
0

Running SQL 2014 Standard. There are 2 NICS on the box one for user facing and one for admin access. Remote login to the server and in SSMS can connect using the user facing IP , but using admin IP fails with. (Application log : “Error: 17806, Severity: 20, State: 14. SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed.” And “Login failed. The login is from an untrusted domain and cannot be used with Windows authentication”, and syslog event id 6037: “the process sqlserv.exe, could not authenticate locally by using the target name MSSQLSvc/AdminDNSName:1433. The target name is not valid”).

When RDP to the server,I connect in SSMS with Windows auth NOT SQL auth.

In configuration manager, SQL is configured to listen to all IPs. I verified with netstat that it listens.

I found some posts for fixing using the LSA key in registry for loopback, but not sure if this is the best for security.

Any other solution?

Thank you,


Does microsoft still support sql server 2012??

$
0
0

Here is the link:

https://support.microsoft.com/en-us/lifecycle/search?alpha=SQL%20Server%202012

We have server 2012 enterprise edition with service pack 3. 

But from the link

1)SQL server enterprise core gets Extended Support End Date--7/12/2022

2)Microsoft SQL Server 2012 Service Pack 3  --Service Pack Support End Date: 10/9/2018

Does Microsoft still support our server (server 2012 enterprise with sp3)? I am confused by the dates listed above.




The computer must be trusted for delegation and the current user account must be configured to allow delegation - SSDT 2012

$
0
0

I am trying to install Microsoft SQL Server 2012 in Windows 10 Operating System.

When I try to open SSDT, I get this error:

The requested operation cannot be completed.The computer must be trusted for delegation and the current user account must be configured to allow delegation.

I have a separate built-in administrator account from where I installed SQL Server.  I am able to open SSDT from that account without any issues.  From my ownuser account, by running SSDT as an administrator, I have the above error.

Can you let me know on how I can overcome this delegation issue? I have installed SQL Server Service 2012 Pack 3.


Viewing all 7707 articles
Browse latest View live


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