History Logging Not Working

Ignition
1

I moved some tags from one folder to another in the SQLTags browser, and perhaps coincidentally, historical logging has stopped working.

I am getting the following error;I am using SQL Server Express and Version 7.0.3 (b4519) of Ignition.
I don’t understand the error, as thetable sqlth_drv does exist, so I’m not sure why Ignition is trying to create it again.

com.inductiveautomation.ignition.gateway.web.pages.config.systemconsole.LogViewer$SerializableLoggingEvent$ClonedThrowable: Error running query: CREATE TABLE sqlth_drv ("id" int IDENTITY(1,1),"name" varchar(255),PRIMARY KEY ("id")) com.inductiveautomation.ignition.gateway.db.schema.DBTableSchema.executeCommandSet(DBTableSchema.java:96) com.inductiveautomation.ignition.gateway.db.schema.DBTableSchema.createTable(DBTableSchema.java:67) com.inductiveautomation.ignition.gateway.db.schema.DBTableSchema.verifyAndUpdate(DBTableSchema.java:60) com.inductiveautomation.ignition.gateway.history.sinks.TagHistoryDatasourceSink.checkTables(TagHistoryDatasourceSink.java:482) com.inductiveautomation.ignition.gateway.history.sinks.TagHistoryDatasourceSink.initialize(TagHistoryDatasourceSink.java:144) com.inductiveautomation.ignition.gateway.history.sinks.AbstractSink.tryToInit(AbstractSink.java:81) com.inductiveautomation.ignition.gateway.history.sinks.TagHistoryDatasourceSink.tryToInit(TagHistoryDatasourceSink.java:135) com.inductiveautomation.ignition.gateway.history.sinks.AbstractSink.isAccepting(AbstractSink.java:98) com.inductiveautomation.ignition.gateway.history.sinks.AbstractDatasourceSink.isAccepting(AbstractDatasourceSink.java:75) com.inductiveautomation.ignition.gateway.history.sinks.TagHistoryDatasourceSink.isAccepting(TagHistoryDatasourceSink.java:175) com.inductiveautomation.ignition.gateway.history.sinks.AggregateSink.isAccepting(AggregateSink.java:81) com.inductiveautomation.ignition.gateway.history.ForwarderThread.run(ForwarderThread.java:74) com.inductiveautomation.ignition.gateway.web.pages.config.systemconsole.LogViewer$SerializableLoggingEvent$ClonedThrowable: There is already an object named 'sqlth_drv' in the database. com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:196) com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1454) com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:786) com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:685) com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:4026) com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1416) com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:185) com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:160) com.microsoft.sqlserver.jdbc.SQLServerStatement.executeUpdate(SQLServerStatement.java:642) org.apache.commons.dbcp.DelegatingStatement.executeUpdate(DelegatingStatement.java:228) com.inductiveautomation.ignition.gateway.datasource.DelegatingStatement.executeUpdate(DelegatingStatement.java:79) com.inductiveautomation.ignition.gateway.datasource.SRConnectionWrapper$SRStatement.executeUpdate(SRConnectionWrapper.java:634) com.inductiveautomation.ignition.gateway.db.schema.DBTableSchema.executeCommandSet(DBTableSchema.java:94) com.inductiveautomation.ignition.gateway.db.schema.DBTableSchema.createTable(DBTableSchema.java:67) com.inductiveautomation.ignition.gateway.db.schema.DBTableSchema.verifyAndUpdate(DBTableSchema.java:60) com.inductiveautomation.ignition.gateway.history.sinks.TagHistoryDatasourceSink.checkTables(TagHistoryDatasourceSink.java:482) com.inductiveautomation.ignition.gateway.history.sinks.TagHistoryDatasourceSink.initialize(TagHistoryDatasourceSink.java:144) com.inductiveautomation.ignition.gateway.history.sinks.AbstractSink.tryToInit(AbstractSink.java:81) com.inductiveautomation.ignition.gateway.history.sinks.TagHistoryDatasourceSink.tryToInit(TagHistoryDatasourceSink.java:135) com.inductiveautomation.ignition.gateway.history.sinks.AbstractSink.isAccepting(AbstractSink.java:98) com.inductiveautomation.ignition.gateway.history.sinks.AbstractDatasourceSink.isAccepting(AbstractDatasourceSink.java:75) com.inductiveautomation.ignition.gateway.history.sinks.TagHistoryDatasourceSink.isAccepting(TagHistoryDatasourceSink.java:175) com.inductiveautomation.ignition.gateway.history.sinks.AggregateSink.isAccepting(AggregateSink.java:81) com.inductiveautomation.ignition.gateway.history.ForwarderThread.run(ForwarderThread.java:74)

2

What version of SQL Server Express are you using?

3

SQL Server 2008 Express - Version is reported as 10.0.1600.22

4

This should be fixed in the 7.0.4 update coming out later today. We’ve been doing some work on better supporting SQL server schemas, which led to this problem. As it stands, schemas are supported, but identical table names in multiple schemas aren’t. We’re working on getting it to work across the board.

You don’t need to worry about all this personally, but I wanted to throw that out there for others who might happen on this thread.

Regards,