License Issue when Using Application Server 3.1 SP3 P01 with New DIObjects Versions

Posted on 212 views

This TechNote gives you important instructions to be performed on each platform at which you want to deploy the DIObjects to avoid having licensing issue in runtime when running new versions from DIObject , which use the new Archestra License not suitelink.lic for example DIMBTCP 3.0 sp1 and DIABCIP 5.0,  inside Wonderware Application Server 3.1 SP3 Patch 1 .

Application Versions

  • Application Server 3.1 SP3 P01
  • DI MBTCP 3.0 SP1
  • DI ABCIP 5.0


Windows Server 2008 R2

When running newer DASSERVER it stops periodically , getting Information message in your logger says that <DASERVER name > Please install a valid license for this DAServer product as shown in fig.1 below. trying with external demo license and getting same issue.

Figure 1: License invalid info message

DAServer now uses the ArchestrA License Manager and the common ArchestrA license file.

If you are still using software versions that use the wwsuite.lic license file, and you do not have an ArchestrA.lic license file with the correct feature line you need to add it, you need to run InitLicense.wsf file included with the CD image to initialize the new ArchestrA Licensing sub-system.

If you are running Wonderware Application Server 3.1 SP3 Patch 1 or older, you must perform the following functions on each platform where you want to deploy the MBTCP DIObjects to it, Please follow below steps.

  1. Undeploy DIObjects. and close IDE.
  2. Install two Microsoft components manually.NET 4.0 Framework and Visual C++ 10.0 SP1 run-time redistributable components.
  3. Run the InitLicense.wsf file included with the CD image, fig.2,  to initialize the new ArchestrA Licensing sub-system.

    Figure 2: InitLicense.wsf file in DIObject CD

    We will see license subsystem Initialization success message as shown in Figure 3 (below).

    Figure 3: License subsystem initialization success message

  4. Launch ArchestrA IDE and deploy DIObjects again.

Script in InitLicense.wsf

<script language=”VBScript”>

Set oShell = CreateObject(“WScript.Shell”)

If CInt(oShell.RegRead(“HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\CurrentBuildNumber”)) > 3790 Then
If WScript.Arguments.Named.Exists(“elevated”) = False Then
‘Launch the script again as administrator
CreateObject(“Shell.Application”).ShellExecute “wscript.exe”, “””” & WScript.ScriptFullName & “”” /elevated”, “”, “runas”, 1
‘Change the working directory from the system32 folder back to the script抯 folder.
Set oShell = CreateObject(“WScript.Shell”)
oShell.CurrentDirectory = CreateObject(“Scripting.FileSystemObject”).GetParentFolderName(WScript.ScriptFullName)
End If
End If

Dim WSHShell, RegKey, OsType, FolderPath, ProgramFilesPath
Set WshShell = CreateObject(“WScript.Shell”)
OsType = WshShell.RegRead(“HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\PROCESSOR_ARCHITECTURE”)

FolderPath = “\Common Files\ArchestrA\License”

If OsType = “x86” Then
RegKey = “HKLM\SOFTWARE\Wonderware\License\”
ProgramFilesPath = wshShell.ExpandEnvironmentStrings(“%PROGRAMFILES%”)
FolderPath = ProgramFilesPath + FolderPath
‘wscript.echo  “Windows 32bit system detected”
If OsType = “AMD64” Then
RegKey = “HKLM\SOFTWARE\Wow6432Node\Wonderware\License\”
ProgramFilesPath = wshShell.ExpandEnvironmentStrings(“%PROGRAMFILES(x86)%”)
FolderPath = ProgramFilesPath + FolderPath
‘wscript.echo “Windows 64bit system detected”
End If
End If

WSHShell.RegWrite RegKey & “FlexLicFileDir”, FolderPath, “REG_SZ”

wscript.echo “ArchestrA Licensing sub-system initialization succeeded.”



Leave a Reply

Your email address will not be published. Required fields are marked *

96 − = 94