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
Hi all,We’ve setup an IFS Cloud Printer Agent for our TEST instance based on this guide Problem:When any prints out of IFS Cloud are being performed, then we get the message that “array dimensions exceeded supported range”: Question:What is this message referring to? Note: On the same Print Server a JAVA Print Agent runs and works perfectly for IFSAPP10.The IFS Cloud TEST instance is a copy of our current IFSAPP10 PROD. No adjustments to reports have been done so far.
Hello,We are on IFS 10 with a MWS running WebLogic Server 12.2.1.3.0. Has anyone imported into the MWS a SSL certificate, whose key has been generated using ECC 256 instead of RSA? I’m afraid of potential incompatibility issues. IFS officially only recommmends RSA:https://docs.ifs.com/techdocs/foundation1/020_installation/020_installing_fresh_system/010_planning_installation/020_security_considerations/010_Certificates/
Hello IFS Community,After an IFS delivery our http server node cant be started due to:D:\ifs\INSTANCENAME\wls_domain\INSTANCENAME\servers\HttpServer1\logs\HttpServer1.log[2022-11-12T20:44:29.6552+01:00] [OHS] [ERROR:32] [OH99999] [ossl] [host_id: mws-server-name] [host_addr: ip-address] [pid: 12140] [tid: 1096] [user: IFS-Service] [VirtualHost: mws-server-name:48081] OHS:2057 Init: (mws-server-name:48081) Unable to initialize SSL environment, nzos call nzosSetCredential returned 28791[2022-11-12T20:44:29.6552+01:00] [OHS] [ERROR:32] [OH99999] [ossl] [host_id: mws-server-name] [host_addr: 10.110.0.72] [pid: 12140] [tid: 1096] [user: IFS-Service] [VirtualHost: mws-server-name:48081] OHS:2171 NZ Library Error: Unknown errorWe tried to perform a MWS reconfigure in order to re-import the valid SSL certificate, but we’re getting: There a few similar issues in the knowledge db, but none applies 100 % to our situation: Question: What is the trust anchor in this context?Is it the java cacert s
Dear IFS Community, Background:We’re hosting IFS10 UPD8 on premise.It was recommended to us, that we should startup IFS through a Desktop shortcut.That shortcut points to a share on the MWS, where the executable is located: Issue:All users who’re using this method experience - independend if its a buisness notebook or a power pc - very long startup times (30 sec+) and - once logged in - very sluggish behaviour (views loading time, field selection, data search time and so). There are no CPU / HD / Memory / Network spikes neither on MWS, DB nor the client itself. When IFS is being accessed through a webbrowser, then IFS behaves a tad more responsive. (Even though the Web variante brings other issues). Basic question:Is anyone else who is hosting IFS on prem accessing IFS through a Destkop shortcut?And if yes, do you or did you experience similar behaviour? Any pointer into the right direction would be appreciated.BR,Cesar
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.