Hi Tom,

The current 4D version at the client’s site is v15.
Through the various versions of upgrade from v11 to 13 to 15, there has not 
been an issue with the SQL connection.

I suspect it could be some GPOs that were pushed down….so the subsequent 
investigation are narrowing down to that.

Regards,
Ronnie
Tarawerkz




> On 16 Sep 2019, at 2:13 PM, Tom Benedict <[email protected]> wrote:
> 
> Hi Ronnie,
> 
> My suspicion is that something around SSL on the external DB has changed. 
> Perhaps your app uses a version of 4D which supports TLS 1.0 and the external 
> DB was changed to use TLS 1.2? Or maybe the other way around? Just a guess.
> 
> Here’s 4D Tech Tip which can help determine what version of TLS your app 
> uses:  http://kb.4d.com/assetid=76175 <http://kb.4d.com/assetid=76175>
> 
> Tom Benedict
> 
>> On Sep 15, 2019, at 22:04, Tarawerkz via 4D_Tech <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> Hi All,
>> 
>> Need some help on a SQL connection issue….
>> 
>> A script that has been to access an SQL database (been deployed for years) 
>> has suddenly stopped working and threw up the following error :
>> 
>>      Error - [DBNETLIB][ConnectionOpen (SECCreateCredentials()).]SSL 
>> Security error
>> 
>> 
>> In the cause of debugging, I tried a simple one-line SQL login command as 
>> follows :
>> 
>>      SQL Login(“IP:10.240.99.99”;$username;$password”;*)
>> 
>>      SQL Login(“IP:10.240.99.99:1433”;$username;$password”;*)
>>      SQL Login(“IP:10.240.99.99:1433:ssl”;$username;$password”;*)
>> 
>> They all resulted in 4D Syntax error that indicates a failure to connect to 
>> remote server, with a SQL error 9918, Generic SQL error
>> 
>> Where has it gone wrong?  Thank you for any advise.  
>> 
>> 
>> Regards,
>> Ronnie
>> Tarawerkz
>> 
> 

**********************************************************************
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[email protected]
**********************************************************************

Reply via email to