Run the following command from an elevated command prompt to install only Microsoft Machine Learning Server (Standalone) and its prerequisites.
Setup.exe /q /ACTION=Install /FEATURES=SQL_SHARED_MR /IACCEPTROPENLICENSETERMS /IACCEPTSQLSERVERLICENSETERMS
Source: Install Microsoft R Server from the Command Line | Microsoft Docs
The web portal is a web application that you open by typing the web portal URL in the address bar of the browser window. When you start the web portal, the pages, links and options that you see will vary based on the permissions you have on the report server. To perform a task, you must be assigned to a role that includes the task. A user who is assigned to a role that has full permissions has access to the complete set of application menus and pages available for managing a report server. A user assigned to a role that has permissions to view and run reports sees only the menus and pages that support those activities. Each user can have different role assignments for different report servers, or even for the various reports and folders that are stored on a single report server.For more information about roles, see Granting Permissions on a Native Mode Report Server.
Source: Web portal (SSRS Native Mode) | Microsoft Docs
Using SQL Server Configuration Manager RemotelyThese steps are meant to be performed on a PC running the client edition of Windows, or Windows Server that has the Server Graphical Shell installed.Open Computer Management. To open Computer Management, click Start, type compmgmt.msc, and then click OK.In the console tree, right-click Computer Management, and then click Connect to another computer….In the Select Computer dialog box, type the name of the Server Core machine that you want to manage, or click Browse to find it, and then click OK.In the console tree, under Computer Management of the Server Core machine, click Services and Applications.Double click SQL Server Configuration Manager.In SQL Server Configuration Manager, click SQL Server Services, right-click SQL Server (), where is the name of a local server instance for which you want to enable Always On Availability Groups, and click Properties.Select the AlwaysOn High Availability tab.Verify that Windows failover cluster name field contains the name of the local failover cluster node. If this field is blank, this server instance currently does not support AlwaysOn Availability Groups. Either the local computer is not a cluster node, the WSFC cluster has been shut down, or this edition of SQL Server 2017 that does not support AlwaysOn Availability Groups.Select the Enable AlwaysOn Availability Groups check box, and click OK.SQL Server Configuration Manager saves your change. Then, you must manually restart the SQL Server service. This enables you to choose a restart time that is best for your business requirements. When the SQL Server service restarts, AlwaysOn will be enabled, and the IsHadrEnabled server property will be set to 1.
Source: Configure SQL Server on a Server Core Installation | Microsoft Docs
To enable remote connections, use SQLCMD.exe locally and execute the following statements against the Server Core instance:
EXEC sys.sp_configure N'remote access', N'1'
RECONFIGURE WITH OVERRIDE
Source: Install SQL Server 2016 on Server Core | Microsoft Docs
I wanted to upgrade the SQL Server 2016 installed on my laptop to service pack 1 last night. But the setup failed with this error:
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): -2068380094
What I noticed in the process was that the setup process tried to stop the MSSQLSERVER service, but after about one minute of trying without any success, the setup process finished with the above error code.
So, I start analyzing the detail log file. Then, I found the following error code:
(01) 2017-01-20 19:56:47 Slp: Error: Failed to run patch request for instance: MSSQLSERVER (exit code: -2068709375)
There was nothing more than that to identify what was happened in the upgrade process. So, I start checking the sql server configuration manager and faced with two interesting things:
- I could not manually stop the MSSQLSERVER service
- Polybase Services stuck in Change Pending state
So, I had an idea for more investigations! Finally, I found the Greg Low’s following post
He was told that “enabling TCP and restarting made all good”
I check it and he was completely right!
I enabled the TCP and restarted and tried setup again with a success!