SQLSTATE[08001]: [Microsoft][ODBC Driver 11 for SQL Server]TCP Provider: No connection could be made because the target machine actively refused it - sql-server-2012

Please tell me how to solve this problem
i am connecting laravel 5.4 with sql server.After all the settings in config/database.php and .env.When i am writing this command php artisan migrate on cmd.it shows following error

Related

How/Can I specify the version of the SQL Server Native Client OLE DB (SQLNCLI) in the connection string

I know that using the OLEDB Driver (MSOLEDBSQL) I can specify this with the Driver keyword as documented here.
Can this be done with the SQLNCLI driver?
MY ISSUE:
I see on the target machine that both version 10 and 11 are installed and we are getting the following error, that I suspect is due an disabling of tls1.1.
System.Data.SqlClient.SqlException: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
It looks like you can't.
I had the v10 version of the SQLNCLI driver uninstalled and everything seems to be working.

Connecting sql developer to oracle 11g from lubuntu to centos

I have Installed sql-developer on Lubuntu and I want to connect sql-developer to oracle 11g, oracle 11g installed in another system(Centos)and sql-developer installed(Lubuntu) while testing the connectivity from sql-developer via tns service name its showing error as "Status -Test Failed: IO Error The Network Adapter Couldn't establish the connection". TNSPING is working for service names and ping ip-address is also working in destination sever where we have installed oracle 11g database.
Please let me know to resolve this issue.
Thanks,
Ranjithkumar
Could you please provide your TNS-Names File or the configuration of your SQL-Developer? The Error seems to occur because of a false Host-Definition. Be sure that you put in the right SID or Service name.
If you assume that your configuration must be right, please Check your DNS- and firewall-Settings. Further you can change into the Oracle-Bin Folder and execute the "tnsping" binary with the Host as Parameter.

Oracle - Apache PL/SQL Gateway Module - mod_owa - access remote server

I have an Ubuntu 13.10 VM that I've created using Vagrant. This is meant to be a local development environment for a remote application using Oracle 11g and Oracle Fusion Middleware 11g.
What I want to do is, clone the application's code repository into the local VM and "route" the requests that are made on the local VM through the server where the application is hosted (DEV), so I won't need to install the database on the local VM together with all it's packages and procedures and also Oracle Middleware.
I came across Apache PL/SQL Gateway Module (https://oss.oracle.com/projects/mod_owa/dist/documentation/modowa.htm) which it's a substitute for Oracle Middleware.
I've installed and configured mod_owa on the VM, but when I restarted Apache I got the following error:
apache2: Syntax error on line 234 of /etc/apache2/apache2.conf:
Syntax error on line 1 of /etc/apache2/conf.d/mod_owa.conf:
Cannot load /usr/lib/apache2/modules/mod_owa.so into server: libclntsh.so.11.1:
cannot open shared object file: No such file or directory
Action 'configtest' failed.
The Apache error log may have more information.
...fail!
The above error makes me think that I still need to install Oracle 11g on the VM. Is there a way to bypass that error and make use of the remote server (DEV)?
I'm late to the party, but yes you need Oracle client installed on your apache server.
You need instant client with OCI (Basic): http://www.oracle.com/technetwork/database/features/instant-client/index-100365.html
Then to simplify your running environment:
As root:
Create a file oracle.conf under /etc/ld.so.conf.d
Single line in that file with a reference you oracle lib directory (oracle client home/lib)
run ldconfig
And you should be good to go.

getting ODBC Sql Sever Driver DBNETLIB Invalid Connection error

i am working on vb.net windows application, it included vb6 reporting application exe also,for this application i am using SQL Server,In my working system it is working good. I have installed EXE in client system ,Some times in some systems i am getting this error like :
[Microsoft][ODBC SQL Server Driver][DBNETLIB] Invalid connection
any one please give me the suggestion on what i have to do.

Informix 11.50 Connection Error ERROR [08001] [IBM] SQL30081N using Informix client sdk 3.5

I have a Windows server 2008 R2 64 bit with a VMware instance of Informix Dynmic Server 11.50 virtual appliance 32bit running.
Using the default database server provided in the virtual appliance i have created a database and a table inside it.
I installed the Informix Client SDK 3.5 and the informix data server provider Drivers on the windows server.
I setup the server connection on the windows server using setnet tool.
I tested the connection with the connect test demo tool of the SDK and the query executed successfully.
Now when I am testing the .Net provider driver by running the testconn.40_32.exe with the following connection String:
testconn40_32.exe -dtc "Database=safdata; Server=192.168.154.128:9088; User ID=root; Password=root"
I get following error:
Unable to open socket to server:
ERROR [08001] [IBM] SQL30081N A communication error has been detected. Communic
ation protocol being used: "TCP/IP". Communication API being used: "SOCKETS".
Location where the error was detected: "192.168.154.128". Communication functio
n detecting the error: "recv". Protocol specific error code(s): "", "", "0".
SQLSTATE=08001
Have you tried both tests from the same machine? If not then maybe you cannot go through firewall or other network device.
If you run tests on the same machine the server works then instead of 192.168.154.128 use localhost or 127.0.0.1. You can also check if Informix listens on port 9088 using netstat command or tool like TCView or ProcessExplorer.
I uninstalled the client SDK and all other drivers.. re-installed only the client SDK and it worked. The client drivers were conflicting with other versions of the driver I had installed.