I have tried it will occur error "DB error: Unable to resolve FQDN ". when I tied to connect taosd by ip it can connect to the db successfully. However, when query data from table. It always throws "FQDN problem".The error screen shot is below.
why this happened and how to solve this? Thanks!
When we use “taos -h” to set TDengine's FQDN to connect. We must make sure that the hostname and ip address is record in hosts file.
In your case, you connect with the TDengine server using IP, you can connect with TDengine server successfully.But the tdengine server always response with FQDN(hostname),if this FQDN is not record in your hosts file. The client always throw error "DB error: Unable to resolve FQDN ".
so you need to configure the hosts file.
Related
I am trying to connect my RDS instance to a Jmeter load test however no matter what I try, I keep getting this error message in the Results Tree:
Cannot create PoolableConnectionFactory (The connection to the host database-1.cqdkrfikhe1t.us-east-1.rds.amazonaws.com, named instance database-1 failed. Error: "java.net.SocketTimeoutException: Receive timed out". Verify the server and instance names and check that no firewall is blocking UDP traffic to port 1434. For SQL Server 2005 or later, verify that the SQL Server Browser Service is running on the host.)
I feel it may be a problem with my Database URL in JDBC Connection Configuration.
The picture below shows the summary report.
I have mainly tried rewriting the Database URL multiple different ways but none of them seem to work. I have also tried removing and reinstalling the JDBC Drivers but that doesn't seem to work either. I have absolutely no idea what the problem could be. Could someone please help me out with this problem?
Edit: When I change the Database URL I sometimes get this error
message as well:
Cannot create PoolableConnectionFactory (The driver could not establish a secure connection to SQL Server by using Secure Sockets
Layer (SSL) encryption. Error: "PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to
find valid certification path to requested target".
ClientConnectionId:9b700d73-f3f0-4cf6-b3a4-607fa9827219)
I think you need to use port 1433
Check out Connecting to a DB instance running the Microsoft SQL Server database engine article
So cross check the port number, VPC options, public accessibility, etc. with the values from the JDBC Connection Configuration
More information: The Real Secret to Building a Database Test Plan With JMeter
i am trying to connect with Azure SQL database using SSMS but i am getting the bellow error message
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)
(Microsoft SQL Server, Error: 53)
We had enabled all the necessary ports also restart the SQL server, added client 'ip' in Azure firewall settings. previously we are able to connect but we changed the location of our Azure SQL server after that we are not able to connect but i can connect to another server which is located at the different location.
I found this article: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server (Microsoft SQL Server, Error: XXX) may give you some useful messages.
Basically, this error message just tell you that the client cannot make a connection to the server. It's equvalent to "SQL Server does not exist or access denied" in MDAC. Although the error message say about Named Pipe Provider, the issue does not have to be NP related. The reason is that, by default, the client stack try TCP and NP in order. If the connection attempt could not success with any of them, then NP is the last protocol tried and this is the error message to present to users.
When users see this error message, sometimes xxx is omitted. But actually, xxx is the most important part of this error message. xxx is Windows error code and it gives customer hints about why the connection fails. Here are some error code users often see. I also explain the root cause and possible solutions here.
1) xxx=53
winerr 53 means "The network path was not found". If you got this message, it means the client stack cannot find the target machine.
Here are possible reasons for this failure:
a. typo in the server name, or using "/" rather than "" between server name and instance name, e.g. "myserver/myinst" is not correct.
b. name resolution to the server name is not correct, "ping -a yourserver" would tell if that's the case.
c. The server machine is firewall'ed and file sharing is not in the exception list. You need put "File and Printer Sharing" in exception.
Hope this can helps you.
I configured the SQLAzure database. I configured the firewall for my IP and when am trying to connect to that database from my local using SQL Server Management studio, getting below error
TITLE: Connect to Server Cannot connect to XXXXX.database.windows.net.
ADDITIONAL INFORMATION:
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) (Microsoft SQL Server, Error: 53)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
The network path was not found
How to resolve this issue?
Please also check network protocol when you connect to Azure database via SSMS. It seems you are using named pipes and TCP/IP is excepted.
Hi Bravo are you able to browse the instance via Visual Studio if you have it installed?
Can you also confirm that you are not behind a corp firewall that blocks 1433 outbound?
Really minor thing but the title of the error has a trailing "." which if that is the machine name you are trying to connect to won't work - it may just be appended by the error message.
You can try a few things:
Ensure SQLAzure database name is correct (the error that you posted translates to name doesn't even exist)
Try adding port number at end of the connection
XXXXX.database.windows.net,1433
If the issue still persists, try pinging the SQLAzure from your local machine.
I have a big trouble: I need connect to my db in another city with Navicat (or other SQL clients). I made vpn - tunnel, but when I connect (with Navicat or other SQL clients) I get the following error
could not translate host name "ip" to address: Unknown host
Please help, what I need to do to fix this?
This happens with HeidiSQL, Navicat etc.
I am trying to connect mssql server 2008 using jdbc connection.
My connection url is like
jdbc:jtds:sqlserver://localhost:1433/dbname;user=username;password=password
However I get the above mentioned exception when I try to execute a stored procedure through prepared statement
I have enabled TCP/IP and Named pipes.
I have disabled firewall.
What could be the issue.
I found out it was because the following error occurs
"ole/db provider returned message login timeout expired"...
but not sure why this happens
The linked server was configured with wrong authentication values. Hence when I tried to connect to the linked server it threw authentication exception which in turn throws above mentioned exception.
Creating a linked server with proper authentication values fixed the issue.
I had the same problem, maybe the problem is related with DNS.
I fixed the problem creating the linked server with the IP Address instead of the server's name.