Problems deactivating IDAS on a newly installed historian.

Haven't seen this before. Tried a little to reproduce on a local system without success. Some guesses at things to check/consider:

1. Have you made any changes to the service identity for "AVEVA Historian Configuration"? 
2. Have you tried with the IDAS enabled (even though you don't need it)?
3. Try re-running the "AVEVA Historian-->Security" configuration in the Configurator 

Hi Elliot,

this message came immediately after fresh historian installation, it has then only been configured as a partner to a primary server. After noticing the warning I tried disabling and enabling the IDAS through the IDAS properties and remembered to commit pending changes.  (on a side note: the "committing changes"  requirement is not obvious)

After giving up, I decided to uninstall the historian completely and re-install config it to drop and create a new database. 

It still continues. 

I also found a technote called "fixing the IDAS deadlock" I tried deleting  the idascfg_xxx.dat  file in the C:\ProgramData\ArchestrA\Historian\IDAS\Configurations

I also tried adding a random IO server by right clicking on IDAS and then deleting it again....

tried disabling the connection to the SMS and re connecting through the configurator.

What puzzles me is that it still comes with the warning even though i shutdown the historian completely, the log below is while the historian is in shutdown mode.

Will try redoing the security configuration as suggested and let you know.

Tried configuring security again, by removing and adding users. still the same 

filtered log aahidas component

Look at the directories within "C:\ProgramData\ArchestrA\Historian". There will probably be some IDAS configuration files (delete those) and there will be a "StartupConfig.xml"--this file is needed and should have one "application" element for "owinhost"--if it has more than one, create a copy of the file and then remove any other "application" elements.

Have you possibly installed and configured the "Insight Publisher" on this node? 

 Jakob Agustsson ,

It appears that this Historian node had been configured as a remote IDAS node. If IDAS appears on Configurator as shown below, highly likely IDAS had been configured as standalone to communicate with a remote Historian. Anyway, when the entire Historian features (including integrated IDAS) were installed on this node, IDAS part was not merged together because both IDAS components were configured independently. It might be good idea to prompt users for merging IDAS in future releases.

There is no way to disable the standalone IDAS configuration in Configurator. We have to manually workaround this issue. So, try to stop aahSupervisor.exe via and see if it will stop warning messages. Alternatively, remove its IDAS configuration in the following steps.

• Rename aahIDAS.config from C:\ProgramData\ArchestrA\Historian\IDAS to aahIDAS.config.xtx
• Rename StartupConfig.json from C:\ProgramData\ArchestrA\Historian\Hosting\Configuration to StartupConfig.json.xtx
• Historian may be required to restart.
• Check aaLogger if those waring messages are suppressed.
• Talk to Technical Support and they will help you removing the IDAS part of Historian from Configurator Plugins if you think it is annoyed.

Good luck!

Regards,

Jacky

 Jakob Agustsson ,

It appears that this Historian node had been configured as a remote IDAS node. If IDAS appears on Configurator as shown below, highly likely IDAS had been configured as standalone to communicate with a remote Historian. Anyway, when the entire Historian features (including integrated IDAS) were installed on this node, IDAS part was not merged together because both IDAS components were configured independently. It might be good idea to prompt users for merging IDAS in future releases.

There is no way to disable the standalone IDAS configuration in Configurator. We have to manually workaround this issue. So, try to stop aahSupervisor.exe via and see if it will stop warning messages. Alternatively, remove its IDAS configuration in the following steps.

• Rename aahIDAS.config from C:\ProgramData\ArchestrA\Historian\IDAS to aahIDAS.config.xtx
• Rename StartupConfig.json from C:\ProgramData\ArchestrA\Historian\Hosting\Configuration to StartupConfig.json.xtx
• Historian may be required to restart.
• Check aaLogger if those waring messages are suppressed.
• Talk to Technical Support and they will help you removing the IDAS part of Historian from Configurator Plugins if you think it is annoyed.

Good luck!

Regards,

Jacky

Hi Jacky,

stopped the service as you suggested.

Warnings have stopped appearing in logger. 

That is sufficient solution for me  so I will not take any further steps, unless disabling this service has some negative interaction with other aspects of the system. ?

Otherwise I am just happy to have a clean log!

The IDAS category is not shown in configurator, but I do recall it being there during re-installation of historian. (previously tried uninstalling and re-installing to see if it would help, i remember seeing the IDAS option but could not uncheck it)

This might also have something to do with me activating a SMS after installing historian for the first time.

Anyway

thank you!