We have an Azure VM where SQL Server 2017 is installed. When the VM was set up, the level "local" was selected. Now we determined it should be private and not "local". We clicked the Edit pencil icon on the portal but the drop down box with supposedly 3 possible option values (public, private, local) is grayed out.
What can be done to open the drop down box and change the SQL Server connectivity level? SQL Server is configured with tcp/ip/named pipes/shared memory enabled and the SQL Server service was restarted but that made no difference.
Thanks
It seems your browser issue. I test on Edge, I could modify it.
I suggest you could change a browser or change a PC and test again.
Related
I have Remote Desktop Services running on Windows Server 2012 R2. This feature is still working just fine. I can log into the RD Web page, and access all of my remote applications that I have published.
However, I can no longer manage the deployment. When I launch server manager, and navigate to Remote Desktop Services, I see a message "A Remote Desktop Services deployment does not exist in the server pool. To create a deployment, run the Add Roles and Features Wizard and select the Remote Desktop Services installation option."
When I click manage > Add Roles and Features. The RD Web components are showing as installed. This just started happening recently. Does anyone know why?
I fixed it! I'm not sure why this fixed it, but disabling the options for IPv6 worked. Basically, go into your NIC adapter properties, and uncheck the box next to IPv6.
I have a VPS with Windows Server 2016 Datacenter, which I access through Remote Desktop. I would like to access it through VPN, so I tried to repeat the working configuration I have in another VPS with Windows Server 2008 Standard.
Both servers have a single Network Interface with a public address and a second internal address (10.1.0.1/255.255.255.248). As I said, VPN works perfectly on 2008.
The procedure I followed is described perfectly with screenshots in an article by Thomas Mauer
http://www.thomasmaurer.ch/2016/10/how-to-install-vpn-on-windows-server-2016/
So, briefly, I added the Remote Access role with the Remote Access and Routing features. The role and features get installed without any problem and then I am directed to a wizard, though which I try to initialize the VPN-only feature with a custom configuration. When I finally get into the "old" Routing and Remote Access Management console and try to right-click on the server node to "Configure and Enable Routing and Remote Access" this procedure never ends. A rotating clock icon stays there forever, so I have to kill the management console from the task manager.
When I reopen the management console, either with or without restarting the server, the server looks like running. Then I right-click on the server and select "Properties" in order to define the tunneling protocol for VPN as well as the internal address range that will be provided to the connected clients. The problem here is that this properties popup never gets saved. The "Apply" button does nothing, the "OK" button does not close the form and only the "Cancel" button closes the form without changing anything.
Has anybody seen this behaviour? Am I missing something?
Best regards,
Alex
I don't know why, but for this service to work the user "Network Service" needs to have "Logon as Service" permission, other services do not seam to require that...
You can grant this permission either by using secpol.msc or by just switching the service to run as e. g. "Local System" and back to "Network Service" (empty password fields).
To answer my question, it turned out that, for reasons I don't know, when the routing and remote access was being installed, the "Remote Access Management Service" was not starting. And after the server's restart it was always at "Starting" status.
This service is installed to run under the "Network Service" credentials with an Automatic (Delayed start) start type. When I changed to "Local Service" and manual, I was able to install the Role and initialize it without any problem. And then when I went back to Network Service and Automatic it runs without any more problems.
Strange ...
Alex
Another year and another Azure portal redesign. I'm now running in the new Preview and I cannot find where to allow a firewall rule so that outside IP addresses (Visual Studio on my own machine) can access Azure SQL.
Does anyone know where this can be set?
Sure, here's the journey: Click Browse, select SQL databases, select your database, now in the database blade click on the server (not the database), you'll now see the server blade where you can click on the Firewall settings. Voilà!
I can access MS Sql from a web application resides in Windows. But it is not possible with a web application reside in Linux. com.microsoft.sqlserver.jdbc.SQLServerDriver is used in this application.
Following are the configurations.
Tomcat 6
MS SQL 2005
jdk6
Driver :com.microsoft.sqlserver.jdbc.SQLServerDriver
There aren't problems. Just make sure that the server in which resides the web app have network visibility on the server where reside MS SQL 2005.
Make sure also that MS SQL 2005 have network connection enabled. To do that look at those lines from microsoft documentation:
"You must enable remote connections for each instance of SQL Server 2005 that you want to connect to from a remote computer. To do this, follow these steps:
Click Start, point to Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Surface Area Configuration.
On the SQL Server 2005 Surface Area Configuration page, click Surface Area Configuration for Services and Connections.
On the Surface Area Configuration for Services and Connections page, expand Database Engine, click Remote Connections, click Local and remote connections, click the appropriate protocol to enable for your environment, and then click Apply.
Note Click OK when you receive the following message:
Changes to Connection Settings will not take effect until you restart the Database Engine service.
On the Surface Area Configuration for Services and Connections page, expand Database Engine, click Service, click Stop, wait until the MSSQLSERVER service stops, and then click Start to restart the MSSQLSERVER service."
We are having a problem deploying a reporting services report to a sql reporting services computer that is configured in SharePoint Integrated mode. I can successfully deploy to the SharePoint document libraries set up for reports and data connections if I do it locally from the box that SharePoint and Reporting Services are deployed on. If I try and do the same thing with the exact same deployment properties from a remote box, I constantly get a Reporting Services Login dialog popping up and no combination of domain\username and password will work. I've even tried the machines local admin account and still nothing.
Any ideas where to start looking?
This occurs when BIDS cannot connect to the Report Server instance. Check the URLs, and see if any firewall is blocking the connectivity to the remote RS instance.
I finally found the solution to this issue. Basically the build of sql server 2008 reporting services I installed added an RSWindowsNegotiate setting into rsreportserver.config file and I was running the reporting service under an account other than Network Service. I removed the RSWindowsNegotiate setting and just left the RSWindowsNTLM setting and everything started working properly for us.
More info can be found here, Solving the Reporting Services Login Issue