Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

Hi etantonio, That null pointer exception wouldn't crash Mango. So, something else must be in your logs, or there may be an hs_err file in your Mango/ directory.. I am not sure what caused it, but the report's filename must be null. You can check to see if the report was actually generated by checking the Mango/web/modules/excelReports/web/report-data/ directory. If you find the right report, you can try to update the row in the database for the report instance that is causing the null pointer exception, or you can delete those report instances since you found the generated files. /sqlConsole.shtm Find and update the reports' records (run whichever line individually): SELECT * FROM excelReports WHERE filename IS NULL; --submit query UPDATE excelReports SET filename='Filename_here.xlsx' WHERE filename IS NULL; --submit update -- use "WHERE id IN (1, 2, 3)" gotten from the select statement if you have more than one type of report) Or just delete those excel report instances with DELETE FROM excelReports WHERE filename IS NULL; -- submit update

You could change the logging type of the points to either an interval or interval change type (I am guessing they are currently log on change?).

Hi Antonio, In the latest Mango you should be able to edit your env.properties file to set store.url= and it will not reach out to the designated store if it is blank.

yes, you are right.

Are you using the new Dashboard Designer or the old Graphic Views? The new UI and Dashboard Designer performs much better. I would strongly recommend learning the new Dashboard Designer rather than Graphic views.

hi, JoelHaggar and CraigWeb: I'm in business trip and cant access mango system as it run internally. I will provide more detial info after I come back. sorry.

Yes, there is no restriction for MySQL in free mode. See here for more information on converting: https://help.infiniteautomation.com/database-conversions/

Thanks Phil

Hi Ralf, It means that for 26 points there was more data already on the receiving end than data on the publisher's side for the period checked. Usually this is caused by a point with interval logging on the publisher transmitting its realtime updates as opposed to logged events, then the receiver's default point logs all data if the receiver is configured to save real time data, and that amounts to an overcount. It can be possible other ways (disk getting full, importing extra data at receiver, etc), but that's what I'd guess caused it here. The solution to prevent it if that is the cause would be to change your publisher's publish event to logged data instead of updates.

That will again depend on the size of the request. Blindly trusting the numbers from this stack overflow thread (as I'm not that deep in the TCP protocol typically): https://stackoverflow.com/questions/31378403/how-much-data-it-cost-to-set-up-a-tcp-connection Without keep alive it would be opened and closed each poll, so 296bytes / poll. 24 * 3600 * 296 = 25574400 so maybe 25.5MB / day But I would still encourage you to meter it if that overhead is important.

The AVERAGEIF is not [yet?] a supported function of Apache POI: https://poi.apache.org/spreadsheet/eval-devguide.html

@etantonio The server must be a SMTP mail server. It is not possible to setup Mango to send emails through a web mail service. Exchange definitely supports SMTP, you will have to ask your customer to send you the correct port number, credentials etc

I gave the reason - the management of the points (particularly the permissions) is more straightforward. But, it does seem unlikely you would give an untrusted user permission to add points to one of the data sources that talks to a device you don't want them setting some values to. Either way I encouraged point level permissions. The other reason is the data source may be able to request all the necessary data in fewer requests if it's all on the same data source. It is likely that you Modbus device has a setting (whether configurable or not) for how many concurrent IP connections it will accept. It should accept a few and work fine.

I would also maybe try relaunching Mango from the command line and watching for any errors that occur when you try to view a watchlist that has this problem, if it persists through a restart.

Thank you MattFox, I get it!

Yes Mango is very much designed for multicore machines. Yes my formal recommending is considering that a denial of service attack on one client will probably affect the other. And that a malicious user in one system could find their way to affecting the other system. In plenty of cases with plenty of people, you may not find that situation. But, running two ideally-separate Mangoes as the root user is leaving the door open to trouble, especially if you're doing a second insecurity like logging in as the admin user on an unsecure connection.

Hmm. Do you know if you saved the point link when the event was active, and that's when it returned to normal? I do think it's possible for a point link to get stuck thinking it's running. I think it would have to be an exception in the PointLinkRT's execute method. I'm not sure where one could produce such an error, but I will do some checking. I would have expected an error in your log like, "Uncaught exception in work item" and that the PointLinkRT's execute method will appear in the stack trace. Otherwise, it could be that two point events for the source series were running at the same moment and the error about not being able to run the point link again is incidental to not having set the value to the device. If the modbus connection was simply down AND two events got queued at the same time, we could expect what you're describing. There would have been a data source event for the set point failure.

No, you can use it. The documentation is out of date. I have fixed it for the next release.

Hi leoboeng, The error implies that you have created a formula in your excel report based on a named range that is not defined. So, if you have a named range like 'range' but your forumla is '=SUM(arange)' that mismatch will produce the shown error (provided there is no named range 'arange' in the worksheet). Posting a screenshot of error text is not as useful as posting the content of the error. Images are not searchable. Here's the text of the error from my reproduction: ERROR 2018-05-04T13:29:19,095 (com.infiniteautomation.mango.excelreports.rt.ExcelReportWorkItem.execute:673) - Specified named range 'BARange' does not exist in the current workbook. org.apache.poi.ss.formula.FormulaParseException: Specified named range 'BARange' does not exist in the current workbook. at org.apache.poi.ss.formula.FormulaParser.parseNonRange(FormulaParser.java:910) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.parseRangeable(FormulaParser.java:501) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.parseRangeExpression(FormulaParser.java:322) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.parseSimpleFactor(FormulaParser.java:1540) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.percentFactor(FormulaParser.java:1498) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.powerFactor(FormulaParser.java:1485) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.Term(FormulaParser.java:1858) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.additiveExpression(FormulaParser.java:1986) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.concatExpression(FormulaParser.java:1970) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.comparisonExpression(FormulaParser.java:1927) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.Arguments(FormulaParser.java:1471) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.function(FormulaParser.java:1343) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.parseNonRange(FormulaParser.java:896) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.parseRangeable(FormulaParser.java:586) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.parseRangeExpression(FormulaParser.java:322) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.parseSimpleFactor(FormulaParser.java:1540) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.percentFactor(FormulaParser.java:1498) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.powerFactor(FormulaParser.java:1485) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.Term(FormulaParser.java:1858) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.additiveExpression(FormulaParser.java:1986) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.concatExpression(FormulaParser.java:1970) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.comparisonExpression(FormulaParser.java:1927) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.intersectionExpression(FormulaParser.java:1900) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.unionExpression(FormulaParser.java:1880) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.parse(FormulaParser.java:2028) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.FormulaParser.parse(FormulaParser.java:170) ~[poi-3.17.jar:3.17] at org.apache.poi.xssf.usermodel.XSSFEvaluationWorkbook.getFormulaTokens(XSSFEvaluationWorkbook.java:85) ~[poi-ooxml-3.17.jar:3.17] at org.apache.poi.ss.formula.WorkbookEvaluator.evaluateAny(WorkbookEvaluator.java:276) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.WorkbookEvaluator.evaluate(WorkbookEvaluator.java:220) ~[poi-3.17.jar:3.17] at org.apache.poi.xssf.usermodel.BaseXSSFFormulaEvaluator.evaluateFormulaCellValue(BaseXSSFFormulaEvaluator.java:64) ~[poi-ooxml-3.17.jar:3.17] at org.apache.poi.ss.formula.BaseFormulaEvaluator.evaluateFormulaCellEnum(BaseFormulaEvaluator.java:192) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.BaseFormulaEvaluator.evaluateAllFormulaCells(BaseFormulaEvaluator.java:267) ~[poi-3.17.jar:3.17] at org.apache.poi.ss.formula.BaseFormulaEvaluator.evaluateAllFormulaCells(BaseFormulaEvaluator.java:258) ~[poi-3.17.jar:3.17] at org.apache.poi.xssf.usermodel.XSSFFormulaEvaluator.evaluateAllFormulaCells(XSSFFormulaEvaluator.java:72) ~[poi-ooxml-3.17.jar:3.17] at com.infiniteautomation.mango.excelreports.rt.ExcelReportWorkItem.execute(ExcelReportWorkItem.java:649) [excel-reports-3.4.1-SNAPSHOT.jar:?] at com.serotonin.m2m2.rt.maint.BackgroundProcessingImpl$WorkItemRunnable.run(BackgroundProcessingImpl.java:676) [classes/:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) [?:?] at java.lang.Thread.run(Thread.java:844) [?:?]