This question already has an answer here:
ColdFusion 10/Windowns 7 Pro 64bit Connection verification failed for data source
(1 answer)
Closed 6 years ago.
I am trying to connect datasource in coldfusion admin with my local sql server 2014 but it is not connecting . I have tried every method to do this but no success.
I have also created new user but it is also not working.
I am getting this error
Connection verification failed for data source: mlc_new
java.sql.SQLInvalidAuthorizationSpecException: [Macromedia][SQLServer
JDBC Driver][SQLServer]Login failed for user 'tester'. The root cause
was that: java.sql.SQLInvalidAuthorizationSpecException:
[Macromedia][SQLServer JDBC Driver][SQLServer]Login failed for user
'tester'.
the datasource details are
datasource name: mlc_new db name: mlc_new sever: DEV-PC\SQLEXPRESS
username: tester password : somestring
Some details on SQL Server mixed authentication. To enable do, the following:
Connect to DB server (presumably via Windows Authentication
Right click for properties on the server icon
On the properties dialog go to Security
Select "SQL Server and Windows Authentication mode". Save.
Related
I upgraded SQLServer 2000 database to SQLServer2012. After that IIS started throwing error:
Error: ERROR#1: return code:0, State:28000, Native Error Code:18456:
Message:[Microsoft][SQL Server][SQL Server]Login failed for user
''. ERROR#2: return code:100, State:00000, Native Error
Code:18456: Message:
I can connect to the remote SQLServer 2012 database via ODBC 64 bit and 32 bit tool from IIS server with same user . No issues. is migrated from SQL Server 2000 to SQL Server 2012.
Able to connect remotely using the same user via sqlcmd.
Connected via Excel to the database using all connection tests works
except IIS.
I created new user in SQLServer 2012 database and got the same error.
IIS configuration info below:
<CfgSpecDataSource>
<Connection>
DRIVER=SQL Server; SERVER=Server_IP; DATABASE=DB_NAME; UID=<db_user>; PWD=passed;</Connection>
</CfgSpecDataSource>
I have mixed mode authentication (windows/sql server) defined on the sql instance.
Tried changing DRIVER=SQL Server Native Client 11.0
and got stuck with 18456 error;
Thanks to Vijunav Vastivch and sepupic for your suggestions.
1) This is a unique problem.
(Dropped the user and created again, tried with another new user ; no luck)
2) sepupic suggestion helped; I looked into the SQL Server Log and it displayed "Password did not match that for login provided"
Password was in UPPER case in the IIS configuration file. I narrowed down the possibilities of didn't match error and tried with lowercase password in configuration file. It worked.
I am using php laravel to connect to a sql server db, but there is an issue sql server db "closed php connection". When I check requests in Profiler Trace, I have 2 requests: first one is from php audit login, then audit logout. The query doesn't complete, and I don't know why.
1) This error I get it from laravel:
SQLSTATE[08S01]: [Microsoft][ODBC Driver 13 for SQL Server]TCP Provider: An existing connection was forcibly closed by the remote host.
(SQL: select * from contact)
2) Image from SQL SERVER Profiler Trace
Im installing the MDM of Informatica.
MDM 10.2 - Jboss 6.4 EAP - SQL Server 11 - Windows Server 2008 R2.
During the creation of the schema 'sip_ant.bat create_bpm' i got this error
Microsoft ODBC Driver 13 for SQL Server : Login failed for user 'sa'.
(Same eeror with another user)
I already tried to use the Auth Mixed Mode and restarted the instance of the DB.
Error received is
D:\informatica\database\bin\common.xml:248: The following error occurred while executing this line:
D:\informatica\database\bin\mssql\database.xml:1214: Launched command return error code 1.
And that's the line of database.xml:1214 that refers:
collation_name="${activevos.collation}" param2=""${dbpath_short}"" param1="${activevos.password}">
Im able to login via SQLCMD on CMD with user 'sa' and other users.
MDM and SQL Server are on different Machine.
Any suggestion?
By default SQL Server will track failed logins and register it in the server log along with the reason. So check out your errorlog and look for errors 18456.
You can read the log by using SQL Server Management Studio by going to server, Management, SQL Server Logs, Current. Or any other way you prefer.
You'll find something like this:
2018-02-27 13:51:26.120 Logon Error: 18456, Severity: 14, State: 5.
2018-02-27 13:51:26.120 Logon Login failed for user 'fasd'. Reason: Could not find a login matching the name provided. [CLIENT: 10.80.62.89]
server=Yourservername,portnumber
You can put the above in your connection string
Problem was due to Customer configured another Default SQL port to use on SQL Management.
I have an existing instance of ColdFusion 11 server and SQL Server 2012 on a Windows 7 Ultimate platform.
I have several SQL Server datasources already connected successfully connected using: localhost\SQLEXPRESS, username "sa" and my password. When I try to add a new database in the CF Administrator I get this error:
Connection verification failed for data source: ocm5
java.sql.SQLInvalidAuthorizationSpecException: [Macromedia][SQLServer
JDBC Driver][SQLServer]Login failed for user 'sa'. The root cause
was that: java.sql.SQLInvalidAuthorizationSpecException:
[Macromedia][SQLServer JDBC Driver][SQLServer]Login failed for user
'sa'.
It appears to be a login issue, not a connection issue so I don't think it has to do with source limits on Developer platforms.
In 2012 or beyond you will not be able to us "sa" - and you should never use it anyway to set up a datasource. Doing so opens up a huge attack vector directly to your data and your server itself.
You will need to set up a separate username and password and give it DBO permissions to your DB. This will expose only your specific database to your CF connection. If you can you should narrow permissions further - do you really need "create" permissions for example?
I have two SQL Servers : one in Dijon, France; one in Arvada, Colorado, US. A data replication has been set up between them.
Everything works fine when users try to connect to SQL Server 2008 R2 Dijon database.
BUT an error occurs when one of my users is trying to connect to SQL Server 2012 US database from a VB.Net application.
The error is :
"A connection was successfully established with the server, but then an error occurred during the login process (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)"
This error shows up only for one user. The others can connect without any issue. I have maybe a clue about this. We already encountered connection issues for him, because he belonged to many AD security groups.
Here is the connection string :
Data Source=server\instance;Initial Catalog=db;Integrated Security=SSPI;Connection Timeout=0;
We have the same issue for a US user trying to connect to the same server. But not when he tries to connect to Dijon. Do you have any clue that could help me resolving this issue please ?
I checked StackOverflow threads and other solutions from the web, but nothing helped me...
Refer following URLs
Troubleshooting: Connection Forcibly Closed
TCP Provider, error:
connection was forcibly closed
Follow these steps
First goto services and check whether 'SQL Server Browser' service is started, if not start the service.
Open SQL Server Configuration Manager
Goto Protocols for MSSQLSERVER
Enable all protocols
Goto SQL Native Client
Select Client Protocols and and Enable All
Restart the SQL Server services.
Use .. (.NET Framework Data Provider for SQL Server) as provider
Connectionstring
Data Source=server\instance;Initial Catalog=;Persist Security Info=True;User ID=;Password=;Network Library=dbmssocn
It was, as I expected, a problem of Kerberos authentication because my user has too many AD security groups...
The solution is explained here : Problems with Kerberos authentication when a user belongs to many groups and here MaxTokenSize and Windows 8 and Windows Server 2012
If the authorization data for a user attempting to authenticate is larger than the MaxTokenSize, then the authentication fails for that connection using that protocol.
On Windows 7 and Windows Server 2008R2 , the MaxTokenSize (the default buffer size for Kerberos) is 12k. Its size has been increased in Windows 8 and Windows Server 2012 to 48k. It wasn't enough for my case.
I had to add a key in the registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters\MaxTokenSize (REG_DWORD type to the decimal value 65535).
Then I rebooted the server.
My user can now access data without error.