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."
Related
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.
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've installed SQL 2012 in Sharepoint Integrated Mode and have Sharepoint 2010 installed on a different server. In Central Administration I have added a SQL Server Reporting Services Service Application and proxy. This all appears to have worked (the RS databases were created).
The problem is I cannot finish the configuration as I need the report server URL. Upon researching I found that this would be "http://myspserver/_vti_bin/reportserver" however this does not connect. I have looked at the rsreportserver.config file and where the URL should be is just
<ReportServerUrl>
</ReportServerUrl>
Upon looking at the at the service applications list I have noticed that the SQL Server Reporting Services Service Application is stopped. This might be why I can't connect to the URL so I tried stopping and restarting the SQL Server Reporting Services Service and although this was successful it made no difference to the state of the service application.
How to get this setup sorted out?
Here is what I've done so far...
I've downloaded SQL Server 2012 Express onto my machine-
successfully restored the database that I'd like to access through VisualStudio 2012 Pro
In VS2012Pro I've clicked on Add Connection in the Server Explorer, where I select Microsoft SQL Server (SqlClient).
In order to log onto the Server I've checked "Use Windows Authentication" (and in the SQL Server properties I've enabled the use of Use Windows Authentication and Use SQL Server Authentication).
Then I select the Database that I want to connect to, and when I test the connection or click the OK button, I get this prompt ---
"A network related or instance specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections (provider: Named Pipes Provider, error: 40, - could not open a connection to SQL Server).
In SQL Server my machine is listed as a registered server like this theMachine\sqlexpress.
What solutions can you think of to circumvent this issue, as I'm at a standstill after looking through Stack and Googling for a solution? I checked to see if SQLServer was running by doing Start --> Run --> Services.msc, and it was running.
You need to start SQL Server and browser in order to connect.
Go to SQL Server configuration manager -> Select SQL Server service -> Right click on SQL Server -> Select Properties -> Select Service tab -> Select Automatic as start mode, then Start server. After that right click on Sql Server browser and select Start.
I've just installed Microsoft SQL Server Express 2008 (with Reporting Services).
My installation is side by side with SQL Server 2005.
So far creating reports and testing them in the development environment has worked fine, however I can't get the web server or report manager working.
In the Reporting Services Configuration Manager, it appears that they have been configured and have a working address (eg: http://mymachine:8080/ReportServer_EXPRESS2008/ and http://mymachine:8080/Reports_EXPRESS2008/).
The Virtual Directories don't exist in IIS, and clicking on the links in the config manager results in a "The page cannot be found".
If I create the Virtual Directories in IIS, and then use Reporting Services Configuration Manager to modify the two sites, Reporting Services Configuration Manager appears to be working correctly (all the right messages appear, indicating that it created the new site and dropped the old site successfully). However, it only drops the existing Virtual Directory and does not create a new one.
Has anyone had this problem before and/or know of a possible solution?
Basically, Reporting Services 2008 doesn't use IIS anymore.
By coincidence (or default?), I already had IIS (with Reporting Services 2005) running off port 8080. Reporting Services 2008 also wanted to run off port 8080.
It appears that the new IIS free address reservation system doesn't work in this situation. Changing the port number fixes the problem.