Skip to main content

Hi all,

We’re trying to adjust our file senders on our new 23R2 IFS CLOUD on prem environment.

We were told that within IFS CLOUD Frontend its sufficient to add the Windows AD Credentials of a Domain User who access to that Share on the sender itself:

 

 

 

The Windows AD user which is being used, has definitely the appropiate rights to access the defined Windows Share, but when a write operation is being executed, like e.g a “Supplier Payment Order” then within IFS Connect “Application Messages” it can be seen, that the Access is denied:

ExecutionException from Sender thread 
Caused by: ifs.fnd.connect.senders.ConnectSender$TemporaryFailureException: Error while sending data to file 
Caused by: jcifs.smb.SmbAuthException: Access is denied.

Since our Windows File Server is setup as a DFS, we thought maybe our on-prem IFS CLOUD Ubuntu Middle Tier needs lacks the ability to communicate with a DFS server, even though DFS should work with SMB.

The file server “//servername.domain.ch/Temp$” itself can be mounted and accessed on OS level of the IFS CLOUD Middletier Server.

But once in IFS CLOUD Frontend: no matter which Share notation or username (SAM Accountname & UPN) is being used, the “access denied” message remains for any Sender write operations.

 

→ Has anyone been confronted with that issue or could point into the right direction?

Hello @cgo ,

From 23R1 some new network policies are added file so for doing the setup in 23R2 you need to do the respective setup in the ifscloud-values.yaml file.


From 23R2 you will observe that default value for networkpolicy.enabled is set to true.

ifscore.networkpolicy.enabled | Set to true to activate network policy | default: true


As per the 23R2 configuration -

Link -https://docs.ifs.com/techdocs/23r2/070_remote_deploy/010_installing_fresh_system/200_installing_ifs_cloud/035_ifs_cloud_ifsinstaller/030_installation_parameters/#general_parameters


Please follow the above documents and configure the parameter accordingly.


Also please check the password policy for the user you are trying.

Thanks,
Hardik

 

Hi @hardik 

Thank you for your feedback

Unfortunately adjusting “ifscore.networkpolicy” Key didn’t have any effect.

 

The Problem was, that the Routing Addresses had the %FILE_OUT% präfix attached.
Our IFS Cloud DB is a copy from IFSAPP10, where this was the correct from. In IFS Cloud it seems %FILE_OUT% has no use anymore.

After removing %FILE_OUT% we had the following application error message when using our DFS share in the file sender:

ExecutionException from Sender thread 
Caused by: ifs.fnd.connect.senders.ConnectSender$TemporaryFailureException: Error while sending data to file 
Caused by: jcifs.smb.SmbException: Failed to connect to server 
Caused by: java.net.UnknownHostException: <servername>

It seems that the ifsconnect POD isnt able to resolve the DFS / <servername>  properly, even though the Middle Tier Host can.

After replacing the DFS share with the FQDN of the server, the file transfer worked.

Reply


Terms & ConditionsCookie settings