Issue with License Installation - Aveva Intouch Wonderware 2020 R2

Hi,

I would start by verifying the following installation steps:

1. In the post-install "Configurator" utilitiy (which can be found on the start menu) the computer must be configured to use a specific license server. If the local computer is the license server you can just go with the default settings but you do need to hit "Configure" to store that setting.
2. The license server must have at least one InTouch license installed and activated.

I see other messages in your screenshots that indicate connection issues and in the Windows taskbar it appears you do not have a network connection. I would expect InTouch to still find a locally hosted license server despite not network, but perhaps this network outage may be related to the problem. It could be worth a shot.

Hi,

I would start by verifying the following installation steps:

1. In the post-install "Configurator" utilitiy (which can be found on the start menu) the computer must be configured to use a specific license server. If the local computer is the license server you can just go with the default settings but you do need to hit "Configure" to store that setting.
2. The license server must have at least one InTouch license installed and activated.

I see other messages in your screenshots that indicate connection issues and in the Windows taskbar it appears you do not have a network connection. I would expect InTouch to still find a locally hosted license server despite not network, but perhaps this network outage may be related to the problem. It could be worth a shot.

Just a thought here, what version of the DA server are you using? Some older versions still rely on file based licenses, 2020(?) and up introduced the concept of OI servers (replacing DA servers).

Did you install your SI Direct as a separate install or the one part of System Platform 2020 install?

Looking at your log it seems view.exe is acquiring a license correctly so the license server should be available. 

The reference to DA server version 10.5 is from the generation of InTouch 2012, and this version was only file based licenses(.lic), in 2020 R2 it's activation based licenses using the License Server (.xml)

Good catch. The phrase "DAS" or "DA Server" may still linger is some places of the product but you may need to confirm that you are using the Communication Drivers Pack rather than older "DA Servers".

Furthermore, you may need to confirm that the license includes the Communication Drivers entitement. Some InTouch licenses include the Communication Drivers, but other do not and may require a separate license for the drivers.

Richard Köhlerstrand said:

what version of the DA server are you using?

DAServer 3.0 SP1

Richard Köhlerstrand said:

Did you install your SI Direct as a separate install or the one part of System Platform 2020 install?

We have Installed SI Direct and DA Server separately, SI Direct is Activated but DAS is not Activated

Richard Köhlerstrand said:

Looking at your log it seems view.exe is acquiring a license correctly so the license server should be available. 

All Licnenses are Working except DAS.

rickard.norin said:

I would start by verifying the following installation steps:

1. In the post-install "Configurator" utilitiy (which can be found on the start menu) the computer must be configured to use a specific license server. If the local computer is the license server you can just go with the default settings but you do need to hit "Configure" to store that setting.
2. The license server must have at least one InTouch license installed and activated.

I already checked that. Everything is fine.

rickard.norin said:

I would expect InTouch to still find a locally hosted license server despite not network, but perhaps this network outage may be related to the problem. It could be worth a shot.

our Communication Drivers are Activating SI Direct but may be not Valid for DAS.

If this is the case then the reason for your license issue is related to installing a .lic file for licensing the driver, the activation based xml file will not support this version of the component.

But it has to be mentioned that it is advised to use the upgraded version of your SIDirect, replacing it with the same generation product (OI Server) SI Direct.

Is there any particular reason for mixing versions in this way? There could be other issues installing such an old product on the same server as 2020 R2.

I have had the same issues in the past, in my case I run the old archestra license manager alongside the enterprise lic manager. (using a lic file instead of xml). The DA SIDIRECT version you are running probably needs to acquire the license from there to run. Here is a screenshot of how it looks. It is probably already installed on your platform. 

...