This issue is now resolved.The problem was fixed by our external support and their findings are as follows;An amendment was actually required to IFSConnect and not IFSAPP as per the error message was stating. A grant was required on to the IFS_ALL permission set to enable IFSConnect access to the ManageMobileApplication.Once this was refreshed and all subsequent failures finished posting we no longer seen the error message above appear.Steps to resolveAmend IFS_APP permission set Grant ManageMobileApplication to that permission Ensure IFSConnect inherits a permission set that has ManageMobileApplication granted within it Refresh Cache Wait for all error messages to stop posting and retrying.Thanks
If anyone wants to complete similar, follow below steps.I got this working by utilising the IDAutomation tool below; https://www.idautomation.com/barcode-components/native-crystal-reports-generator/user-manual/After purchasing the QR CODE (IDA102) I imported the element that was embedded in to a prebuilt report. After amending the formula within field to use GS-1 formula field I created (Concatenation of multiple IFS Fields) the output was as required.Steps to completePurchase a license from ID Automation Copy over the prebuilt element within the report they supply Amend the element to use any data fields you require. In my instance this was a prebuilt formula field Run the report to ensure the element actually created a QR code Amend the font type the new element uses to; Lucida Console Ensure size of the font is between 3-5 for usage with thermal printers Insert report in to Report Definitions and printed this to ensure the QR code. Scan using a barcode scanning tool such as WaDaCo.T
Hi @RemyGeilvoet I’ve had a similar issue in the past. I know in IFS Apps 10 we have a view titled ‘QUICK_REPORT_LOG’ I’m not 100% sure if you have it in Apps9. If this view is accessible then you’ll be able to write a simple query to give you the results you require. e.g. one I wrote in the past. This will simply display the quick_report_id of anything older then the value you enter. SELECT DISTINCT QUICK_REPORT_LOG.quick_report_id--,QUICK_REPORT_LOG.description, QUICK_REPORT_LOG.executed, QUICK_REPORT_LOG.user_nameFROM ifsapp.QUICK_REPORT_LOGWHERE QUICK_REPORT_LOG.quick_report_id NOT IN ( SELECT DISTINCT QUICK_REPORT_LOG.quick_report_id FROM ifsapp.QUICK_REPORT_LOG WHERE QUICK_REPORT_LOG.executed >= ADD_MONTHS(TRUNC(SYSDATE), -&Months))ThanksRyan
Hi @mwilson We have external support that are dealing with this and this is the information they sent across:The lower limit it 4 GB and the upper limit is 6 GB for both Managed Server memory allocation for IFS MWSOur OS memory has 32gb allocated to it. Normally 20gb is being used by Java over 5 different Processes. The settings you’ve requested are:We currently don’t have a huge IFS user count. Maybe 40 active connections at peak so I can’t understand why we’re having memory related problems unless there’s a memory leak or the likes?
Hi @mwilson We have external support that had completed the work. They stated they updated the memory allocation for Manager Server on IFS MWS:They increased it to;Lower limit 0.4gbUpper Limit 0.6gb We currently are licensed for 200 users and use 135. Realistically we peak at around 40 active connections maximum currently. When I check the middleware server admin I can see both our initial memory size and maximum is similar to yours.
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.