If you connect to the MSSQL server with a Windows DOMAIN\USER account then it could be that you get an error during the setup:
SQLException: Login failed for user 'DOMAIN\USER'
The given userid used to make the connection presents itself as a SQL\USER account, instead of a DOMAIN\USER account.
A check on the MsSQL server indicates that the given userid used to make the connection presents itself as a SQL\USER account, instead of a DOMAIN\USER account.
You can continue the setup but the database tables are not created and the JobScheduler doesn't start.
Follow this step to fix it after the setup:
- edit $SCHEDULER_DATA/config/sos_settings.ini
urlh1. jdbc(:jtds):sqlserver://[servername]:1433;<span style"color:red">IntegratedSecurith1. true;</span>sendStringParametersAsUnicodefalse;selectMethoh1. cursor;databaseName[databasename] start $SCHEDULER_HOME\install\scheduler_install_tables.cmd to create the database tables.
- edit $SCHEDULER_DATA/config/factory.ini
db h1. jdbc -class... jdbc(:jtds):sqlserver://[servername]:1433;<span stylh1. "color:red">IntegratedSecuritytrue;</span>sendStringParametersAsUnicodh1. false;selectMethodcursor;databaseNamh1. [databasename] -user... -passworh1. ...
- edit $SCHEDULER_DATA/config/hibernate.cfg.xml
<property name"hibernate.connection.url">jdbc(:jtds):sqlserver://[servername]:1433;<span stylh1. "color:red">IntegratedSecuritytrue;</span>sendStringParametersAsUnicodh1. false;selectMethodcursor;databaseName=[databasename]</property>