Do you mean this screen:Found it yesterday and enabled. Do you know what Verification Type: PIN Code referes to and how to set?How does the checkpoint work with SSO in Azure where you don’t have a password?Thanks,Alex
Great thank you. Alex
Yes thats exactly what I need as my list has now updated to 23.1 so I can only see those. Could you send me a screenshot of the remote bins below also? Many thanks,Alex
Indeed I think I have the process but when I try and run the installer now I get this:I think I have a mismatch of the bin files and my actuall install but I don’t know which version of the bin files I should use for 22.2.4.Thanks,Alex
I have a similar issue. My log just reports this bit:18/01/2024 12:36:46[IFSCRCFG]-[GetDbInfoFromXml] Decrypted.18/01/2024 12:36:46[IFSCRCFG]-[GetDbInfoFromXml] Decrypted.18/01/2024 12:36:46[IFSCRCFG]-[GetDbInfoFromXml] Retrieved Information from XML : DBUser-IFSSYS DBPassword-******* PrintUser-IFSPRINT PrintPassword-******* DBServerName-CFGPDB AppOwner-IFSAPP IALOwner-IFSINFOOn screen I get Error in retrieving the parameters Thanks,Alex
Did you find an answer to this in the end? I also have a selector that I can’t add a property to. Thanks,Alex
I know this thread is a little old but we’ve found a tool to assist with moving IFS Application 10 IEE permission sets to Aurena permissions. We are evaluating the tool now but we’ve have talked with someone who is using the tool and they found it useful. The tool was created by the IFS partner Nayo Tech and it’s called Nayo Security Suite. https://www.nayotech.com/nayo-security-suite is the link to the product information. Regards, William Klotz Can I ask how you got on with the product and if you have any feedback? Looking at using the product too.Regards,Alex
@cblome I have raised the issue with IFS Support - Investigations are ongoing. One avenue that we have looked at is if the Kubernetes cluster had installed correctly as all the PODS were stuck at a Pending State.. Hi we have the same issue. How did you resolve that? thanks Gary Its been my experience that if you have PODS in a pending state you need to look at the logs using the ./mtctl dump --namespace [namespace] command. This will create a dump folder in the delivery folder and you can see which POD is holding things up. They run up one by one but will not start new PODS if one errors. It could be you simply don’t have enough memory or a database connection error, but you will only know by looking at the logs.Thanks,Alex
Hi Asanka,Great work this could save us a lot of time, I work with Linda in technical and I tried to run the script.When I run in PLSQL I get clob_to_blob not declaired: ifsapp.edm_file_storage_api.write_blob_data(objversion_, objid_, clob_to_blob(rec.text)); Am I doing something wrong or could this be because we are using 22.2? Thanks,Alex
I now get this when it starts the ifsapp-amm pod: Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning Unhealthy 4m52s (x197 over 3h32m) kubelet Startup probe failed: Unable to connect to database I’ve checked the ifsmon-password and ifsapp-user passwords and they both seem correct. Which password does it use to connect to the database and what permissions should it have? Thanks, Alex My misake, although the password was correct the ifsmonitoring account ws locked in Oracle.
My misake, although the password was correct the ifsmonitoring account ws locked in Oracle.
I now get this when it starts the ifsapp-amm pod:Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning Unhealthy 4m52s (x197 over 3h32m) kubelet Startup probe failed: Unable to connect to databaseI’ve checked the ifsmon-password and ifsapp-user passwords and they both seem correct.Which password does it use to connect to the database and what permissions should it have?Thanks,Alex
Are you using Windows 11? I’ve just had a user get the same error in Apps9. I had heard only recently that Micorsoft are removing .rtf functionallity from Windows 11 and WordPad but that maybe a coincidence.Regards,Alex
Thank you. It was the IFSSYS password at fault, must not have been set properly.
Can ping both no problem. Running the command manually seems to point to this being the source of the timeout: unable to recognize "/var/snap/microk8s/current/args/cni-network/cni.yaml": Get "https://127.0.0.1:16443/api?timeout=32s": net/http: TLS handshake timeoutunable to recognize "/var/snap/microk8s/current/args/cni-network/cni.yaml": Get "https://127.0.0.1:16443/api?timeout=32s": net/http: TLS handshake timeoutUnable to connect to the server: net/http: TLS handshake timeoutUnable to connect to the server: net/http: TLS handshake timeout127.0.0.1 api.snapcraft.io already exists in /etc/hosts) Many thanks,Alex
No not yet, it is taking some time. Do you have the same error?
Yes its Case CS0095991
No not yet. It seems speaking to support that this test is no longer expected to work so testing in this way is not indictiave of anything.Does it actually work from the appliction? If not what errors do you see?One way to tell if the application and the WebService are talking is to enable logs in IFS Cloud :Crystal Web Services Logs > Edit Log ConfigurationEnable Logs > Click OKWhen we enable we get this error:IFS support are currently investigating.
I hope you’re doing well and keeping safe.This is a new feature request and we’re aware of the requirement. And this option will be available with IFS Cloud 22R2 release. Best Regards, Do we know if this got implimented? Are there any instructons as I couldn’t get it to work. Thanks,Alex
I think the confusion is centred arround this part of the Technical Documentation:Buildhome and Delivery Creation during Upgrade iterations for Customers Upgrading to IFS Cloud from Previous IFS Application VersionsBuild home creation is handled by using a tested sanity tag of the customer solution repository. The build home thus created can be uses as input to the Upgrade build home creation required when upgrading to IFS Cloud from earlier releases of IFS Applications.Creating Buildhome - Technical Documentation For IFS Cloud Thanks for your assistance.
Me too - it seems to be the ADFS password that seems to be the issue.Thanks,Alex
It is looking for this certificate:java.io.FileNotFoundException: C:\ifsroot\config\certs\IFS.pfx (The system cannot find the file specified)Is it in the ifsroot folder?
I have had this many times and usually because I’d forgotten to update the cert in the local user profile:Get the kubeconfig file from the Kubernetes cluster in Middle Tier Server.¶This command grabs the kube config file from the Kubernetes cluster and copies it over to the Windows VM. This file is used to access Kubernetes when used with command line tools such as kubectl and helm.ps> .\main.ps1 -resource 'GETKUBECONFIG' Copy the file ifsroot\config\kube\config to c:\users\.kubeps> mkdir $HOME\.kubeps> copy .\config\kube\config $HOME\.kube\
Do you have the certificate specified in your ifscloud-values.yaml file?certificateFile: C:\ifsroot\config\certs\IFS.pfxcertificatePassword: [pfx cert password]I think it needs one for the domain you are publishing the middleware to i.e. ifscloud.yourdomain.comThanks,Alex
Extended during testing to 60m without any success. I have created a support ticket and will let you know if IFS support manage to resolve.
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.
