Devart Forums

hsldev

Bump... any suggestions gratefully accepted!

hsldev

Hi,

I am trying to disable TLS 1.0 & 1.1 when using TMSConnection. Currently we are using the (default) SQL OLEDB provider which only supports up to TLS 1.0. I found documentation on this site that suggests I need to configure TMSConection to instead use the SQL Native Client provider, which supports TLS 1.2 using the following code:

connection.Options.Provider := prNativeClient;

I have done this, and installed 'Microsoft SQL Server 2012 Native Client', however, I still receive the error 'Required provider is not installed' when connecting to the database. Using RAD Studio 2007 and Windows Server 2012 R2.

Can you please advise how to fix this issue.

Thanks,
John

hsldev

Hi,

I am revisiting this issue now as we are at a point where we really need our product to support 64-bit.

I was encouraged to see that the latest version of SDAC 6.6 supported 64 bit and was hoping this didn't just refer to support for Win32 but alas it appears to be, because testing 6.6 under the same scenarios i did above over a year ago produced the same result.

Are you please able to confirm this is the case and if there are any plans to support this at some time?

Regards,

hsldev

dotConnect sounds great but that isn't going to help us with our 10,000 line delphi library (using SDAC) that we aren't going to be rewriting any time soon.

We need this library for our win32 application and now we wish to use it with a 64-bit .NET application which doesn't sound unreasonable given delphi can produce "Any CPU" or even "x64" IL for .NET.

The .NET SDAC libraries must be compiled with a target of "Any CPU" otherwise the 64-bit application would fail trying to bind the DLLs. Perhaps you should specify the .NET SDAC libraries with a target of "x86" if you aren't going to support 64-bit so that there can be no confusion.

Regards,

hsldev

Hi,

Thanks for the prompt reply, though I must say I don't fully agree with your answer.

I created my code sample to very simply describe the issues we are having with our product in trying to use Delphi 2007 .NET DLLs (that use SDAC) with a VS 2010 project, but perhaps by trying to oversimplify my example I made it a little misleading.

I was able to duplicate my example as a Delphi 2007 .NET console application and setting the target platform as x64 was again able to get the overflow exception. I can email you this code sample as well if you like?

I realize that Delphi itself does not have a 64-bit compiler, but by virtue of Delphi 2007 being able to dual compile code in Win32 and/or .NET, and .NET projects being able to target 32-bit or 64-bit platforms, Delphi does indirectly support x64 and I believe supporting 3rd party components should as well.

Regards,

hsldev

Hi,

We have found an issue using the SDAC .NET DLLs when referenced in a visual studio 2010 (.NET 3.5) project that has a target platform of 64-bit.

The exception is
"System.OverflowException: Arithmetic operation resulted in an overflow."
It appears this was raised in the below post but no solution was added.
http://www.devart.com/forums/viewtopic. ... e6a8be1f3e

We are using version 4.35.1.5016 of the SDAC components but I downloaded the latest trial version (5.x) and the same exception occurred.

I have a very basic demo project that I'm happy to send you, but it basically looks like this...

Code: Select all

using System;
using CoreLab.Sdac;

namespace DevArtSdacTest
{
    class Program
    {
        static void Main(string[] args)
        {
            try
            {
                Console.Write("Please enter the database server: ");
                string server = Console.ReadLine();

                TMSConnection c = new TMSConnection(null);
                c.Authentication = TMSAuthentication.auWindows;
                c.Server = server;
                c.Database = "master";
                c.Connect();
            }
            catch (Exception e)
            {
                Console.WriteLine(e.ToString());
            }
            Console.ReadLine();
        }
    }
}

Any help would be greatly appreciated!

Regards,

hsldev

Hi there,

We are having the same problem above running a .NET app on windows server 2008r2 (64-bit) and was happy to see this post, but then sad to see there was no resolution on here!

I presume you were able to solve the issue and advised this person by email, but could you post the resolution as well for others who then have the same problem?

Regards,

hsldev

Hi,

We currently have a threaded application that is returning this error.

"TOLEDBCommand.Destroy - interfaces not released (1) (D:\Projects\Delphi\Sdac\Source\OLEDBAccess.pas, line 2515)"

We realise that it is probably something we are not doing correctly in the threaded environment, but we cannot see anything untoward. Eureka log tells us that this seems to be happening on freeing up a data module containing sever TmsStoredProc's that we create inside the thread. We are not really sure where else to look.

The error occurs only intermittently at client sites and we haven't been able to reproduce it in a test app.

Details:
Windows XP SP2
SQL Server 2005
Delphi 5.01
SDAC 3.80.0.36

Matt

Devart Forums

Search found 8 matches

Re: Required provider is not installed

Required provider is not installed

Re: .NET 64-bit exception

.NET 64-bit exception

TOLEDBCommand.Destroy - interfaces not released (1) (D:\Projects\Delphi\Sdac\Source\OLEDBAccess.pas, line 2515)