I am trying to fetch data from remote windows server using SQL Loader Connector.
Server Name: sv-12345.devsrv.rem.local
File Location: D:\Path1\test.csv
In SQL Loader Connector, details added are:
Datafile URL: jdbc:csv:https://sv-12345.devsrv.rem.com/Path1
Test Connection SQL Query: SELECT first(‘EmpId’) FROM Test
IIS was not configured in the server, hence I configured the IIS on the server and opened the https on port 9443. Also, I installed the server certificate on IIS.
However, when I try to do a test connection, I get the error:
We have detected an error from the managed system.
Error Received:
[ ConnectionFailedException ] [ Possible suggestions ] Verify that Connection User and Password are correct. [ Error details ] Error occurred while establishing the connection with Data File during test configuration operation. Failed to load table Test: java.io.IOException: https://*:*@vsv-12345.devsrv.rem.com/Test.csv
I have tried combinations for URL including replacing the server with IP address, but still get the same error:
For this URL to work, you would have to have D:\ set as the wwwroot folder for your IIS server. Normally, the folder is something like C:\inetpub. Try moving your file test.csv to that folder.
Hi Alicia,
I read your response to another question on SQL Loader connecter, moved the test.csv file to the location C:\inetpub, continue to get the same error.
I am not familiar with IIS configurations required to access the file, do you have any thoughts on weather this looks correct:
From your screenshot, as long as the folder D:\Path1 matches the configuration of your IIS sqlloadfiles path that you crossed out. If your test.csv is in the D:\Path1 folder, then your URL in the SQLLoader configuration would be https://sv-12345.devsrv.rem.com/
I do notice is that your urls are different. For the server name, you say:
sv-12345.devsrv.rem.local
But for the sql loader url, you say:
sv-12345.devsrv.rem.local
Two things to try:
Go to the VA, use the command nslookup to verify which of these values will translate to an IP address.
nslookup sv-12345.devsrv.rem.local
Use the curl command from the VA to make sure that you can access the file
curl https://sv-12345.devsrv.rem.local/
The other thing I noticed from your screenshot on IIS is that your Default IIS configuration is showing that you are running on port 9443. Are you running on 9443 for your sqloadfiles as well? If so, you would need to add it to the url like https://sv-12345.devsrv.rem.local:9443/
curl sv-12345.devsrv.rem.local --output ss.csv => Upon reading the ss.csv file, I see the below text:
“Description: Unable to locate the server named “sv-12345.devsrv.rem.local” — the server does not have a DNS entry. Perhaps there is a misspelling in the server name, or the server no longer exists. Double-check the name and try again”
I am able to see the files mapped via IIS in local browser and download it. However, the error remains same during test connection, below is what I see in VA logs.
Thanks for the pointer, the issue with CURL command has been resolved. However I still face issue with connectivity and error is still same in IDN. Anything else that might be blocking?
As VA is managed and maintained by Sailpoint, and as VA has always been connected, I assume it is updated. Is there something specifically suspicious that hints at invalid CCG Version?
JDBC had a connection error recently, and was rectified by a CCG update, the errors you’re facing are similar to the ones experienced with an outdated CCG. In order to test this it would be best to try and create a simple JDBC connector in Java and test you can access the database from there. If you are able to with the same credentials then it will most likely just be a connector error.
After some further research, it could be that the user account you are using does not have read access to the “Path1” folder, which would explain the username and password error even though you are using correct details. Could you please check this by right clicking the folder, clicking security and adding read permissions on the user.
It took some time to figure out the issue, but could finally resolve it.
The VA is configured with Proxy. So, even after opening the firewall and ports, the requests were flowing via the Proxy server instead of the VA. As a resolution, I added the Proxy server IP in the proxy.yaml file, and aggregation started working like charm!
Thanks to all the community members for help and inputs. In case you have additional questions on this issue, ping me.
