I'm currently trying to Implement a RSView SE app to write to a SQL DB. (MySQL)
I have completed setting up the datalog models based on time,trigger,on change and writing to the database.
The problem comes in, when I write to the database when it is empty everything works great. The second time RSView SE app is restarted is where my problems come in. It cannot create tags for one of my processors. (I am monitoring 7 processors with about 20,000 tags) The tags for this ONE processor fails to write to the SQL database. All my other processors/data log models work fine though.
All of my tag tables in the SQL database are configured the same. There is not a difference in the tags compared to another processor. (tag type, path, etc)
Does anybody have any ideas as to what the problem is? I have read the MySQL manual and RSView SE manuals and there is no indication in there why this would be happening.
I'm wondering if this particular processor is configured differently as the data log models and tables in the SQL database are identical to the working processors. But, as I and another guy did the programming on all the processors (he did this one) we don't know of any special configuration. And if there was a special configuration for the processor, why would it work the first time?
Is it trying to write to the same tag index twice? If so, why? How can I make RSView write to a seperate tag index everytime? This works on the other 6 processors! (sorry, frustration coming out)
Again, the second time trying to write to the tag table for 1 of 7 processors, the tags come back 'Failed to add item' in the diagnostic viewer for the RSView SE.
I have even recreated the datalog model to make sure RSView SE didn't lose it's configuration internally for the model. (I am not a supporter of RSView's efficiency or stability)
I beg for advice and assistance as I've been trying to find a work around for this for about a month now.
I have completed setting up the datalog models based on time,trigger,on change and writing to the database.
The problem comes in, when I write to the database when it is empty everything works great. The second time RSView SE app is restarted is where my problems come in. It cannot create tags for one of my processors. (I am monitoring 7 processors with about 20,000 tags) The tags for this ONE processor fails to write to the SQL database. All my other processors/data log models work fine though.
All of my tag tables in the SQL database are configured the same. There is not a difference in the tags compared to another processor. (tag type, path, etc)
Does anybody have any ideas as to what the problem is? I have read the MySQL manual and RSView SE manuals and there is no indication in there why this would be happening.
I'm wondering if this particular processor is configured differently as the data log models and tables in the SQL database are identical to the working processors. But, as I and another guy did the programming on all the processors (he did this one) we don't know of any special configuration. And if there was a special configuration for the processor, why would it work the first time?
Is it trying to write to the same tag index twice? If so, why? How can I make RSView write to a seperate tag index everytime? This works on the other 6 processors! (sorry, frustration coming out)
Again, the second time trying to write to the tag table for 1 of 7 processors, the tags come back 'Failed to add item' in the diagnostic viewer for the RSView SE.
I have even recreated the datalog model to make sure RSView SE didn't lose it's configuration internally for the model. (I am not a supporter of RSView's efficiency or stability)
I beg for advice and assistance as I've been trying to find a work around for this for about a month now.