Hi @Thejaswini ,This error seems to be getting due to the incompatible algorithm.Below are the key-exchanges, Host Keys, and cipher suites supported by IFS SFTP Connectors:• SSH2 protocol support.• Key exchange: diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha256,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521• Cipher: blowfish-cbc,3des-cbc,aes128-cbc,aes192-cbc,aes256-cbc,aes128-ctr,aes192-ctr,aes256-ctr,3des-ctr,arcfour,arcfour128,arcfour256• MAC: hmac-md5, hmac-sha1, hmac-md5-96, hmac-sha1-96• Host key type: ssh-dss,ssh-rsa,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521• Userauth: password• Userauth: publickey(DSA,RSA,ECDSA)• Userauth: keyboard-interactive• Userauth: gssapi-with-micConfirm above types are compatible with your SFTP server. Thank you,Aswin.
Hi @MUNAJANSE , Yes, you can troubleshoot the workflow by passing sample data to the workflow using the Inspect option available to debug the flow.Please refer the below documentation for further information. https://docs.ifs.com/techdocs/23r2/040_tailoring/500_business_process_automation/040_workflow_tooling/#troubleshooting Thank you,Aswin.
Hi @jamie.malangyaon , Batch_Sys.Fnd_Heavy_Cleanup_ - Heavy Cleanup is a scheduled cleanup job which must run once a night. (Usually scheduled to run at 12 Midnight). The job will remove data from Print Jobs, Archived Print Jobs, History log data, Scheduled Tasks and Event messages.This job shouldn’t be scheduled to run during the peak hours. Could you please check the time it has been scheduled.For further details on scheduled jobs, please refer the below documentation.https://docs.ifs.com/techdocs/foundation1/020_installation/020_installing_fresh_system/050_initial_system_configuration/007_background_processing/020_configure_scheduled_tasks/default.htm Thank you,Aswin.
Hi @feng , If the URL end point of a HTTP or REST routing address is secured and the SSL certificate of the relevant URL is not a trusted one, the SSL certificate can be uploaded through Routing Address view. If the SSL certificate is available for a routing address, a runtime keystore will be created with the uploaded certificate when connecting with the URL. This will ensure the secure communication between application and the URL end point. https://docs.ifs.com/techdocs/23r1/030_administration/030_integration/300_ifs_connect/030_routing_rules_addresses/#uploading_ssl_certificate I’ll update you on further details. Thank you,Aswin.
Hi @didous , The error message is missing. Could you please attach it. Thank you,Aswin.
Hi @ebruirmakk, You can try out a full Application reconfiguration and check whether the error message is still there. Please refer the below documentation for more details on application reconfiguration. https://docs.ifs.com/techdocs/foundation1/040_administration/400_core_server/010_middle_tier/010_middleware_server/005_reconfiguration_and_administration/010_reconfiguration/default.htm Thank you,Aswin.
Hi @NickPorter , Yes, deleting the IAM user is the correct approach when you do any changes in the IDP configuration. Thank you,Aswin.
Hi @arebbeadle , Please refer the “Address Data → SFTP” section in the below documentation to know what you can include in the Output file name. Added the screenshots from the documentation for your reference.https://docs.ifs.com/techdocs/Foundation1/040_administration/240_integration/300_ifs_connect/030_routing_rules_addresses/default.htm Thank you,Aswin.
Hi @tcollins57 ,This issue can be fixed by applying the “IFS Middleware Server binary patch 10.16.19.0 delivered via LCS Solution 301730” or the latest version “IFS Middleware Server binary patch 10.19.22.0 delivered via LCS Solution 305455”.Please raise a case to IFS Support Team including followings,A description of the issue. Test Plan - Steps to reproduce this error. Screenshot of the error message you get.They’ll investigate the issue and provide you the solution. Thank you,Aswin.
Hi @kjro ,This error "DBMS_SQL SECURITY ERROR: ORA-29471" is a generic Oracle issue which will be thrown when trying to close a cursor that is already closed using dbms_sql.close_cursor. @jasahu has explained it in his comment.Oracle has provided solutions for this issue in their official documentation. Since this is a DB issue, it has to be handled from DB level with the help of a Database Administrator. Please refer the below documents when resolving this issue.ORA-29471 Error When Executing dbms_sql.close_cursor ( Doc ID 760560.1 )Ora-29471: Dbms_sql Access Denied" From Software Package After Upgrade ( Doc ID 556301.1 ) Hope it helps. Thank you,Aswin.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.