Hi,
Sorry, I just saw this post. It does sound like the most likely problem is that the OPC server is responding very slowly to the process of creating group subscriptions. This does affect the startup of FactorySQL, though there aren’t many options for better ways to handle it. We can’t create multiple subscriptions in parallel, due to how the connection to the OPC server works.
There are two other possible causes of slow startup times: first, since you’re using redundancy, the project is loaded from the database. If the database was responding slowly, this could cause the startup to take a while. However, I’ve never really seen this be an issue.
The second, more common problem, is that there is a lot of data stored up in the data cache. Processing this data can sometimes slow the system down. Look for “data_cache.fdb” in the install directory, and see how big it is. If it appears to be large (over a few MB), it might be causing problems.
As for the write error, I’m not sure why it’s displaying that. There are technically two result codes that get returned, and one may be success (the write status) while the second (the call result) is coming back as bad. You may be able to look at the diagnostic information in the OPC server to find more information.
To confirm that subscriptions are slow to create, or that my idea about the write error is correct, you could install the OPC Analyzer, and point a few of your groups to use that instead. This will pass the calls through to the opc server, but will show each call and how long it took.
As for the folder, I’m afraid you may need to export the project, perhaps to csv, clear the project in the database, and reload it. The folders appears to be stored inside of serialized objects, so there isn’t a way to delete them directly in the database. If you rename the folder, does the old name get created again?
Finally, what version of FactorySQL is this?
Regards,