Problem:
Could not open SQL Database!
Make sure IPSClient is running.
Idealpos will now shut down.
SSL Provider: The client and server cannot communicate because they not posses a common algorithm.
---2147467259
Could not open SQL Database!
Make sure IPSClient is running.
Idealpos will now shut down.
[DBNETLIB}{ConnectionOpen (SECDoClientHandshake()).]SSL Security error.---2147467259
This can also manifest itself with the following error when attempting to access Setup > Licence Gateway:
System.ServiceModel.Security.SecurityNegotiationExceptions: Could not establish secure channel for SSL/TLS with authority 'services.idealpos.net'.
The request was aborted: Could not create SSL/TLS secure channel.
Cause:
This was identified at Cater Care (All Divisions)
They have recently done a security audit and part of that auditing program has disabled TLS 1.0 and TLS 1.1 in the registry.
The program that they are using is CYRISMA Sensor version 2.5 by Dataspotlite Inc.
Cater Care's IT Services have been requested to stop patching these servers.
Solution:
- Modify the registry for Client and Server under the TLS 1.0 and TLS 1.1 keys and set the Enabled REG_DWORD to 1.
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server
- Restart the system or restart the running SQL services
Log Entries:
These can vary, I think depending if a close suite has been performed or database maintenance or housekeeping schedule or a restart or attempted re-installation of either Idealpos or SQL.
Some entries are as follows.
V8
IPSError.log
20240411 04:55:48.985 2h 51m 42s SQLOpenConnection : [DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error.---2147467259
20240411 04:55:48.032 2h 51m 42s DbSupport.GetADORecordSet on Line: 124 Error: 3709 - The connection cannot be used to perform this operation. It is either closed or invalid in this context. = SELECT * FROM DatabaseMaintenancePlans 3709-The connection cannot be used to perform this operation. It is either closed or invalid in this context.
IPSError.log
20240411 00:02:54.417 21h 26m 45s Error in Receive Packet Line 370 : Shared Memory Provider: No process is on the other end of the pipe.
: -2147467259
20240411 00:03:09.432 21h 27m 0s OpenIPSTerminalADO : SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. ---2147467259
20240411 00:03:09.432 21h 27m 0s OpenIPSTerminalADO : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.---2147467259
20240411 00:03:09.432 21h 27m 0s OpenIPSTerminalADO : Login timeout expired---2147467259
V7
IPSError.log
20240412 10:20:23.303 0h 3m 10s DbSupport.GetADORecordSet on Line: 112 Error: 3709 - Requested operation requires an OLE DB Session object, which is not supported by the current provider. = SELECT * FROM NETWORKPRINTERS WHERE SITE = 0 3709-Requested operation requires an OLE DB Session object, which is not supported by the current provider.
20240412 10:20:28.352 0h 3m 15s SQLOpenConnection : [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified---2147467259 TimeTaken=0
The yellow highlighted lines may not be the same, I assume this is one of the first queries that is being run by Idealpos upon attempted opening.