Wonderware Intouch 10.1 License File: A Simple Solution for PLCforum Users[^3^]
erdapanetwwsuite.lic - This is an older form of Wonderware's license files, and is typically used for products like InTouch 7.11 through to InTouch 10.1, as well as for older IO Servers and DA Servers, etc.. If you receive one of these files with your licenses, it is easier to install it even if you are unsure if you'll need it, as it may prevent problems later on if you do install an older version of a product (Example: an old IO Server). The format of the wwsuite.lic file and the archestra.lic file are very similar, with the determining factor primarily being the age of the software.archestra.lic - This is the newer form of Wonderware's license files. Many newer products are migrating to this file, such as InTouch 2012 and higher, Wonderware Historian, and standalone Historian Client. If you receive one of these licenses it is easier to install it, even if you are unsure if you'll need it, as it may prevent problems later on. The format of the wwsuite.lic file and the archestra.lic file are very similar, with the determining factor primarily being the age of the software.
Wonderware Intouch 10.1 License File
Download File: https://ssurll.com/2vIaaE
archestraServer.lic - This type of license file is used for server based licensing, where a central server houses the licenses, and clients connect to this license server to obtain a license. This is primarily used by Wonderware Information Server and Historian Client. Currently there are only a few Wonderware products that will make use of this type of license. If you are unsure if you'll need this license, it is typically easier to not install it, as these types of licenses may need additional configuration to specify which users/computers are allowed to obtain licenses.Some newer products such as Recipe Manager Plus utilize an online activation system. For this, you will typically receive a .XML file which when activated will become a .BIN file on the hard drive.
You may receive a .BIN file directly if you are just testing the software, as you will typically receive a preactivated license. In this case you would not use the license manager to activate the file, you will typically place this directly on the hard drive.
A softkey is used by InTouch Machine Edition (ITME), which uses the MAC address of the PC you are on, then does an online activation. In this case you will not actually receive a file, instead the license will be generated online using the ITME software and your credentials on the Wonderware website.
Wonderware enforces the use of its products with a software license. After you install a Wonderware product, you must install a single license file, ARCHESTRA.LIC, which contains your customer information, product data, and software features. Until you apply your Wonderware license, you can run the InTouch HMI only in demonstration mode.
Licenses for Wonderware products are maintained in license files or on a license server. The license file contains one or more license components, which are lines of information that specify licensing for an individual product.
Unserved licenses, also known as local licenses, are installed on the same computer as the applications using them. Unserved licenses do not run on a license server. Unserved license files usually have the file names wwsuite.lic or ArchestrA.lic.
Click
File, and then Install License File. The Choose a License File to Install dialog box appears.Browse the small license DVD (or other path to your license file), select the ARCHESTRA.LIC file, and click
Open.When the License manger launches, browse the tree in the left pane and click on the computer name. The installed license files should be shown in the right components window. Locate the
Serial Number column to the right and record the number for your records.The License Utility main window appears. Browse the tree in the left pane and click on the computer name. The installed license files should be shown in the right components window. Locate the
Serial Number column to the right and record the number for your records.InTouch HMI (v10.5) Patch 01 resolves the following issues listed by their Change Request number: L00096629: HF CR L00116487 SR 103116551: The StartApp() function in InTouch 10.1 did not correctly open the Excel spreadsheet. L00100439: HF CR L00118773 SR 15616845: Using Dynamic Resolution (DRC) replace-type windows behavee unexpectedly and closed windows already open. L00110323: HF CR L00117084 SR 41610071 HF 2355: Zooming in and printing the application output wrong coordinate positions. L00110611: HF CR L00117425 SR 19816998: On importing an InTouch window in a Managed Application, the System tags displayed as placeholders. L00110695: HF CR L00117085 SR 41610081: InTouch keypad remains open even after the parent window that invoked the keypad is closed. L00110791: HF CR L00116976 SR 33410812 HF 2294: Importing DBLoad from the IDE failed. Add a new Registry DWORD value DisableWriteToNewTag to the following Registry locations: On 32-bit operating systems: HKEY_LOCAL_MACHINE:SOFTWARE\Wonderware\Intouch\Installation On 64-bit operating systems: HKEY_LOCAL_MACHINE:SOFTWARE\Wow6432Node\Wonderware\Intouch\Installation If you do NOT intend to do a delta import from the Historian (InSQL), set the DisableWriteToNewTag DWORD value to 1 to improve the performance of the DBLoad. Otherwise, set the value to 0. L00115201: HF CRs L00114702, L00116121 SRs 33430926, 33410952]: An alarm or event record was not logged to the alarm database if one of the fields contained a single quotation mark (apostrophe). L00115667: HF CR L00114593 SR 41610130: Window location information was unexpectedly changed and saved when using the mouse scroll wheel in WindowMaker. L00115766: HF CR L00115350 SRs 33410954, 33410861: When an attribute in alarmed state had its value or alarm limit modified so that it remained in alarmed state and was then reported again due to an engine restart, the alarm was logged twice with the same timestamp but with different values. L00116359: HF CR L00113474 SR 38231312: After switching languages, then printing a window without opening it, the window did not print in the new language. L00116367: HF CR L00112069 SR 33410861 HF 2467: With the AlarmDBLogger running as a service, a local platform query to get alarms from the Galaxy flooded the Alarm database with hundreds of old alarms so that the database grew one GB in two days. Add a new Registry DWORD value ArchestrAAlarms to the following Registry locations: On 32-bit operating systems: HKEY_LOCAL_MACHINE\SOFTWARE\Wonderware\AlarmLogger\ArchestrAAlarms On 64-bit operating systems: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Wonderware\AlarmLogger\ArchestrAAlarms The new DWORD value, ArchestrAAlarms, controls how the system looks up the ArchestrA alarms. In the absence of the ArchestrAAlarms DWORD value or if it is disabled by setting its value to zero or any value other than 0, 1, or 2, the system looks up ArchestrA Alarms using the GUID (current behavior). If the ArchestrAAlarms DWORD value is added and is set to 1, then the system looks up the alarms using the TagName+OriginationTime+ProviderId combination. If the same alarm is reported by multiple InTouch alarm providers, then the alarm is considered to be separate alarms, each coming from a different provider. If the ArchestrAAlarms DWORD value is added and is set to 2, then the system looks up the alarms using the TagName+OriginationTime. If the same alarm is reported by multiple InTouch alarm providers, then only one instance of the alarm will be logged in the database. L00116419: HF CR L00116319 SR 103121430 [CAR 050820]: A NAD client opening or compiling a window for the first time resulted in error and warning messages, "Bitmap pixels and planes mismatched 32:16 1:1" and "Failed to load Window Index 10804. Stage=9 Linked=1". The windows still loaded properly. L00116551: HF CR L00116132 SR 103122267: When a condition script was configured to execute every minute, inserting data into SQL through SQL Access, WindowViewer ceased to function after less than an hour. L00116690: HF CR L00116494 SR 103122402: The Alarm DB Logger hangs with the error message, "The statement has been terminated." The conversion of a CHAR data type to a DATETIME data type resulted in an out-of-range DATETIME value. L00116865: HF CR L00116007 SR 15316210: A Smart Symbol replace operation modified many Tagnames in the Instance References column. The window was saved and closed, but when the window was reopened, the original default Tagnames appeared in the Instance