Saviynt unveils its cutting-edge Intelligence Suite products to revolutionize Identity Security!
Click HERE to see how Saviynt Intelligence is transforming the industry.
Saviynt Copilot Icon

Internal Server Error - SFTPFileTransfer Connector

ybharadwaj319
New Contributor III
New Contributor III
Hi Team,
 
We are trying to create SFTPFileTransfer connector type and we enabled the microservices config for "Enhanced Connector Framework" under Microservices section.
But when we try to change the value to True under the "Enhanced Connector Framework" at the connector type level, we are facing Internal Server Error as below.
 
ybharadwaj319_0-1720195765985.png

We see the below in the logs:

Error Logs:
"Date Timestamp (UTC)","Service Name","Class Name","Thread Name","Log Level","Message"
"2024-07-05T12:06:30.720+00:00","gateway","o.s.b.a.w.r.e.AbstractErrorWebExceptionHandler","reactor-http-nio-1-4wns5","ERROR","[191988a3-17136]  500 Server Error for HTTP POST "/ECMv6/api/connectorms/test"|java.net.UnknownHostException: Failed to resolve 'connectorms' [A(1)] after 2 queries |    at io.netty.resolver.dns.DnsResolveContext.finishResolve(DnsResolveContext.java:1088) ~[netty-resolver-dns-4.1.92.Final.jar!/:4.1.92.Final]|    Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException: |Error has been observed at the following site(s):|    *__checkpoint ⇢ org.springframework.cloud.gateway.filter.WeightCalculatorWebFilter [DefaultWebFilterChain]|    *__checkpoint ⇢

Can anyone review and suggest or should we raise a ticket with Saviynt to fix this?

Please note that we recently moved to v24.5 and have never tested this in previous versions.

Regards,

Bharadwaj Y.

[This message has been edited by moderator to mask sensitive information]

2 REPLIES 2

rushikeshvartak
All-Star
All-Star

Please raise support ticket for this


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

ybharadwaj319
New Contributor III
New Contributor III

I raised a ticket with Saviynt simultaneously to this post, and it was resolved by them.

The issue was "Microservice for connector was on unhealthy/hung status", which was resolved upon Saviynt restarting the service.

Regards,

Bharadwaj Y.