![]() Edit the "ConnectionString" value and replace "SQLOLEDB" with "SQLNCLI11".ĪdTempus should now be able to connect to the database.The SQL Server Native Client can be installed as part of the SQL Server 2012 Feature Pack and is also included in other SQL Server packages from Microsoft. Edit the "ConnectionString" value and replace "SQLOLEDB" with "MSOLEDBSQL".ĪdTempus should now be able to connect to the database.Run the Registry Editor and go to key "HKEY_LOCAL_MACHINE\Software\Arcana Development\adTempus\Database".Then configure adTempus to use this driver: Install the Microsoft OLE DB Driver for SQL Server on the adTempus server. Note: This driver may not be available for older operating systems (e.g., Windows Server 2008). Option 1: Microsoft OLE DB DRIVER for SQL Server Two new drivers are available, and one or both may already be on your server. To resolve this problem you must install a different database driver on the computer, and configure adTempus to use that driver. This happens because the SQL Server OLEDB database driver that adTempus uses by default does not support TLS 1.2. Don't forget to change the connection string. I don't know the ODBC version numbers by heart, but you can always download and install the most recent ODBC driver which is ODBC 17. (-2147467259 native error=18 SQL state=08001) Cause The most likely this is a TLS issue where one component uses TLS 1.0 and the other wants TLS 1.2. After SSL 3 and TLS 1.0 are disabled on the adTempus server or your database server, the adTempus service fails to start and logs an error message similar to the following:ĬonnectionOpen (SECCreateCredentials()).]SSL Security error. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |