When you say 'Perceive loses the configuration', what do you mean exactly? Is the data source just not there in the list?
If Perceive can't startup datasources properly, because of edits to the datasources.xml file which are inconsistent with the config.xml file, this could happen.
Otherwise I've never seen that before.
Correct... The data source is no longer listed in the Administration tab under Data Sources...
When this happens, I have to recreate the data source, reactivate it, and then bring Perceive back nnline...
You think this could be caused by an invalid datasources.xml file? Are there any particular things I should look out for or make sure I didn't do that could cause this?
Thanks for the help!
Typically, the data source type "name" in the datasources.xml has been updated, but all the data source instances of that "type" attribute in the config.xml haven't been updated.
During startup in 7101, Perceive reads the data sources in config.xml and will abort on the first one with a type that doesn't match (and therefore can't be found) in datasource.xml
Hope that helps.
I think I found the problem... I recently changed Perceive boxes and had not created one of the ODBC data sources used for Perceive in the Data Sources config in the control panel of the Win2K system...
Anyhow, got rid of the errors now, and the configuration is kept in Perceive. Should Perceive come up "active" and have activated data sources when the service/box is restarted? The data source appeared when I restarted the service, but it didn't activate the data source...