For example, if Force Protocol Encryption is not set for the client, an application may request encryption itself.
Application settings never reduce the level of security set by SQL Server Client Configuration Manager, but may strengthen it. In this case, encryption will use a self-signed server certificate without validation if no verifiable certificate has been provisioned on the server.Īpplications may also use the "TrustServerCertificate" keyword or its associated connection attribute to guarantee that encryption takes place. To enable encryption to be used when a certificate has not been provisioned on the server, SQL Server Configuration Manager can be used to set both the Force Protocol Encryption and the Trust Server Certificate options. If you deploy a verifiable certificate on the server, ensure that you change the client settings about trust the certificate to FALSE.įor information about connection string keywords, see Using Connection String Keywords with SQL Server Native Client. By setting your client to trust the certificate on the server, you might become vulnerable to man-in-the-middle attacks. By default, encryption of all network traffic for a connection requires that a certificate be provisioned on the server. This may also be configured by SQL Server Configuration Manager using the Force Protocol Encryption option, and by configuring the client to request encrypted connections. The keywords are "Encrypt" for ODBC and OLE DB when using a provider string with IDbInitialize::Initialize, or "Use Encryption for Data" for ADO and OLE DB when using an initialization string with IDataInitialize. Transport Security Layer (TLS) can be made secure only with certificate validation.Īpplications may also request encryption of all network traffic by using connection string keywords or connection properties. It is highly recommended that you provision a verifiable certificate on SQL Server for secure connectivity. The encrypted handshake is based on NT LAN Manager (NTLM). Self-signed certificates do not guarantee security. If no certificate has been provisioned on the server when it starts up, SQL Server generates a self-signed certificate which is used to encrypt login packets. SQL Server always encrypts network packets associated with logging in. If so, what is the connect string that Crystal is using to try to connect to SQL Server?ĭoes anybody have this information? PLEASE.Applies to: SQL Server (all supported versions) Azure SQL Database Azure SQL Managed Instance Azure Synapse Analytics Analytics Platform System (PDW).Is the PeopleSoft module providing instructions to Crystal Reports, and Crystal Reports is making the connection?.If so, what is Crystal passing to PeopleSoft?.Is Crystal passing connect information to the PeopleSoft module, and letting the PeopleSoft module make the connection?.I need to know how Crystal Reports is trying to connect to the database. Through the Data Link utility, I am able to see the connect string using just the SQL Server Native client, but I can't do that with the PeopleSoft PeopleTools connection type that we use in Crystal Reports.
Details: 01000: The driver doesn't support the version of ODBC behavior that the application requested (see SQLSetEnvAttr)
At that time, the login window shows me PeopleSoft PeopleTools as the Server, and prompts me for my User ID and password (like it does in Windows 2008), but, it also asks me for the Database in that first window. On Windows 2012, however, it all looks the same until I select PeopleSoft PeopleTools from the ODBC (RDO) source list.
Aside from having to enter my username and password twice, it works beautifully. Then I get the PeopleSoft login window where I specify the database, user, and password. I get a Connection Information window where I specify my PeopleSoft username/password. I create a new connection, select ODBC (RDO), select PeopleSoft PeopleTools as my ODBC Data Source. On Windows 2008, Crystal Reports connects to the database successfully.
The only difference is the Windows version. Both servers have the same Crystal Reports, the same SQL Server Native Client version, and the same PeopleSoft version installed. I am using Crystal Reports 2011 on Windows 2008 R2 successfully, but it is failing on Windows 2012 R2.