After upgrading to Microsoft.Data.SqlClient Version=4.0.0 got the error:
A connection was successfully established with the server, but then an
error occurred during the login process. (provider: SSL Provider,
error: 0 - The target principal name is incorrect.
I looked up the breaking change https://github.com/dotnet/SqlClient/pull/1210 and then set Encrypt=False in the connection string, however the error remained the same.
The error went away only by reverting to 2.0.1
Could anyone please suggest how to fix the issue in 4.0.0 ?
Related
I am having an issue with getting a server connection using the rsDriver function using this code:
driver <- rsDriver(browser = "chrome", chromever = "111.0.5563.19", port=free_port(),check=F, verbose=T)
I get this error:
Warning: Could not determine server status.[1] "Connecting to remote server" Could not open chrome browser. Client error message: Undefined error in httr call. httr output: Failed to connect to localhost port 14415 after 2229 ms: Connection refused Check server log for further details.
As suggested by other posts, I have tried deleting the LICENSE.chromedriver files which has not worked, as well as updating all dependencies of wdman. I have also attempted to revert wdman back to 0.2.5 from the current version but the old version will not install. While attempting to roll wdman back to v0.2.5 using
remotes::install_version("wdman",version="0.2.5",repos="http://cran.us.r-project.org")
I get this error:
Downloading package from url: http://cran.us.r-project.org/src/contrib/Archive/wdman/wdman_0.2.5.tar.gz Installing package into ‘C:/Users/abc/AppData/Local/R/win-library/4.2’ (as ‘lib’ is unspecified) Warning message: In i.p(...) : installation of package ‘C:/Users/abc/AppData/Local/Temp/RtmpuCeY3j/remotes1aec32a03b15/wdman’ had non-zero exit status
I have also tried using firefox instead of chrome without success. This is on windows 10, with R 4.2.2, RSelenium 1.7.9.
Good day, I am experiencing the below error after deploying my CapApp on EI 7.1.0
"WARN {FtpClientFactory$FtpConnectionFactory} - Invalid connection timeout null. Set the connectionTimeout as 5000. (default)
[2022-10-13 15:50:12,626] WARN {FtpClientFactory$FtpConnectionFactory} - Invalid connection retry count null. Set the connectionRetryCount as 5. (default)
[2022-10-13 15:50:12,626] ERROR {ListFiles} - Error while performing file:listFiles for folder ftp://ftp-user:***#192.168.1.36:21/Incoming/In org.apache.commons.vfs2.FileSystemException: Could not connect to FTP server on "192.168.1.36"."
Any assistance will be much appreciated.
I am somewhat experienced with Robot Framework, but new to the idea of connecting it to databases. I am trying to create a basic database test in my organization using Robot Framework in the PyCharm IDE. I've written the test using pymssql. It gives an unusual error message when it fails. I've read that I might need to install FreeTDS to do this, but I would prefer not to if I don't absolutely have to. I have seen several answers to this kind of question from Python developers, but I've not seen any who are using Robot Framework specifically.
Versions:
PyCharm 2020.1
Python 3.8.
Pymssql version 2.1.5.
Here is my code and the error messages I am getting.
*** Settings ***
Documentation DB Suite
Library Zoomba.GUILibrary
Library DatabaseLibrary
Resource ../../Pages/xxx/resource.robot
*** Variables ***
${DBName} DBxxx
${DBUser} USER xxx
${DBPass} PASS xxx
${DBHost} localhost
${DBPort} 1433
*** Test Cases ***
TC 001 Database Check
Connect To Database pymssql ${DBName} ${DBUser} ${DBPass} ${DBHost} ${DBPort}
${output}= Execute SQL String select * from dbo.xxx;
Log To Console ${output}
Disconnect From Database
And here is the error message:
OperationalError: (20009, b'DB-Lib error message 20009, severity 9:\nUnable to connect: Adaptive Server is unavailable or does not exist (localhost)\nNet-Lib error during Unknown error (10061)\nDB-Lib error message 20009, severity 9:\nUnable to connect: Adaptive Server is unavailable or does not exist (localhost)\nNet-Lib error during Unknown error (10061)\n')
I have read elsewhere that this error means that my Pymssql just can't find the server, but I've seen Pymssql not throw these errors before in other tutorials. It just connects right away. Anybody got any ideas on this one? I'd really appreciate the help.
I am currently workinig on datastax cpp-driver in C and was working around some examples when I came across a very trivial problem. While trying to execute the Basic Authentication Script here, I found this error showing up and the code execution getting stuck.
The Error:
1587040775.210 [ERROR] (cluster_connector.cpp:192:void datastax::internal::core::ClusterConnector::on_connect(datastax::internal::core::ControlConnector*)): Unable to establish a control connection to host 127.0.0.3 because of the following error: Underlying connection error: Connect error 'connection refused'
1587040775.210 [ERROR] (cluster_connector.cpp:192:void datastax::internal::core::ClusterConnector::on_connect(datastax::internal::core::ControlConnector*)): Unable to establish a control connection to host 127.0.0.2 because of the following error: Underlying connection error: Connect error 'connection refused'
1587040775.211 [ERROR] (cluster_connector.cpp:192:void datastax::internal::core::ClusterConnector::on_connect(datastax::internal::core::ControlConnector*)): Unable to establish a control connection to host 127.0.0.1 because of the following error: Underlying connection error: Received error response 'Invalid or unsupported protocol version (66); supported versions are (3/v3, 4/v4, 5/v5-beta)' (0x0200000A)
1587040775.211 [WARN] (cluster_connector.cpp:289:void datastax::internal::core::ClusterConnector::on_connect(datastax::internal::core::ControlConnector*)): Host 127.0.0.1 does not support protocol version DSEv2. Trying protocol version DSEv1...
1587040775.212 [ERROR] (cluster_connector.cpp:192:void datastax::internal::core::ClusterConnector::on_connect(datastax::internal::core::ControlConnector*)): Unable to establish a control connection to host 127.0.0.1 because of the following error: Underlying connection error: Received error response 'Invalid or unsupported protocol version (65); supported versions are (3/v3, 4/v4, 5/v5-beta)' (0x0200000A)
1587040775.212 [WARN] (cluster_connector.cpp:289:void datastax::internal::core::ClusterConnector::on_connect(datastax::internal::core::ControlConnector*)): Host 127.0.0.1 does not support protocol version DSEv1. Trying protocol version v4...
What could be these protocols that are not supported by my machine? Also, after it comes to the last warning, which is trying protocol v4 it gets stuck.
I'm using Casssandra 3.10+, Cpp-driver 2.13.
Anybody with a workaround or a solution would be of much help. Thanks in advance
I've looked around a bunch to find some documentation to back this up but I can't find any, so this part is conjecture. It appears that server version 3 uses protocol V3. It looks like server version 4 (still in beta) will use protocol V4. I suspect V5 is a future iteration that is being planned and still not written in stone yet (and why it's tagged as beta in the warning).
This part isn't conjecture.
If you add this to your code before you connect to the cluster:
cass_cluster_set_protocol_version(cluster, CASS_PROTOCOL_VERSION_V3);
All the warnings about downgrading to different protocols should go away.
Running Neo4j Desktop version 1.0.15. Trying to start DB causes the start fail:
Database failed to start:
DB [database-f8950fdd-6b5f-4fea-8c9f-e8457ee1da9a] 'v3.3.1' exited
with status 'KILLED'. Check the logs
Major Log parts are below
2018-02-26 23:03:38.004+0000 ERROR Failed to start Neo4j: Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase#6411d3c8' was successfully initialized, but failed to start. Please see the attached cause exception "Connection timed out: connect". Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase#6411d3c8' was successfully initialized, but failed to start. Please see the attached cause exception "Connection timed out: connect".
Caused by: java.lang.RuntimeException: Error starting org.neo4j.kernel.impl.factory.GraphDatabaseFacadeFactory, C:\Users\kiril\AppData\Roaming\Neo4j Desktop\Application\neo4jDatabases\database-f8950fdd-6b5f-4fea-8c9f-e8457ee1da9a\installation-3.3.1\data\databases\graph.db
Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.backup.OnlineBackupKernelExtension#c6e0f32' was successfully initialized, but failed to start. Please see the attached cause exception "Connection timed out: connect".
Suppressed: org.neo4j.kernel.lifecycle.LifecycleException: Exception during graceful attempt to stop partially started component. Please use non suppressed exception to see original component failure.
Caused by: java.io.IOException: Unable to establish loopback connection
It might be your neo4j was still running.
I solved this problem by shutting down the database and restarting it.
Platform: Windows 10;
Neo4j Desktop version: 1.1.13
Open a commend-line window and go to the directory of your neo4j database.
run
bin\neo4j status
to check the status of your database.
If it is running, run
bin\neo4j stop
to shut down your database.
Then go back to the Neo4j Desktop, click the start button, and it could be symptom-free.
I had the same problem and the issue was resolved when I cloned the graph I was connecting. Thereafter, I could connect to the new graph without any problem.