I believe that error indicates a problem with the .Net framework (which must be installed for the upgrade process). We recently saw a problem like that even with the framework installed, on a 64-bit machine. In that case, it was possible to run the “db-to-xml” upgrade portion manually, and then import the xml.
- Download the FSQL Upgrader Tool, and extract it.
- Run “ProjectConverter.exe fsqlproj.fdb output.xml” (with the correct file name, of course)
- Take the resulting “output.xml” and use that in the legacy upgrade screen instead of the “fdb” (I know the screen says it will only take “fsp” and “fdb”, but it will also take XML).
I’m mostly outlining this for other people who have this problem, since your right that in your case you’ll probably have just as much work to convert the addresses after your upgrade.
NOW, as for alerting: You are adding SQLTag references to groups, which is why you can’t define additional alerting on them. It is also possible to add direct references to OPC into groups, in which case you can then define scaling, alerting, etc.
The difference between SQLTags in groups and OPC items is described a little in the user manual Here, but in short the key thing to know is that with SQLTags, the tags are subscribed and evaluated according to their scan class, whereas opc items in groups are subscribed and evaluated according to the group. If you’re going to use the tags in status displays and the like (in other words, you’re going to make sqltags anyhow), you could do your alerting there. Otherwise, you could add the opc items to the group and alert on them in that way.
Hope this helps,