Choose "With SQL Server authentication using a loging ID and password entered by the user" and use the 'sa' user and password.Ĥ. Here you should be prompted with an option to use "With Integrated Windows authentication" or "With SQL Server authentication using a loging ID and password entered by the user".
After confirming the SQL server connection strip and DSN Name click "Next >' button. On the System DSN tab ensure the 32 bit system ODBC DSN name used in the CIMPLICITY project is using the SQL Native Client version that corresponds to the Version of SQL server connecting to.ģ.Go to the System DSN tab and select the 32 bit system ODBC DSN name used in the CIMPLICITY database logger and click the 'Configure' button.
#COMPARE SQL ON MAC 32 BIT#
In old Windows version the 32 bit snap-in can be found in C:\Windows\SysWOW64\odbcad32.exeĢ. In WIndows 10/2016 and higher the 32 bit system ODBC DSN configuration snap-in can be found in Windows Control Panel->Administrative Tools->ODBC Data Sources (32-bit). Open the 32 bit system ODBC DSN configuration snap-in. Please review Microsoft MSDN for support on reviewing and configuring SQL mixed mode authentication.ġ. However, if the SQL server was installed manually this may not have been configured at the time of the installation.
#COMPARE SQL ON MAC INSTALL#
The CIMPLICITY install media will install with mixed mode authentication. NOTE: SQL Server must be configured with mixed mode authentication. Solution 1 - SQL Authentication (GE Supported cfg)Ĭonfigure the 32 bit system ODBC DSN connection to use SQL authentication with 'sa' user and password instead of Windows authentication. SYSTEM is not meant to be used for remote connections by default in both the Windows and SQL security models which restricts the CREATE TABLE rights in the SQL server By default the 'CIMPLICITY HMI service' uses the SYSTEM account on the local computer. When the process in question is the CIMPLICITY Database logger this will be the security context of the 'CIMPLICITY HMI service' (CMD->services.msc) that is running the CIMPLICITY project. When using Windows authentication configured in the 32 bit system ODBC DSN connection the SQL server will authenticate to the Windows Security context of the process making the SQL query. Primary Product Module : Data Logger - SQL NOTE: Error messages can vary depending upon database name, ODBC cfg, CIMPLICITY Database logger cfg, and SQL/Windows Security policies. 10:58:20 AM Failure 7084 MAC_PTDL odbc_connect 0 10:58:20 AM Warning 7084 MAC_PTDL PTMAP_send_sl 0Įrror of type: COR_PTMAP_ERR, Code: 25021 (42000) Cannot open database "CIMPLICITY" requested by the login
#COMPARE SQL ON MAC DRIVER#
Unable to connect to ODBC driver $LOGGING 10:58:09 AM Failure 6740 MAC_DL odbc_connect 0 When the CIMPLICITY project starts and the Database Logger Creates tables for the first time the following error/s can be found in the project status log (cor_recstat.clg/cl2).
CIMPLICITY Database Logger is configured to log to a remote SQL server using a 32 bit system ODBC DSN connection that is configured for Windows authentication to the remote SQL server.