SQL Server could not connet to the database service for server configuration. The error was: [Microsoft][SQL Native Client] Encryption not suppprted on the client. Refer to sever logs and setup logs for more information. For details on how to view setup logs, see :how to View Setup Log Files" in SQL Server Books Online.
Product: Microsoft SQL Server 2005 -- Error 29515. SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Encryption not supported on the client. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
I have SQL2000 installed as the default instance, and now I'm trying to install SQL 2005 standard edition as a named instance.
I receive this error : SQL Server could not connect to database service for server configuration.. [SQL Native client] Encryption not supported on the client. However I'm able to install client tools
The setup works fine on other box with the same config : SQL 2000/Windows XP, is there any work around for this issue ?
In my SQL 2000 client network utilty "Force proctocol encryption " is desabled and did not find the setting for SQL 2005 !
I have tried reinstalling the sqlncl.msi - re-booting etc without success.
I'm on windows vista beta 2 build 5384.
Brand spanking new machine (less that 48 hrs old) and I can't beleive my bad luck with sql express. My xp pro machine works fine.
Hers's the error:
TITLE: Microsoft SQL Server 2005 Setup ------------------------------
SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Encryption not supported on the client. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=setup.rll&EvtID=29515&EvtType=lib%5codbc_connection.cpp%40Do_sqlScript%40OdbcConnection%3a%3aconnect%40connect%40x15
------------------------------ BUTTONS:
&Retry Cancel ------------------------------
Here's the log:
Microsoft SQL Server 2005 9.00.2047.00 ============================== OS Version : Professional (Build 5384) Time : Sat Jul 01 08:01:37 2006
Machine : JOHN-PC Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.2047.00 Install : Successful Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_JOHN-PC_SQLSupport_1.log -------------------------------------------------------------------------------- Machine : JOHN-PC Product : Microsoft SQL Server Native Client Product Version : 9.00.2047.00 Install : Successful Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_JOHN-PC_SQLNCLI_1.log -------------------------------------------------------------------------------- Machine : JOHN-PC Product : Microsoft SQL Server VSS Writer Product Version : 9.00.2047.00 Install : Successful Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_JOHN-PC_SqlWriter_1.log -------------------------------------------------------------------------------- Machine : JOHN-PC Product : SQL Server Database Services Error : SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Encryption not supported on the client. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online. -------------------------------------------------------------------------------- Machine : JOHN-PC Product : Microsoft SQL Server 2005 Express Edition Product Version : 9.1.2047.00 Install : Failed Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_JOHN-PC_SQL.log Last Action : InstallFinalize Error String : SQL Server Setup could not connect to the database service for server configuration. The error was: {Microsoft}{SQL Native Client}Encryption not supported on the client. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online. Error Number : 29515 --------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
SQLSetup0001_JOHN-PC_SQLNCLI_1.log snippet (right at the end) says:
<snipped>
MSI (s) (AC:64) [20:59:38:014]: Product: Microsoft SQL Server Native Client -- Configuration failed.
MSI (s) (AC:64) [20:59:38:014]: Product: Microsoft SQL Server Native Client. Version: 9.00.2047.00. Language: 1033. Configuration change completed with status: 1603.
</snipped>
and at the end of SQLSetup0001_JOHN-PC_Core(Local).log
<snipped>
Running: ReportChainingResults at: 2006/5/30 20:59:42 Error: Action "ReportChainingResults" threw an exception during execution. One or more packages failed to install. Refer to logs for error details. : 1706 Error Code: 0x800706aa (1706) Windows Error Text: The endpoint format is invalid.
Source File Name: sqlchainingsqlchainingactions.cpp Compiler Timestamp: Mon Jan 16 02:06:13 2006 Function Name: sqls::ReportChainingResults::perform Source Line Number: 3245
Can anyone advise. I'm willing to take a "you'll have to re-build your machine" response if I have to. But I just need to know if this really is required.
I currently have SQL2005 Std, using 2 separate domain accounts for both SQL server and SQL agent. When accessing the MSDB stored packages folder from mgmt studio, I get the following error:
Client unable to establish connection. Encryption not supported on SQL server.
I did google for this error, but have tried all suggestions, including updating the MsDtsSvr.ini.xml file with the servername. I am using a default instance.
Also, I am only able to access the MSDB folder if I set the SQL service account to the local admin account. I have also set the SQL service account to be part of the local admins group, but without any luck.
On Windows XP systems I get the following issue when trying to browse the MSDB folder in SSIS
Client unable to establish connection Encryption not supported on SQL Server. (Microsoft SQL Native Client)
I have noticed another post where several others have noticed the same issue. It appears to only occur on Windows XP installations. Is there a workaround or fix for this?
I have a basic understanding of the encryption using T-SQL, but is all of this at the T-SQL level? Like can a client have a certificate, be sent the encrypted value (that was encrypted on SQL Server), and using the same cert that is on the server decrypt the data?
Is there a good article/book that covered encryption in detail that you can suggest? Or is this something that you would build in .NET?
Using SQL Server Business Intelligence Development Studio, when I try to create a new OLEDB connection manager and I try to connect to the SQL 2005 DB, I get an error message saying that "Client is unable to establish connection Encryption not supported on the client"
This is ONLY in SQL Server Business Intelligence Development Studio!
If I connect to the same server using SQL Server Management Studio and using server type Integration Services, everything works just fine.
However this way I cannot create a working SSIS package from the client, if not working locally on the server, which is a bit nonsense.
I am accessing a SQL2005 Express SP1 Server via TCP/IP (all machines fully up to date with windows update). For ease of configuration the Server IP is mapped to an Alias in Native Client Configuration Manager. On the Client Force Protocol Encryption is set to Yes and Trust Server Certificate is set to No. The clients are accessing the DB via SQL 2005 Management studio express and Ms Access 2003 (an access adp front end to the sql database).
As a test i turned off force encryption on the server. A Network trace shows no encryption! Turning on force encryption on the server corrects this.
As a further test I configured the server with a certificate the client doesn't trust. No error is generated by the un-trusted certificate! The only way to generate the certificate error is to enable encryption in the connection properties of each application. Why isn't the Native Client Configuration Manager utility enforcing this???
This brings me on to a second (off-topic problem). In my access adp file, if I enable €œuse encryption for data€? advanced option under the database connection dialog all works as expected (encryption + certificate verification). However, I am programmatically updating the connection in VBA
Application.CurrentProject.OpenConnection "Provider=SQLOLEDB.1;Data Source=AliasName;Use Encryption for Data=True;..."
If I do this no encryption is enabled!!! Access seems to just ignore the encryption statement.
Has anybody got any ideas as to why either of these issues are occurring or if there are any workarounds?
Starting the LogReader Agent produce the error 'Unable to start execution of step 2 (reason: Error authenticating proxy NETRTLSRVSvcSQLLogReader, system error: Logon failure: unknown user name or bad password.). The step failed.'
This is the result of the SQL Agent Error [298] SQLServer Error: 22046, Encryption error using CryptProtectData. [SQLSTATE 42000]
We are running SQL Server 2005 - 9.00.3042.00 (Intel X86) in a cluster environment.
If I change the Step 2 of the Agent Job (Type=Replication Transactional-Log Reader) to "Run AS" SQL Agent Service Account , everthing works fine.
There seems to be a problem with the access to the generated proxy/credential
Why it doesn't work with the special SvcSQLLogReader domain Login ?
I have created two user defined functions for encryption and decryption using passphrase mechanism. When I call encryption function, each time I am getting the different values for the same input. While I searching a particular value, it takes long time to retrieve due to calling decryption function for each row.
best way to encrypt and decrypt using user defined functions.Below is the query which is taking long time.
SELECT ID FROM table WITH (NOLOCK) Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â WHERE dbo.DecodeFunction(column) = 'value'
When I try to use symetric or asymetric encryption, I am not able to put "OPEN SYMETRIC KEY" code in a function. So, I am using PassPhrase mechanism.
I have created a DTS package on my SQL 7.0 SP3 server which simply reads a table on another SQL 7.0 server and populates a local table with the information that has been read.
Whenever I try to execute the DTS package (via Run or scheduling it) I get the following error:
------------------------------------------------------------------------- ... DTSRun: Executing... DTSRun OnStart: Delete from Table [AfterSalesAccessories].[dbo].[model_derivative] Step DTSRun OnError: Delete from Table [AfterSalesAccessories].[dbo].[model_derivative] Step, Error = -2147217887 (80040E21) Error string: The property 'Use Encryption for Data' is not supported. Error source: Microsoft Data Transformation Services (DTS) Package -------------------------------------------------------------------------
I have not selected the encryption option and can't see what I'm doing wrong. Has anybone else seen this ? I've looked on Technet but no joy.
Hello and thank you all in advance for any assistance provided. I have a two node SQL 2005 cluster running (1 node is failover). I have a job that I am trying to run using a proxy account. The credential account that is used within the proxy is a domain account and I have ensured that the passwords are all correct. The problem I am experiencing is that whenever I try to run a job, it fails with the following message:
Unable to start execution of step 1 (reason: Error authenticating proxy ROCHARR ("just an example"), system error: Logon failure: unknown user name or bad password.). The step failed.
This is also displayed in my SQLAGENT.OUT log file:
SQLServer Error: 22046, Encryption error using CryptProtectData. [SQLSTATE 42000]
In the event viewer, I also recieve failure audits when I run the job that look like this:
Logon Failure:
Reason: Unknown user name or bad password
User Name: ARR
Domain: ROC
Logon Type: 8
Logon Process: Advapi
Authentication Package: Negotiate
Workstation Name: HOSTA
Caller User Name: ITUSER
Caller Domain: ROCH
Caller Logon ID: (0x0,0x22EF57C8)
Caller Process ID: 5780
Transited Services: -
Source Network Address: -
Source Port: -
Now I have made sure that the "ITUSER" is trusted for delegation since that is the account that is running the SQL Server Agent Service. I have all the proxy settings configured correct in the job itself, so it shouldn't be that. Any assistance is greatly appreciated as I am going crazy with this.
I have a commercial application built for Pocket PC's that connects to SQL Server 2005 via TCP/IP over wireless networks. In installations for our sales people we installed SQL 2005 Express on their notebooks for demonstrations. In one of these installs we are getting the following error message: "An error occurred - SQL Server requires Encryption On". We do not use encrypted connections and I have verified encryption is turned off in the Options tab in SQL 2005 login screens.
Here is the connection string we use in the app.config file on the Pocket PC's: <add key="connStr" value="Data Source=192.168.0.19,1433;Initial Catalog=SQL0018;User ID = User01;Password=PW01"/>
Other apps on the notebook are connecting to this same SQL Server without any issues. Thank you in advance for any help here,
I have a commercial application built for Pocket PC's that connects to SQL Server 2005 via TCP/IP over wireless networks. In installations for our sales people we installed SQL 2005 Express on their notebooks for demonstrations. In one of these installs we are getting the following error message: "An error occurred - SQL Server requires Encryption On". We do not use encrypted connections and I have verified encryption is turned off in the Options tab in SQL 2005 login screens.
Here is the connection string we use in the app.config file on the Pocket PC's: <add key="connStr" value="Data Source=192.168.0.19,1433;Initial Catalog=SQL0018;User ID = User01;Password=PW01"/>
Other apps on the notebook are connecting to this same SQL Server without any issues. Thank you in advance for any help here,
I have a commercial application built for Pocket PC's that connects to SQL Server 2005 via TCP/IP over wireless networks. In installations for our sales people we installed SQL 2005 Express on their notebooks for demonstrations. In one of these installs we are getting the following error message: "An error occurred - SQL Server requires Encryption On". We do not use encrypted connections and I have verified encryption is turned off in the Options tab in SQL 2005 login screens.
Here is the connection string we use in the app.config file on the Pocket PC's: <add key="connStr" value="Data Source=192.168.0.19,1433;Initial Catalog=SQL0018;User ID = User01;Password=PW01"/>
Other apps on the notebook are connecting to this same SQL Server without any issues. Thank you in advance for any help here,
The following (VB.Net) code causes exceptions at seemingly random times. Any suggestions? Not sure if the problem is in .Net's ODBC support or in Sql Native Client.
If MARS is off, usually after less than 100 loops:
Code Snippet
System.Data.Odbc.OdbcException was unhandled ErrorCode=-2146232009 Message="ERROR [HY000] [Microsoft][SQL Native Client]Connection is busy with results for another command" Source="SQLNCLI.DLL" Turning MARS is on bypasses that error, so it will sometimes survive a thousand or so runs before hitting:
Code Snippet
System.Data.Odbc.OdbcException was unhandled ErrorCode=-2146232009 Message="ERROR [23000] [Microsoft][SQL Native Client][SQL Server]Cannot insert the value NULL into column 'Number', table 'tempdb.dbo.#TempTable___..(shortened to fit).. _________000000002F3F'; column does not allow nulls. INSERT fails. Source="SQLNCLI.DLL" Code here: (Console Application, empty database, Visual Studio 2005, .Net 2.0, Windows XP,SQL Server 2005 or SQL Express 2005, Local or Remote)
Code Snippet
Module Module1
Sub Main()
'Dim connection As New SqlClient.SqlConnection("database=TestDB;server=.sqlexpress;Integrated Security=SSPI;") 'Doesn't crash 'Dim connection As New OleDb.OleDbConnection("Provider=SQLNCLI;database=TestDB;Server=.sqlexpress;Trusted_Connection=yes;") 'Doesn't crash
'Dim connection As New Odbc.OdbcConnection("Driver={SQL Native Client};Database=TestDB;Server=.sqlexpress;Trusted_Connection=yes;") 'Crashes Dim connection As New Odbc.OdbcConnection("Driver={SQL Native Client};Database=TestDB;Server=.sqlexpress;Trusted_Connection=yes;MARS_Connection=yes") 'Crashes
VBMath.Randomize()
Dim run_count As Integer = 1 connection.Open() Console.WriteLine("Connected!!")
While True 'connection.Open()
Dim testcmd As New Odbc.OdbcCommand("CREATE TABLE [#TempTable] (Number int PRIMARY KEY)", connection) testcmd.ExecuteNonQuery() testcmd.Dispose() testcmd = Nothing
Dim dtTemp As New DataTable Dim daTemp As New Odbc.OdbcDataAdapter("SELECT * FROM [#TempTable]", connection) daTemp.MissingSchemaAction = MissingSchemaAction.AddWithKey daTemp.Fill(dtTemp) Dim cbTemp As New Odbc.OdbcCommandBuilder(daTemp) Dim viewTemp As New DataView(dtTemp, Nothing, "Number", DataViewRowState.CurrentRows)
Dim i As Integer For i = 1 To 1000 Dim test_number As Integer = CInt(Rnd() * 2000) If viewTemp.Find(test_number) = -1 Then 'Keep it unique Dim new_temp_row As DataRowView = viewTemp.AddNew() new_temp_row("Number") = test_number new_temp_row.EndEdit() End If Next
daTemp.Update(dtTemp)
'daTemp.Dispose() 'daTemp = Nothing
'cbTemp.Dispose() 'cbTemp = Nothing
'dtTemp.Dispose() 'dtTemp = Nothing
'viewTemp.Dispose() 'viewTemp = Nothing
Dim testcmd2 As New Odbc.OdbcCommand("DROP TABLE [#TempTable]", connection) testcmd2.ExecuteNonQuery() testcmd2.Dispose() testcmd2 = Nothing
'connection.Close() 'GC.Collect()
'Console.Write(".") run_count += 1 End While
End Sub
End Module
Usually the ".Update" triggers the exception, but sometimes the other sql commands do it. Have tried various experiments with disposing of objects immediately when finished, but no effect. Opening and closing the connection each loop seems to delay the errors, but it still happens eventually.
I have SQL 2005, and Reporting Service has been uninstalled and reinstalled, go through each step of confiugration until Encryption Key, for some reason, the backup button is grayed out, only "restore" button is clickable, as well as Delete, but we never backup the key before, so this is really strange since we do not have backupkey, so we cannot restore.
we tried "Delete", then we got the following error:
ReportServicesConfigUI.WMIProvider.WMIProviderException: The encrypted value for the "LogonCred" configuration setting cannot be decrypted. (rsFailedToDecryptConfigInformation) at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ThrowOnError(ManagementBaseObject mo) at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.DeleteEncryptedInformation()
Browse report manager and reportserver also got the same error, run rskeymgmt -d, does not help either
When trying to create a publication or subsubscription running under a Windows Domain account the following error message appears:
Replication-Replication Distribution Subsystem: agent ECHOECHO-InsDB-INS_CMS_PUB-HARPO-58 failed. Unable to start execution of step 2 (reason: Error authenticating proxy DETINIsrvRep_user, system error: Logon failure: unknown user name or bad password.). The step failed.
Further in the SQL logs we find that the above message is due to:
[298] SQLServer Error: 22046, Encryption error using CryptProtectData. [SQLSTATE 42000]
It appears that when Credentials for the agent proxy are being created that this message occurs. So when the SP that tries to run the agent (snapshot or distrobution) is called it always returns incorrect password details.
The Credentials do appear to be created, they are visible via SQL Studio, but you can't see the password. Changing the password via SQL Studio does not work as the Credentials are recreated every time.
I have checked the following:
MSDTC is running correctly The Domain Account has the correct privileges to run these services Regenerated the Service Master Key Created Master Keys in each database effected by replication Ensure SQL Service accounts have access to decrypt the Service Master Key I can create a Publication and Subscription using the local system account on the cluster
A customer of my program is getting the SQL CE error message "The operating system does not support encryption".
I've seen several threads on this issue, but none of them seem to apply to my problem. This is a Windows Forms application, so no device and no web service.
The OS is a German Windows XP - so there shouldn't be any issues regarding strong encryption. It even runs in Windows 2000 in our test VPC.
I've SQL Server Reporting Services 2005 configured on my system, but now I'm NOT Able to start the report server. I get this error on http://<serverurl>/Reports/Home.aspx:
The report server cannot decrypt the symmetric key used to access sensitive or encrypted data in a report server database. You must either restore a backup key or delete all encrypted content. Check the documentation for more information. (rsReportServerDisabled) (rsRPCError) Get Online Help
The report server cannot decrypt the symmetric key used to access sensitive or encrypted data in a report server database. You must either restore a backup key or delete all encrypted content. Check the documentation for more information. (rsReportServerDisabled) Key not valid for use in specified state. (Exception from HRESULT: 0x8009000B)
I don't want to loose any data. Please help me resolving this error.
FYI, I've modified the SQL Reporting Services account LogOnAs info, in Properties of "SQL Server Reporting Services (MSSQLSERVER)" Service, in Windows Service Managment.
Earlier I had .useraccount as username, I modified it to domainnameuseraccount. And then suddenlt everything broke for reporting server.
We have problems connecting ISQLW on 3 clients to a SQL server 7.0 databsae. The error is Server Error (No: 10040,Severity:9) - "DB-Library network communications layer not loaded". There are no errors from the client install. It works fine on 30 other clients and could be something to do with the build of these PCs.
In the SQL Client Configuration Utility the default network is TCP/IP but the library version and DLL both say 'Not Found' even though dbmsso3.dll is in c:windowssystem and c:mssqlin and the latter is on the client's path.
This has us stumped so if you have any suggestions then it would be very much appreciated.
I'm new in this forum and I 'm Italian, so my English won't be perfect!
If i want to connect to my SQL Server database in prompt i type:
"osql -U sa" and then i type the password. So, I get an error that says:
"[Sql Native Client] Provider Via: Impossible to find the specified module. [Sql Native Client] Access timeout expired [Sql Native Client] An error occured during the attempt to estabilish a connection to the server. During the connection to SQL Server this error may be caused by pre-defined settings that don't ......"
How i can solve this problem? Who can help me? Thank you!!
I'm new in this forum and I 'm Italian, so my English won't be perfect!
If i want to connect to my SQL Server database in prompt i type:
"osql -U sa" and then i type the password. So, I get an error that says:
"[Sql Native Client] Provider Via: Impossible to find the specified module. [Sql Native Client] Access timeout expired [Sql Native Client] An error occured during the attempt to estabilish a connection to the server. During the connection to SQL Server this error may be caused by pre-defined settings that don't ......"
How i can solve this problem? Who can help me? Thank you!!
Upgraded Enterprise Mgr. from SQL7 to SQL 20000. When trying to connect to SQl 2000 server using Enterprise mgr using TCP/IP am getting Invalid attribute/option identifier any suggestions???
I have developed a VS2008 .net application using Sql Server express 2005. Running this on my development machine works fine but after i deploy to a client machine i get:
Cannot open user default database. Login Failed for user 'mycomputernameadministrator'
The client machine has sqlserver express 2005 installed using all instllation defaults
My connection string is:
Data Source=.SQLEXPRESS;AttachDbFilename=c:mydatamyfile.mdf;Integrated Security=True;User Instance=False"
I want to be able to deploy my app to any client PC without any database user login (i use my own built in to app) or errors obvoiusly
Could someone give me a step by step to resolve, much appreciated
I have a VB 2005 synchronization application that successfully pulls (through RDA) data to a SQL 2005 Mobile DB at my place of business, but when I try it at home on my SSL VPN Client connection, I get Hresult -2147012889 ("A request to send data to the computer running IIS has failed."). Typically, a -2147012889 error is a connection issue that relates to resolving the server name.
Here's a snippet:
Dim RemoteConn As String = "Provider=sqloledb; Data Source={company server};" _
& "Initial Catalog={companyDB}; User ID={username}; password={pass}"
Dim SourceURL As String = "http://{Company server name}/MobileConnection/sqlcesa30.dll"
Dim SqlRA As New System.Data.SqlServerCe.SqlCeRemoteDataAccess
SqlRA.LocalConnectionString = strConn
SqlRA.InternetUrl = SourceURL
SqlRA.InternetLogin = ""
SqlRA.InternetPassword = ""
SqlRA.CompressionLevel = 3
Try
(Perform Pulls...etc..)
When I pull the sourceURL string and plug it into IE, it works fine. I get the "SQL Server Mobile Server Agent 3.0" message indicating that I have a solid connection over to IIS. That works fine.
But I can't figure out anything in the program. I've rotated the IP address with the name resolution and neither works for me in the program. The difference though when I use the IP address for the server is that I get a slightly different Hresult of -2147012867 (which means you can't connect to the server).
Also, I have IIS configured for anonymous access, the SQL DB I'm trying to pull from isn't restricting access, and my company doesn't have a proxy I need to go through.
I've written a small VB .Net app using Visual Studio 2005 to test mirroring from the client's perspective.
I have a button that does the following: 1) opens a connection to a sql 2005 database (SP2), 2) uses the connection, 3) closes the database connection.
After running this code, but while the client app is still running, I failover the database to the failover partner.
When click my button again, I get the following error: "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)". Checking the Event log on what is now the mirror, I see a string of "18456 Login failed for user 'testuser'"
If I close the app and launch it again, it does the right thing (and connects to the new primary). Also, instead of closing/re-opening the app, if I wait long enough (e.g. 10 minutes), then try again, it connects successfully to the new primary. Finally, instead of closing/re-opening the app if I tweak the connection string (e.g. change the application name) then try to connect again, that also works.
Based on articles I've read online, I've disabled the connection pool in my connection string, but that didn't solve my problem (although I'm getting a different error than if pooling is on).
Here is the connection string I am using:
Data Source=DB1PACS,12345;Failover Partner=DB2PACS,12345;Pooling=False;Initial Catalog=PACSTest_Client;Integrated Security=No;User ID=testuser;Password=*****
Here is the code snippet that I run before and after the failover. Based on the fact that I'm not using Pooling, the ClearAllPools() if overkill. Any help would be appreciated; I've been researching this for days without luck.
I can keep clicking the button that runs this code, and it keeps failing. If I wait long enough (e.g. 10 minutes) and then click the button again, it works. Or I could quit/restart the app, or tweak the connection string.
Dim TestClient_Connection As New SqlClient.SqlConnection(txtConnectionString.Text)
If Me.DataGridView1.Rows.Count > 0 Then Me.Test_ClientDataSet.Clear()
Similar to the JDBC driver article I mentioned, when using the connection string above (where DB1 is the principal and DB2 is the failover partner) if DB2 is the actual principal when I initially query and close the database connection, then after failover to DB1 my application reconnect just fine.