I am trying to connect runtime to a Microsoft SQL server using integrated security (window service is running with a dedicated AD account). It work fine with the SQL account but not with window.
Changes made on runtime are: updated engineparameter.xml, changed JDBC connection string, removed SQL login, removed SQL password, copied sqljdbc_auth.dll, copied sqljdbc42.jar and restarted window. But it doesn't made it work.
Here is the error found in "com.indy.engine.42000.log": ERROR - Error during Log initialization
com.indy.engine.common.exceptions.EngineExceptionI: Problems getting the log parameters
Best Answer
G
Gaurav Srivastava
said
about 2 years ago
- Leave below parameters in Engineparameter with the empty value "".
<parameter name="userLogRdbmsUser" value=""/>
<parameter name="userLogRdbmsPassword" value=""/>
- Check if we can able to setup a connection from another java-based Query tool (dbeaver, squirrel...) using the same integratedSecurity connection mode.
- Removed all sqljdbcxx.jar files from the server, except the one in Runtime\lib\jdbc.
- Removed all sqljdbc_auth.dll from the server, except the one in Runtime (next to the startengine.bat file).
The sqljdbc42.jar used by the designer and local runtime wasn't the same (same name but different file size). I replaced with the one from qual/prod environment and placed the sqljdbc_auth.dll next to Stambia.exe -> everything works fine.
1 Comment
G
Gaurav Srivastava
said
about 2 years ago
Answer
- Leave below parameters in Engineparameter with the empty value "".
<parameter name="userLogRdbmsUser" value=""/>
<parameter name="userLogRdbmsPassword" value=""/>
- Check if we can able to setup a connection from another java-based Query tool (dbeaver, squirrel...) using the same integratedSecurity connection mode.
- Removed all sqljdbcxx.jar files from the server, except the one in Runtime\lib\jdbc.
- Removed all sqljdbc_auth.dll from the server, except the one in Runtime (next to the startengine.bat file).
The sqljdbc42.jar used by the designer and local runtime wasn't the same (same name but different file size). I replaced with the one from qual/prod environment and placed the sqljdbc_auth.dll next to Stambia.exe -> everything works fine.
Gaurav Srivastava
I am trying to connect runtime to a Microsoft SQL server using integrated security (window service is running with a dedicated AD account). It work fine with the SQL account but not with window.
Changes made on runtime are: updated engineparameter.xml, changed JDBC connection string, removed SQL login, removed SQL password, copied sqljdbc_auth.dll, copied sqljdbc42.jar and restarted window. But it doesn't made it work.
Here is the error found in "com.indy.engine.42000.log": ERROR - Error during Log initialization
com.indy.engine.common.exceptions.EngineExceptionI: Problems getting the log parameters
- Leave below parameters in Engineparameter with the empty value "".
<parameter name="userLogRdbmsUser" value=""/>
<parameter name="userLogRdbmsPassword" value=""/>
- Check if we can able to setup a connection from another java-based Query tool (dbeaver, squirrel...) using the same integratedSecurity connection mode.
- Removed all sqljdbcxx.jar files from the server, except the one in Runtime\lib\jdbc.
- Removed all sqljdbc_auth.dll from the server, except the one in Runtime (next to the startengine.bat file).
The sqljdbc42.jar used by the designer and local runtime wasn't the same (same name but different file size). I replaced with the one from qual/prod environment and placed the sqljdbc_auth.dll next to Stambia.exe -> everything works fine.
Gaurav Srivastava
- Leave below parameters in Engineparameter with the empty value "".
<parameter name="userLogRdbmsUser" value=""/>
<parameter name="userLogRdbmsPassword" value=""/>
- Check if we can able to setup a connection from another java-based Query tool (dbeaver, squirrel...) using the same integratedSecurity connection mode.
- Removed all sqljdbcxx.jar files from the server, except the one in Runtime\lib\jdbc.
- Removed all sqljdbc_auth.dll from the server, except the one in Runtime (next to the startengine.bat file).
The sqljdbc42.jar used by the designer and local runtime wasn't the same (same name but different file size). I replaced with the one from qual/prod environment and placed the sqljdbc_auth.dll next to Stambia.exe -> everything works fine.
-
Set webservice password dynamically in XDI
-
Unable to use "PATCH" as HTTP verb in a REST API call
-
Microsoft SQL server "Could not establish a secure SQL Server connection using SSL encryption"
-
how to import SQLITE database
-
Chiffrement de fichier
-
Azure Service Bus - possible to connect to a topic?
-
Export Log
-
Error HttpRest metadata when reversing API
-
API key authentication instead of basic authentication
See all 15 topics