Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 days ago.
Improve this question
I have just started to work with ESB system .And my project is running in my local work computer without any errors.If deploy my project to cloudhub ,there is no connection with data base server .
and also i can't run my project in cmd .
enter image description here
enter image description here
i have this kind of error and i don't know what to do.
NOTE : I ' M USING JDK11 AND JDBC8
IF I deploy the project to our work server ,will it work or not?
note::: i cant run my project in cmd
NOTE ::: I 'm using oracle db server
Your application in CloudHub does not has network connectivity to the database. Your database is in a private network so it could be assumed that is not accessible from the public Internet. Establishing connectivity requires networking expertise and is different in CloudHub 1.0 than CloudHub 2.0.
As for the question if it will work in your server it is impossible for anyone outside your network to answer. You should check network connectivity from the Mule server to the database DNS name or IP, and port. Or ask your network administrator or similar teams.
The version of the JDBC driver will not change network connectivity but may show different error messages. The version of the JDK is also not relevant to this issue. Unrelated to that you should use the same version as your target to avoid incompatibilities. CloudHub at this time doesn't support JDK 11.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
This is what I have if I search for SQL in my installed programs:
and if I try localhost then I get the connection error.
I CAN successfully connect to online database we have at work but for practicing I want to use my own local DB and I can't connect to it?
Check if you have an entry "Microsoft SQL Server xxxx" in your Start Menu > Programs. If so, you have some bits of SQL Server installed.
If you have this folder - try to find the "Configuration Tools > SQL Server xxxx Configuration Manager", and launch it.
If it open, it should show you a screen something like this:
In the "SQL Server Services" tab, find the entries labelled "SQL Server (xxxx)" - if you don't find any --> you do not have SQL Server installed.
If you find some - is their "State = running" ? If not - SQL Server is installed, but not running, so you cannot connect to it.
The value in brackets after "SQL Server" is the instance name - MSSQLSERVER stands for the default (unnamed) instance which you should be able to connect to using ., (local) (including the parenthesis!), or localhost.
If you see any other string, that's the instance name that needs to be used for connecting to it - in my case e.g. SQL2014, so I can connect to that instance using .\SQL2014, (local)\SQL2014, or localhost\SQL2014.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I'm developing a small app on my own and I am trying to install a database on a local machine that I will be using for development.
So far I have done all of these things:
Install SQL Server Management Studio;
Created a server with name (fictious) is MYCPU/SQLEXPRESS
Created in it a database named MYPROJECT1and I have set the sizes as best as I could figure out
Added in security a login user named test / passwordfor connection tests;
SQL Server configuration manager tells me that the SQL Server service is running, the SQL Server agent is stopper and the SQL Server Browser is running;
Got the IP of my machine which will be (fictious) 254.254.254.123
In windows firewall, I have added an Inbound Rule named SQL Server Port 9999 (9999 being the proper port which is supposed to be listened by the Server);
I have a Linksys router and, on this router, in security tab, single port forwarding, I have a Remote Desktop connection with external / internal port routing to port 9999 with ip 254.254.254.123 and it is enabled;
I have authorized TCP/IP protocol on my server.
This resumes what I have done as best as I remember as I have tried many things. My objective is to connect to the MYPROJECT1 using a connection string in visual studio; however I do not know how to format this connection string, so I am using a modified connection string took from another project which connects on a remote database which works (but is not located at home):
<add name="MyDatabaseConnection"
connectionString="metadata=res://*/Models.Database.MYPROJECT1.csdl|res://*/Models.Database.MYPROJECT1.ssdl|res://*/Models.Database.MYPROJECT1.msl;provider=System.Data.SqlClient;provider connection string="data source=254.254.254.123;initial catalog=MYCPU/SQLEXPRESS\MYPROJECT1;user id=test;password=password;MultipleActiveResultSets=True;App=EntityFramework""
providerName="System.Data.EntityClient" />
However when I try to connect to this database, Visual Studio shows me the following error:
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)
The system cannot find the file specified
I need help troubleshooting to find the exact cause of the problem and FINALLY connect to my database remotely, this would mean a lot to me. If you have any questions in the process or think that there is information missing, feel free to ask.
You incorrectly specified data source and initial catalog properties in connection string.
Instead of
data source=254.254.254.123;initial catalog=MYCPU/SQLEXPRESS\MYPROJECT1`
try to specify
data source=254.254.254.123\SQLEXPRESS;initial catalog=MYPROJECT1
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
There is not route between the web server (CentOS, 192.168.10.100) and the SQL Server (192.168.12.200).
I have installed tiny_tds on the web server. Which network ports are required to add to the routes in order for tiny_tds to read/write SQL Server data?
By default SQL Server runs on 1433 port but you can configure that in SQL Server Configuration Manager.
Go to SQL Server Network Configuration -> {PInstance} -> TCP / IP and you’ll see a list of IP addresses and ports SQL Server is configured to use by default. Make sure that IP address you are using to reach SQL Server is enabled in SQL Server Config manager.
If this still doesn’t work you might want to check connection string and/or post some code here.
The default SQL Server port is 1433, and client ports are assigned a random value between 1024 and 5000.
http://support.microsoft.com/kb/287932
tiny_tds follows the default ports.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
My problem is that I can't connect to any SQL Server instance installed on our server (it has both 2008 and 2012) using dynamic ports. Static ports works well. Also, if you mention dynamic port number in connection string, you can connect. But connection failed (regular error "Network or instance-specific...") with named instance without port number.
I found the solution - run sqlbrowser.exe -c on the server. After that everything works until server restarts. How to solve or diagnose it?
P.S. Firewall is OFF.
EDIT:
Also, when I'm closing this tool, it becomes inavaliable again. I'm not always connected to server with remote desktop. Now it works only when I connected and started this tool. Looks not OK for me.
If you want to connect to an instance without a port number, then the browser service must be running. The fix is simple. Set the browser service to start automatically in the services console or in SQL Server Configuration Manager.
With dynamic ports, the port number will change every time you restart the server.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I've tried to connect to an SQL Server via WAN using as servername my WAN IP (in my case, a domain) but I can't do that when I can via LAN.
How can I fix that?
Can you be more specific?
How are you connecting to the server? Which language are you using? Can you paste the IP of both machines?
I'm not sure if you are using the right IP, but one thing to remember in networking is that "your own network does not know itself"; what I mean is that, supposing I have 64.148.129.89 as public IP, if I try to connect to that IP from any computer on my network, I will get the "Not Found Error" or a "Timeout Error."
Why? Well, simply because DNS doesn't make a U turn: After it bubles up outside of your network, it won't point back to the same spot.
What's the solution you say?
Use your local intranet IP to connect between machines. An example of intranet IP is 192.168.2.1 which usually points to your default gateway.