In some cases, SQL Server will require windows authentication as opposed to SQL Authentication with a username and password.
This requires two configuration steps on the server where the agent is running in order to support this authentication using the MSSQL JDBC. However, this configuration only needs to be done once.
Part I: SQL Auth DLL
In order for Integrated Security to work, the appropriate DLL file must be placed on the server running the agent, at a location that the JDBC can access it, along the java.library.path. Microsoft provides a downloadable .exe extractor file that contains the appropriate files here:
Note: the plugin uses the v6.4 JDBC
Once downloaded, run the executable and specify a folder for the tool to extract.
Navigate to the extracted directory
Select the auth directory
Select the x64 directory
Copy the sqljdbc_auth.dll file - this is the file that will allow the plugin to use Windows Authentication
Paste the file in C:\Windows\System32\ - you will be prompted to approve this transfer as an administrator
Part II: Service User
After you have configured the agent to run as a service, you will need to set the service to run under a specific user or service account that has access to that network drive resource.
Find your service in Services
Right-click on the service and select Properties
3. Go to the Log On tab and select “This account” and then Browse…
4. Select Advanced…
5. Select Find Now. This will give you a list of the users on the machine; select your user account and press OK
6. Enter in and confirm the password you use to log into the machine, then click Apply
7. A warning dialog will pop up granting the access the rights to run as a service and/or that the service will have to be restarted. Click OK on these.
8. Right-click on the service you created during the Gateway agent installation and select Restart