1MRK500115-UEN - IET 600 Installation Guide-rV
1MRK500115-UEN - IET 600 Installation Guide-rV
1MRK500115-UEN - IET 600 Installation Guide-rV
The software or hardware described in this document is furnished under a license and may be used,
copied, or disclosed only in accordance with the terms of such license.
Trademarks
Hitachi Energy is a registered trademark of Hitachi Energy Group. All other brand or product names
mentioned in this document may be trademarks or registered trademarks of their respective holders.
Warranty
Please inquire about the terms of guarantee from your nearest Hitachi Energy representative.
Disclaimer
We reserve the right to make technical changes or modify the contents of this document without prior
notice.
The data, examples and diagrams in this manual are included solely for the concept or product
description and are not to be deemed as a statement of guarantee properties. All persons
responsible for applying the equipment addressed in this manual must satisfy themselves that each
intended application is suitable and acceptable, including that any applicable safety or other
operational requirements are complied with. In particular, any risks in applications where a system
failure and/or product failure would create a risk for harm to property or persons (including but not
limited to personal injuries or death) shall be the sole responsibility of the person or entity, applying
the equipment, and those so responsible are hereby requested to ensure that all measures are taken
to exclude or mitigate such risks.
This document has been carefully checked by Hitachi Energy but deviations cannot be completely
ruled out. In case any errors are detected, the reader is kindly requested to notify the manufacturer.
Other than under explicit contractual commitments in no event shall Hitachi Energy be responsible or
liable for any loss or damage resulting from the use of this manual or the application of the
equipment.
Important notice
Experience has shown that reliable operation of our products is assured, providing the information
and recommendations contained in these Operating Instructions are adhered to.
It is scarcely possible for the instructions to cover every eventuality that can occur when using
technical devices and systems. We would therefore request the user to notify us directly or our agent
of any unusual observations or instances, in which these instructions provide no or insufficient
information.
In addition to these instructions, any applicable local regulations and safety procedures must always
be strictly observed both when connecting up and commissioning this equipment.
We expressly accept no responsibility or liability for any damage, which may result from operation of
this equipment, even if no reference is made to the particular situation in the Operating Instructions.
1MRK500115-UEN Rev. V Table of contents
Table of contents
Section 9 Annex............................................................................................................33
9.1 Software Under Open Source Licenses Used in IET600.................................................... 33
9.1.1 LumenWorks.Framework.IO............................................................................................. 33
9.1.2 Log4Net.............................................................................................................................33
9.2 Known MSSQL Server Installation Problems......................................................................33
9.2.1 Incompatibility of MSSQL Server 2008 with MSSQL Server 2008 R2.............................. 33
9.2.2 Verify Existing IETSERVER Instance(s)............................................................................34
9.2.3 Installation Fails due to Pending Reboot...........................................................................34
9.2.4 MSSQL Server and Encryption......................................................................................... 34
IET600 uses some additional software components from Microsoft. If they are not contained on your
basic Windows installation already, these will be installed by the IET600 Prerequisites package (see
New Installation of IET600), they do not require any additional licensing from your side:
• Windows Installer 5
• .NET Framework 4.8
• SQL Server 2014 Express SP3
This chapter is valid if you install IET600 5.4 or later on a new PC. If you upgrade from an installation
of IET600 5.3 FP2 or older, please see chapter Upgrading from IET600 5.3 FP2 and earlier.
1. IET600 Prerequisites :
Contains the above mentioned software components and configures a special MSSQL instance
IETSERVER2 as a database where IET600 will later store its data.
The IET600 Prerequisites need to be installed only for the first time on a new PC or if you are
upgrading from an older IET600 5.2.x installation or if you need to install .NET Framework 4.8
offline.
2. ABB IET600 Setup :
Installs the 5.4.x version of IET600
When inserting the USB memory stick, the following screen appears.
IET600 is now installed in the Destination folder. A Shortcut is also available on the Desktop to start
the program.
IET600 5.3 FP8 or later requires at least Microsoft .NET Framework 4.8. This can be installed in two
different ways depending on your PC configuration.
Microsoft .NET Framework 4.8 will be deployed with the IET600 Prerequisites 5.2.5 or later.
With this setup you can also update the .NET Framework of an earlier IET600 Prerequisites 5.2.x
installation. No internet connection is required.
The .NET Framework 4.8 can be downloaded from the Microsoft Download Center.
If the following condition are fulfilled, you can upgrade the .NET Framework when you run IET600 5.4
the first time:
• An earlier version of IET600 Prerequisites (5.2.0 - 5.2.2) is already installed on your PC.
• .NET Framework 4.5 or later is installed.
• Your PC has access to the internet.
Upgrade steps:
4. Save and run the .NET Framework 4.8 web installer package.
5. Follow the Wizard to complete the installation.
6. Run IET600 5.4 again.
When you obtained IET600, you should have received a Dongle that contains the License:
Connect this Dongle to a USB-Port of the PC on which you have IET600 installed (all necessary
software components, drivers etc. have been installed along with IET600). It may take the system up
to 10 seconds to recognize the License; after that time you can start IET600 and use it.
If you try to start IET600 and no license is found on your PC, you may get the following error
message:
In this case, the Dongle has either not been plugged in or has not been recognized. If possible,
correct the problem and click OK.
Occasionally it happens that after an installation, the License Manager Service does not start; or that
it unexpectedly stops. If this service is not running and you try to start IET600, the following dialog
will appear:
If you have administrator rights, you can start the service again manually:
Open the Services Management console ( services.msc or Control Panel /Administrative Tools /
Services ).
Check whether the service Sentinel Local License Manager is running, otherwise start it from the
context menu:
If you do not have administrator rights, you need to reboot your PC.
This chapter applies, if you have IET600 5.3 FP3 (IET600 5.3.3xx). If you had older
versions (IET600 5.3.2xx or smaller), see Upgrading from IET600 5.3 FP2 and
earlier.
An IET installation package has the version name included, e.g. ABB IET600 SAS Setup - Baseline
5.3.305.zip.
To allow you to easily check for available updates, IET600 provides an in-built check.
We distinguish between:
• Bugfixes
• Updates (adding of minor features, improvements etc.).
• Upgrades (adding of considerable new functionality).
IET600 has an inbuilt check whether any of the above updates are available (see chapter "Checking
for Updates").
If the version differs only in the 4th digit (e.g. 5.3.305.1 against 5.3.305.2), it is a “bugfix”.
As the older version is considered to be buggy and should not be used in future, a bugfix version will
overwrite the corresponding older version with the same 1st, 2nd and 3rd digit (e.g. 5.3.305.2 will
overwrite 5.3.305.1, but not 5.3.304.x).
It is recommended to always install such “bugfix” versions. They do not require a new license.
IET600 is under continuous development, small features which enhance usability, engineering
efficiency etc. are added continuously. So that you may soon take advantage of these, IET600
provides “Feature Updates”.
Versions differs in the 3th digit (e.g. 5.3.11 against 5.3.10) will typically contain such improvements or
additional features, but no major changes.
Such a version will be installed in parallel to existing versions; i.e. existing versions will not be
removed. However, if you open a project in the newer version, it may require a migration after which
a project cannot be opened in older versions. It is strongly recommended to always open a project in
the older version one more time and make a backup before opening it in the new version.
Changes in the operation of IET in such versions are typically slight and can be understood
intuitively, no re-training is required.
While such versions are tested against common project configurations, they very occasionally
introduce a bug or change a behaviour in a way that is unexpected to the engineer. It is therefore
recommended to delay an update when in critical periods of engineering; otherwise an update is
recommended and uncritical as you can always go back to using an older version installed in parallel.
“Feature” updates usually require no new license, but there may be exceptions. See chapter
"Checking for Updates" to find out whether a new license is required.
If the version differs in the 2nd digit (e.g. 5.3 against 5.2), it will contain major new features. Usually a
training will be required for users to familiarize themselves with new editors, concepts or engineering
processes.
Such a version will be installed in parallel to existing versions; i.e. existing versions will not be
removed. If you open a project in the newer version, typically a migration will be required, after which
a project cannot be opened in older versions. It is strongly recommended to always open a project in
the older version one more time and make a backup before opening it in the new version.
Major updates usually will require a new license, but there may be exceptions. See chapter
"Checking for Updates" to find out whether a new license is required.
2. Open the Updates tab. It will show you the current IET600 version.
5. If you click on Download Updates, you will be offered a Zip-file for download and you can select
where to save it. A successful download will be confirmed:
6. Now you can install the downloaded Zip file as described in chapter New Installation of IET600).
Normally, no new prerequisites should be needed, otherwise you will be informed accordingly in
Step 4.
IET600 uses MSSQL as a database to store its projects; MSSQL is installed in the ABB IET600
Prerequisites setup.
Until IET600 5.3.2xx MSSQL Server® 2008 Express was used. Any earlier IET600 version used the
same MSSQL version, therefore there was no need for any upgrade.
To support Windows 10 (which IET600 5.3 FP3 or newer supports), MSSQL Server® 2014 Express
is required. It will be installed in parallel to the older MSSQL Server® 2008 Express.
New projects created with IET600 5.3 FP3 or newer will therefore be residing on a different database
than the old ones. Unlike in earlier updates, you will not see any projects from older IET600 versions,
but must take an additional step to transfer them to the new database, from where they can then be
migrated and opened like in earlier IET600 Updates.
You may use both MSSQL Server® versions in parallel, if you need to work with both IET600 5.3
FP2 (or older), and IET600 5.3 FP3 (or newer) on the same PC. Also for the upgrade described here,
you need both versions.
To prevent conflicts between the two MSSQL server products, several names and folders have been
changed in IET600 5.3 FP3. The following table gives an overview of the differences:
IET600 5.3 FP2 or older IET600 5.3 FP3 – FP5 IET600 5.3 FP6
IET600 Version 5.1.x or older Version 5.2.x – 5.2.3 Version 5.2.4
Prerequisites
MSSQL Server Product MSSQL Server® 2008 MSSQL Server® 2014 MSSQL Server® 2014
Express SP2 Express SP3 Express
MSSQL Server Instance IETSERVER IETSERVER2
Name
Project Subfolder \IETProjects\ \IETProjects\ \IETProjects\
project projectSQL2014 projectSQL2014
Project Backup File .ietprj .ietprj2 .ietprj2
Extension
To make it easy for you, you can get access to IET600 5.4 the same way as any normal update (see
chapter "Checking for Updates"). However, not only the comparatively small IET600 installation
package will be downloaded, but a new version of the IET600 Prerequisites which are more than 10
times the size.
Therefore, please do not be surprised if download and installation take considerably longer than
usual.
You can verify that everything went well after the installation by opening the Microsoft “Computer
Management” Dialog:
In case of an upgrade, the services should be configured as shown in the above image.
Today’s Microsoft operating systems have miscellaneous mechanisms to either prevent accidental
deletion of program components or restore them automatically. A Repair of an IET600 installation
should therefore be needed only rarely.
If you decide to do a Repair, you need to have the Installation package of the particular IET600
version, which you want to repair, available.
GUID-F0124825-A925-4832-A36C-D2F5675114EB V1 EN-US
3. One more dialog will ask you for confirmation. If you confirm with Install, the IET600 version will
be repaired.
Repairing an IET600 installation will not repair a defective MS SQL Server installation which is also
needed by IET600 for correct functioning.
A ‘Repair’ of IET600 Prerequisites should be needed only rarely as most components are part of the
operating system (for these components, the IET600 Prerequisites just ensure that they actually exist
in older version of the operating system).
In rare cases, the MSSQL Server may need a repair. You can try a repair directly; experience shows
however, that quite often, MSSQL IETSERVER2 needs to be removed first to ensure a clean install/
repair afterwards.
If you decide to do a ‘Repair’, you need to have the Installation package of the particular IET600
Prerequisites, which you want to repair, available.
GUID-3BE57076-7A0B-41D0-A94A-55E792C5D17A V1 EN-US
3. One more dialog will ask you for confirmation. If you confirm with Install, the IET600
Prerequisites version will be repaired.
Uninstalling an IET600 version removes only this particular version. Other versions as well as data
such as IET projects, project backups, licenses etc. will not be removed.
You need to have the installation package of the particular IET600 version, which you want to
remove, available.
GUID-3F48FEA5-B819-40E7-A2E3-333D508E0D78 V1 EN-US
3. One more dialog will ask you for confirmation. If you confirm with Remove, the IET600 version
will be removed.
If you do not have the original IET600 Installation package available, you can also remove IET600
from the Control Panel.
• System components which cannot be uninstalled without potentially affecting other programs.
• MS SQL Server 2014 with the Database instance IETSERVER2
Removing IET600 Prerequisites will not remove any of those components, but will only remove some
few Registry entries. Once you remove IET600 Prerequisites, you may not be able to install IET600
packages.
If you intend to remove the MSSQL Server component, please see chapter Remove MSSQL/
IETSERVER for instructions.
The IET600 Prerequisites do not show up in the system as programs which can be uninstalled;
uninstallation this way is not possible.
GUID-ABE274D7-19C3-4094-8324-CD6ED33AE8EE V1 EN-US
1. One more dialog will ask you for confirmation. If you confirm with Remove, the IET600 version
will be removed.
When using MSSQL, it is installed as different instances which are independent of each other.
Unfortunately, when uninstalling it, this is made apparent only relatively late in the uninstallation
process.
While you are using IET600 5.3 FP3 and newer, you must not uninstall IETSERVER2.
While you are using IET600 5.3 FP2 and older, you must not uninstall IETSERVER.
For an Upgrade from IET600 5.3 FP2 and older to IET600 5.3 FP3 and newer, you need both
IETSERVER and IETSERVER2 instances.
it is considered good security practice to remove applications which you do not need anymore. This
is also true for an MSSQL Server Instance.
If you uninstall any such instance, be sure to export or archive all projects from within IET600 before,
otherwise your project data may be lost!
Valid cases in which you might want to uninstall an MSSQL Server instance are:
• You have upgraded all projects from IET600 5.3 FP2 and older and do not intend to use an older
IET600 version anymore.
• You shift IET600 from a PC to another one, you have exported all projects and now want to
uninstall all IET600 components in the first PC.
Below we show how to remove an older IETSERVER instance. You might want to do this, if you have
upgraded from IET600 5.3 FP2 and older and have upgraded all projects to the newer version
Select Remove.
4. Before doing anything, the system performs several checks:
The IET600 program folder can be found under C:\Program Files (x86)\HITACHI, as shown below:
GUID-4D5901F6-0C6B-4AA8-AD9B-CBADF0774B65 V1 EN-US
For the software mentioned in this chapter, license conditions other than the IET600 ALC apply.
LumenWorks.Framework.IO is licensed under the MIT License, a copy of which can be found in:
IET600 includes Log4Net, a library providing logging services. Log4Net is software developed by the
Apache Software Foundation (http://www.apache.org) and is licensed under the Apache 2.0 License,
a copy of which can be found in:
https://logging.apache.org/log4net
When installing the IET600 Prerequisites, occasionally, they do not install correctly. Almost
exclusively, this is due to a problem in the installation of MSSQL Server.
The following chapters provide you some guidance what you can check in such a case.
IET600 5.3 FP2 and older versions rely on MSSQL Server 2008. Even though the name may
suggest otherwise, this version is not compatible with MSSQL Server 2008 R2 as the shared
components of each version will overwrite those of the other version and render it useless.
If you have any other application which requires MSSQL Server 2008 R2, the only solution is to use
IET600 5.3 FP3 with MSSQL Server 2014 (older projects from another IET600 installation can be
imported via *.ietprj files).
1. Open the Management Console (Right-Click Computer Icon on Desktop -> Manage)
2. Select Services, scroll down to SQL …
3. You should now see the following (the older IETSERVER items only exist, if you have upgraded
from an earlier installation, the two IETSERVER2 items must appear). Verify the status of each
item according to the picture below:
4. If the services are there, but SQL Server is not started, try to start it manually (right-click on the
service -> Start). If it does not start now, it may provide you an error message indicating what
has gone wrong.
5. If the services are not there, the MSSQL installation has failed.
After that, the most common reason for a failing MSSQL installation is a pending reboot. Although
the installer tries to find out about pending reboots, there are several such mechanisms in Windows,
and quite often a pending reboot is overlooked.
Reboot your PC. After reboot, before you try again to install the IET600 Prerequisites, please check
in the Task Manager in the Process Tab, if one or several msiexec.exe processes are running.
If so, already another installation process has started which will interfere again with the MSSQL
installation. This is commonly encountered in a new PC of an older Microsoft OS version (e.g.
Windows 7), the OS may download updates and security patches for 1-2 hours, and some of those
require a reboot. In such cases, it is recommended to wait till at least OS and Virus Scanner are fully
updated.
It becomes more and more common to encrypt data to protect them (e.g. due to loss of a notebook).
• Disk encryption encrypts the whole disk, on mounting the disk, its contents are decrypted and
provided to the user. Products are e.g. Microsoft Bitlocker or TrueCrypt. This can be used
concurrently with MSSQL Server.
• File-based encryption. This is most commonly tied to a User Account, so that designated files
(e.g. all files below C: /Data ) are encrypted with a user-specific key. Products are e.g.
Encrypting File System (EFS) provided by Microsoft’s operating systems.
As MSSQL Server has its own account to access its files and system databases, such systems
are only compatible, if several user accounts can be made to use the same key. This is not the
case for EFS encrypted files, you need to specifically exclude all databases and folders used by
MSSQL from this kind of encryption (per default, these are the folders C: /Data /IETDatabases
and C: /Data /IETProjects ).