Knowledge Base
The Inductive Automation Knowledge Base provides support solutions, error messages, bugs and troubleshooting guides. To begin either search for a keyword or enter in an article id. To view all articles click on the View All link to the left.
Error occured while loading tag information
Problem
You are getting an error every few seconds when trying access SQLTags
history. This is caused by installing ignition 7.3 and downgrading
to version 7.2. The problem is that the 'querymode' for the
SQLTags history has a new possible value in 7.3 that wasn't in version
7.2. This causes the following error:
History.SQLTags.DataLoader.XXXXX
(id=1dbf91b6)
Error occured while loading tag information.
java.lang.ArrayIndexOutOfBoundsException:
3
at
com.inductiveautomation.ignition.common.sqltags.history.InterpolationMode.getTypeForValue(InterpolationMode.java:32)
at
com.inductiveautomation.ignition.gateway.sqltags.history.query.loaders.DatasourceHistoryLoader.loadTagInformation(DatasourceHistoryLoader.java:224)
at
com.inductiveautomation.ignition.gateway.sqltags.history.query.loaders.DatasourceHistoryLoader.initialize(DatasourceHistoryLoader.java:146)
at
com.inductiveautomation.ignition.gateway.sqltags.history.query.loaders.AggregateHistoryLoader.initialize(AggregateHistoryLoader.java:50)
at
com.inductiveautomation.ignition.gateway.sqltags.history.query.HistoryWriter.execute(HistoryWriter.java:158)
at
com.inductiveautomation.ignition.gateway.sqltags.history.query.BasicTagHistoryQueryProvider.query(BasicTagHistoryQueryProvider.java:137)
at
com.inductiveautomation.ignition.gateway.servlets.gateway.functions.QueryTagHistory.invoke(QueryTagHistory.java:99)
at
com.inductiveautomation.ignition.gateway.servlets.Gateway.doPost(Gateway.java:389)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at
com.inductiveautomation.ignition.gateway.bootstrap.MapServlet.service(MapServlet.java:85)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at
java.lang.Thread.run(Unknown Source)
Resolution
Modify the SQLTags History raw data.
To fix it you need to modify the raw data in one of the SQLTags history tables in the database. If you don't feel ok doing this, call in to the tech support line and we can help you.
To start, open a database browser and check that the sqlth_te table contains the incorrect values. To see all the bad rows, use this query:
SELECT * FROM sqlth_te
WHERE querymode = 3; This fix will only work if you are currently running a version below 7.3. Upgrading to 7.3 again will also fix this problem. Now that you see the entries with a querymode of 3, you can fix them by entering the following:
UPDATE sqlth_te SET
querymode = 1 where querymode = 3; Article ID: 135
Type of Document: KB Article
Created: Jan 11, 2012
Last Modified: Jan 11, 2012
Type of Document: KB Article
Created: Jan 11, 2012
Last Modified: Jan 11, 2012