OMNIA. Installation Guide SWARCO MIZAR S.R.L.
OMNIA. Installation Guide SWARCO MIZAR S.R.L.
OMNIA
Installation Guide
SWARCO MIZAR S.R.L.
A publication of
Contact:
[email protected]
Reproduction in whole or part, in any form, without the written consent of the copyright owner
is prohibited.
CONTENT
2 Introduction .................................................................................................................................... 7
9 Troubleshooting .......................................................................................................................... 68
9.1 Internet Information Service (IIS)........................................................................................... 68
9.1.1 Installation of one or more roles, role services, or features failed ................................. 68
9.2 WEB Services ........................................................................................................................ 69
9.2.1 Test procedure does not work with Firefox ................................................................... 69
9.2.2 Test procedure does not return any data ...................................................................... 72
9.3 Graphical User Interface........................................................................................................ 73
9.3.1 Server Error in ‘/Omnia/WebDesktop’ Application – The request failed with HTTP status
404: Not Found .............................................................................................................................. 73
9.3.2 Server Error in ‘/Omnia/WebDesktop’ Application ......................................................... 74
9.3.3 Failed to load data xml from ../GroupStatusPageHandler.ashx?from... ........................ 75
9.3.4 Server Error in ‘/Omnia/WebDesktop’ Application –
System.Web.Services.SoapException .......................................................................................... 76
9.3.5 Server Error in ‘/Omnia/WebDesktop’ Application – Response filter is not valid ......... 76
9.3.6 Signal Group Diagram export to PNG or PDF crashes ................................................. 77
9.3.7 Fault management not able to load data ....................................................................... 77
9.3.8 Error loading OMNIA Calendar Editor ........................................................................... 78
OM0807E18SG
1.1 Objectives
1.3 Versions
Version-
Date Change Author
number
01 18-05-2017 First version Fabio D’Aprile,
Antonella Barletta
02 12-02-2018 Various updates Antonella Barletta
03 14-03-2018 Pre-updating sanatorium and revisions Antonella Barletta
04 16-04-2018 Minor updates Antonella Barletta
05 11-05-2018 Section of creation db user and Omnia Server 1001 Antonella Barletta
error
06 23-05-2018 Section OmniaConfigManager.exe Antonella Barletta
07 14-06-2018 Various updates Antonella Barletta
08 04-07-2018 Third party and WCM changes Antonella Barletta
OM0807E18SG
1.4 Definitions
DB Database
DBMS Data Base Management System
DOS Disk Operating System
DSN Data Source Name
DTD Document Type Definition
FEP Front End Processor
HW Hardware
LAN Local Area Network
LU Logical Unit
MISTIC Mizar Software for Traffic Information Centre
MIZAR MIZAR Automazione S.R.L.
MoM Minutes of Meeting
MS Microsoft®
MS SQL Microsoft SQL Server™
OCX OLE Control eXtension
ODBC Open Database Connectivity
OLE Object Linking and Embedding
OSI Open Systems Interconnection
SQL Structured Query Language
SRT Short Receive Telegram
SW Software
TCP Transmission Control Protocol
UAC User Account Control
UDP User Datagram Protocol
UI User Interface
URL Uniform Resource Locator
VMS Variable Message Sign
XML eXtensible Markup Language
OM0807E18SG
2 Introduction
This guide intends to aid technicians involved with the installation or update of OMNIA.
The installation phases are described in this document in three main chapters which refer to
three different installation scenarios:
OMNIA can be installed on physical or virtual servers equipped with Microsoft Windows
Server 2008 R2 / 2012 / 2012 R2 / 2016.
OMNIA system databases are based on the relation database Microsoft SQL Server.
Versions 2008 R2 / 2012 / 2014 / 2016 of Microsoft SQL server are supported.
The business engines for the OMNIA were implemented using Microsoft Visual Studio 2010 /
2015.
They stand over the .NET Framework 4.0 and extensions.
These engines also use an "Open Database Connectivity" (ODBC) fully supported by “SQL
Server”.
OM0807E18SG
4 OMNIA Environment
According to the specific system requirements, OMNIA can be installed in different
approaches.
The two most common use cases described in this guide are:
A distributed installation over multiple servers
A “stand alone” installation over a single server
A typical distributed installation requires the following three servers (physical or virtual):
Database Server
Applications Server
Web Server
The following names are suggested for the servers mentioned above:
The use of these names is not mandatory since the setup packages allow using different
names; it does not affect the installation process.
It is strongly advised, however, the use of the given default names in order to establish a
standard installation procedure that aims to provide an answer to all possible questions that
may arise during the installation process.
In case of requiring this type of installation, please refer to the specific note regarding the
applicability of this particular case in the following chapters.
OM0807E18SG
A single server installation means that the three main components of OMNIA: Database,
Applications and Web components; will be installed onto one single server.
Follow the installation steps described in the following chapters concerning this case.
OM0807E18SG
OMNIA supports the operating system Microsoft Server 2008 R2 / 2012 / 2012 R2 / 2016.
The physical or virtual machines that make up the environment must have previously
installed the above operating systems. Then, a user with full administrator rights must be
allocated on all the machines and network disks required. This User shall be used during the
installation process of the Platform.
In order to disable the UAC from the policy manager, the policy of active directory must be
changed.
The kernel applications of OMNIA use some libraries created by third parties.
These packages are available from the SWARCO Mizar Download Center and are
distributed in order to simplify the installation of the Omnia on the machines that comprise
the environment:
Apps and Web machines must have previously installed the Microsoft.NET Framework
versions 4.0 or higher.
It is a standard component of the Windows operating system and the above version can be
retrieved and installed through the Omnia Installer program from the SWARCO Download
Center (Mizar Release server) or directly downloaded from Official Microsoft Download
Centre using the provided links https://www.microsoft.com/en-
us/download/details.aspx?id=42642; however it is necessary to refer to the Microsoft website
in order to download updates and / or language support.
Also important for web server installation is Microsoft Internet Information Services (IIS), a
standard component of the Windows operating system.
OM0807E18SG
Please refer to the Microsoft official Support centre for information regarding the installation
of the Microsoft Framework and related software.
Since there is only one system server, then the only concern would be to give a primary valid
IPV4 IP address to the machine.
The above names are only suggestions as the installation packages allow to define different
names as it has been previously stated into this guide.
This manual does not cover how to install Microsoft SQL Server. Please refer to the official
Microsoft support centre for information about it. This chapter only covers the features
necessary in order to install Omnia.
Install Microsoft SQL Server 2008 R2 or higher in English with all the features available
either on a dedicated server (distributed installation) or on the unique system server (single
server installation).
It is suggested to install SQL Server with “named instance" under the name "SQLOMNIA01".
The database instance name is required throughout the setup of a MS SQL Server
authentication; this is the instance name given to the TCP / IP port. The name of the
database can contain a maximum of 128 characters.
In MS SQL Server in order to install OMNIA databases you have to use an user “db_owner”
roles. For example:
Login: omniauser
Password: omnia123
If you don’t have a dedicated machine, it needs to use an administrator database user.
Default names have been suggested for the default SQL Server instance. Although these are
only suggestions and should not represent a constraint; there is however, a restriction
between the instance name and the name of the Database Server machine.
No No Yes
Special Use Case: Multiple instances of Omnia with a unique Database Server
In case of having to install multiple instances of SQL Server on the same server; it is
suggested to use the names: “SQLOMNIA01”, “SQLOMNIA02”, and so on.
In order to set up a new user, open “Microsoft SQL Management Studio” on the database
server machine and follow these steps:
Enter the username and password (Eg. “omniauser” and “omnia123”) respectively; and
remove the option about “Enforcing password policy” from the checkbox:
OM0807E18SG
Map out the user to the system databases (“master”, “model”, “msdb”, “tempdb”) and the
roles “public” e “db_owner”:
The Server machine where the Omnia applications package is to be installed must be
supplied with a physical disk for example identified with the letter “C:\” which is not
compulsory but strongly advised. In this case the Omnia applications are installed into the
directory C: \ Omnia \ Apps.
In case of setting up a distributed installation and in case of having the availability of a NAS,
it is advised to make so, that all machines that are part of the system environment, point out
to the disk “C:\” where the Omnia applications are.
The user in charge of setting up all machines of the Platform must have full Administration
rights on the disks and computers involved.
This manual is not a reference to the Windows Operating System Guide. Please refer to the
Microsoft official guide for information about disk configuration and use.
The web server computer must be supplied with Internet Information Services (IIS) version 7
or higher.
Please make sure that all of the IIS features are installed since a Standard IIS installation will
not contain all the features required by Omnia Web.
The web server engine can be customized by adding or removing modules. Integrate
pipeline processing of IIS and ASP.NET. Please refer to the guide chapters for the correct
configuration.
Use Case: Specific Web Server machine with disk C:\ within an array of shared hard disks
(NAS) amongst Database/Application/Web Server or Single System Server installation
The Omnia web components are installed into the directory C: \ Omnia \ Web, the web
commons components directly in the C: \ Omnia directory.
It is not compulsory but strongly advised to install these components into the drive “C: \”,
particularly for this use case.
Use Case: Specific Web Server machine without a disk unit C:\ into an array of hard disks
and the drive C:\ is shared amongst Database/Application/Web Server
Omnia Web components are installed in the directory <drive>:\ Omnia \ Web \, the web
commons components directly in the <drive>:\ Omnia directory.
The chapter dedicated to the installation of web and web commons components of this guide
describes how to set up the above installation directory.
In addition to the creation of the system environment and installing web and web commons
components (directory and Web applications) the installation package performs the following
actions:
6 New Installation
This type of installation applies to systems that do not have any components of Omnia
installed; that is on servers that only comply with the Microsoft packages required:
It is out of the scope of this guide to describe the installation process of the above packages.
Please refer to the official Microsoft support centre for information on how to install any of the
above software components.
These programs must be previously installed and must be working properly before installing
OMNIA.
The "STEP 1 - Download Setup Packages" must be applied on the server where Omnia is to
be installed.
The "STEP 1 - Download Setup Packages" must be repeated on each server that takes part
of the distributed environment.
Make sure that all the downloaded content was fully copied into the destination folder
C:\InstallOmnia of the appointed server.
Create the “InstallOmnia” folder on the C: \ drive of your server (C: \ InstallOmnia)
From the Browser of your choice, go to the SWARCO Mizar Download Center page:
http://products.miz.it/DownloadCenter/OmniaPackages/lastrev.html as it is shown in the
following screenshot:
OM0807E18SG
Download the program OmniaInstaller.exe by clicking on the corresponding link and save it
into the folder “C: \ InstallOmnia”.
The link to the Download Center will always return the last updated version of this
application.
Note:
Prior to executing any action to update Omnia (once an initial installation was performed),
make sure that the current version of OmniaInstaller.exe is the same as the one available on
the download page. To know the version of OmniaInstaller.exe program right click on it and
Properties/Details.
In case the version in use were older than the one available at the Download Center, then
download first the latest version and replace (overwrite) the old one (in C:\InstallOmnia\
OmniaInstaller.exe) with the new one.
OM0807E18SG
The program OmniaInstaller.exe will display an empty list of components since such
packages have not been downloaded yet from the SWARCO Mizar Download Center.
Click on the “Packages Downloader” tab for downloading the most up to date versions and
released packages from the SWARCO Mizar Download Center.
After a few seconds of downloading, depending on your internet connection speed, the
program will display a list of files and updated installation packages available for download;
as it is shown on the following image:
Select either all or individual files to be downloaded by clicking into the boxes on the left
hand side.
OM0807E18SG
Note:
The application OmniaInstaller.exe displays the list of all files available on the SWARCO
Mizar Download Center; however, only the files not yet updated locally will be downloaded.
At the end of the download process, the Platform Installer will display the following:
OM0807E18SG
Tab “Packages Downloader” will show the status of “Completed” for all files
Tab “Packages Launcher” will display the list of packages to be installed.
Don’t close the OmniaInstaller application until the end of all installation activities. Incorrect
closing of the application, however, does not cause any problems.
Actions
Use the OmniaInstaller.exe to select the option “Third Parts Components” and click on the
“Install” button.
OM0807E18SG
1) Microsoft.NET Framework
2) ASP.NET MVC 4 for Visual Studio 2010 SP1 and Visual Web Developer 2010
SP1
3) Microsoft Internet Information Services (IIS)
It should be noted that the .NET Framework components on Windows 2012 Microsoft
operating systems and above represent "server roles"; can be enabled from Server Manager.
When the OmniaInstaller launches the installation of the Framework packages, a warning is
displayed saying that this must be done through the Server Manager tool.
When this happens, proceed with the installation of the remaining components (automatically
launched) by pressing the "Close" button.
On Windows 2016, use the "Server Manager" tool in order to install the Framework
components, as follows:
In the step "Installation type" select the option “Role-based or feature based installation”:
OM0807E18SG
Go through the steps “Server Selection” and “Server Roles” to get to the “Features” screen:
Select the options “.NET Framework 3.5 Features” and “.NET Framework 4.6 Features” and
then click “Next”.
Once the installation process has finished click on the “Close” button.
OM0807E18SG
Manual Installation example of the server roles of IIS over Windows 2012
On Windows 2012, use the "Server Manager" tool in order to install the Framework
components, as follows:
3. Click on “Add roles and features” to open the “Add Roles and Features Wizard”
5. Click “Next” to start the Server Selection, select the server from the Server Pool and
next to start the configuration of the Server Roles only for selected server
6. From the Roles list, select “Web Server IIS”, “Add Roles and Features Wizard” is
OM0807E18SG
displayed
7. “Add Roles and Features” window will appear to include “Management Tools”, click
“Next”
8. Confirm the option to include management tools and click “Add Features” button to
proceed
c. locate the “Management Tools” section and select “IIS Management Scripts and
Tools” and “IIS 6 Management Compatibility” (all features).
Once the installation process has finished click on the “Close” button.
OM0807E18SG
Continue with the STEP “A” or “B” depending on the type of installation.
It is suggested to keep the “OmniaInstaller” application open until the end of all installation
activities. Closing the application mistakenly, however, does not affect the correct installation
of the platform.
The evaluation of an optimal environment for OMNIA as well as the necessary hardware will
be performed in advance by a qualified SWARCO technician.
Actions
After downloading the individual installation packages on the server, follow the next steps in
the order listed below:
install the “Omnia Database Components Management” package
Run the “OmniaDbBuilder” application in order to construct the databases on MS
SQL Server
install the “Omnia Web Commons Components” package
install the “Omnia Web Components” package
install the “Omnia WCM Service” package
install the “Omnia Applications” package
install the “Omnia Server” package
Please refer to the appropriate chapters within this guide for every step. The specific actions
to be followed that correspond to any particular Use Case can be found there.
After downloading the installation packages on all servers that belong to the system
environment, it is required to perform the following installation steps in the order stated
below. This must be repeated for every dedicated server:
Database Server
OM0807E18SG
Please refer to the appropriate chapters within this guide for every step. The specific actions
to be followed that correspond to any particular Use Case can be found there.
Install the components for every server of the platform in the following order:
1) Database Server
2) Application Server
3) Web Server
SPECIAL Use Case 1: Distributed Installation using only two servers grouping Application
and Web into one server
Even when Omnia installation is done into a single server, it is required to install its
components in the correct order.
Firstly install the database components into the Database server as stated into the
appropriate chapter.
Then, it is required to install the Omnia applications package followed by the web
components package into the same server (Application and Web machine). Please refer to
the appropriate chapter in the guide in order to do so.
OM0807E18SG
This package must be installed on the “Database Server” machine; this is the server where
MS SQL server is installed.
Actions
Use the “OmniaInstaller” application from “C: \ InstallOmnia” and select the "Omnia Database
Components" option, then click on the "InstallOmnia" button.
Press the "Next" button at the bottom of the screen to continue with the window for selecting
the installation directory:
Press "Next" and on the next input form, please edit information about:
Database Server Name – name of the machine where the installation is taking place
Database Server IP Address – primary IPV4 of the machine
OM0807E18SG
At the end of the installation, it is possible to verify the presence of the components installed
by opening the "Start" menu in Windows.
The system storage (multiple databases) is build up into the single system machine.
The system storage (multiple databases) is built up using the “Database Server”. Perform the
required actions on the database server machine.
Actions
After having installed the necessary components to build up the database, it is then possible
to build up the database for Omnia.
From the "Start" menu in Windows, launch the OmniaDbBuilder application through the
menu item:
Omnia \ Database Config Apps
OmniaDbBuilder
The application OmniaDbBuilder will be displayed with the input fields correctly filled in with
the default values that correspond perfectly to the environment to be installed.
OM0807E18SG
If necessary, change the installation paths of the database files, otherwise are used the
default paths.
Default:
Database Path: C:\Omnia\SqlData\Database
SWARCO MIZAR S.R.L. a socio unico
Via Nizza, 262/57, I-10126 Torino, T. +39-011-6500411, F. +39-011-6500444, E. [email protected]
Tribunale di TORINO 189/82 - Capitale Sociale Euro 200.000 i. v. - C.C.I.A.A. Torino 606099 – C.F. e P.I. IT03972050011
Direzione e coordinamento: SWARCO AG 38/78
SWARCO MIZAR S.R.L.
At the creation of a new database, you can write the name of it and chose the collation to use
for it. Remember that for the creation of a new database you have to use a “sysadmin” user
(e.g. the user “omniauser” created before). At the updating operation you can select the one
existing database, clicking on the button associated to the database name.
Open the tab “Script Execution” and click the button “Launch” to launch the scripts
associated to the last database revision:
Scripts will be executed for the construction of the database components contained in the
solution. A progress bar will show the status of the work.
This phase takes a few minutes, depending on the hardware used.
OM0807E18SG
Errors can be easily identified by the presence of a red icon on the left hand side. Error
details are also available through the button "Show Log".
At the end of the construction phase of the database, the application OmniaDbBuilder can be
closed by clicking the "Close" button.
OM0807E18SG
The list of databases that comprise Omnia can be seen from SQL Server Management
Studio.
The web components will be installed onto the single system machine.
Using the OmniaInstaller.exe application, select the option “Omnia Web Components” first
and “Omnia Web” then and click the install button.
This is the Welcome screen of the installation package for the web components (web
Commons and Web components):
OM0807E18SG
The installation of web components is very similar to the one of the kernel applications;
hence, enter the reference to the machines that make up the system environment.
Next, three input forms will be displayed for web components to enter the connection to the
installation machines.
Since this is an installation on a single server machine, it is required to enter the same
references for the entries:
The automated installation provide to assign the correct database server name and instance
name in the Omnia connection string in the config file, but doesn’t change the name of
database if it is different from the default “Omnia”.
1. Open Windows Explorer and browse the destination (local or network) disk where the
setup of the Web Services has been performed (i.e. C:\Omnia\Web\WebServicesApp)
2. Open the “web.config” file in the WebServicesApp directory using any textual editor
1. Open Windows Explorer and browse the destination (local or network) disk where the
tool provided by setup is located (i.e. C:\Omnia\WinApps\OmniaConfigManager.App)
2. Launch the OmniaConfigManager.exe application
3. The values presented in the form are the default values of the section
<connectionStrings> of the key “connectionString” of the file
C:\Omnia\Web\WebServicesApp\web.config:
4. Change these values as you need and save the results (clicking on the “Save” button)
OM0807E18SG
1. From the “Internet Information Services” Manager, open the Web Sites tree to the deep
level of the “Omnia\WebServicesApp”.
2. Click on “WebServicesApp” to display the list of files in the “WebServicesApp” directory
3. In the list of files, locate the file “WS_Access2.asmx”, select it and then right click to open
the drop down menu, then select “Browse”.
5. Fill the username field using the default administrator user (username=admin), then click
“Invoke” button.
OM0807E18SG
username admin
password admin
In order to be able to configure and activate the custom logo in OMNIA, you should first of all
prepare the custom logo.
Different logos for different customers will of course have different aspect ratio and they
should be adjusted to proper fit in OMNIA login and welcome page.
To ease the configuration, a SWARCO logo with the aspect ratio of 150x44 pixels is
available in the “[TARGET DIR]\Omnia\Web\WebData\UI” directory of the installation folder.
OM0807E18SG
<add key=“CustomLogo”
value="..\WebData\UI\customlogo.png|||136|||40|||205|||60"/>
Omnia WCM Service will be installed onto the single system machine.
Using the OmniaInstaller.exe application, select the option “Omnia WCM Service” first and
click the install button.
This is the Welcome screen of the installation package for the Omnia WCM Service:
OM0807E18SG
OMNIA Web Connection Manager (WCM) is the server of the communications with all the
web clients and dispatches messages between OMNIA functions and web clients.
Omnia Web Connection Manager (WCM) can be configured directly from the Omnia WCM
console web interface.
SPXTCP.DAT
IPC connections are used to interface only ‘INTERNAL APPLICATIONS’ (OMNIA managers).
Detailed settings about the IPC connections with ‘INTERNAL APPLICATIONS’ are available in the
‘sysconf.ini’.
SPXTCP.DAT file is stored in the Web Communication Manager (WCM) folder (default:
C:\Program Files (x86)\Swarco Mizar\Omnia WCM Service).
OM0807E18SG
Please remember that, if necessary, the Applications components can be installed on the
machine through the UTOPIA installation packages (Please do reference to UTOPIA-
Installation Guide).
Using the OmniaInstaller.exe application, select the option “Apps Components” and click the
install button.
This is the Welcome screen of the installation package for the web components (web
Commons and Web components) and then click on “Next” button:
OM0807E18SG
Next, three input forms will be displayed to enter the connection to the installation machines.
If this is an installation on a single server machine, it is required to enter the same references
for the entries:
In case of distributed installation insert the different values and continue until the end of the
installation wizard.
Using the OmniaInstaller.exe application, select the option “Omnia Server” first and click the
install button.
This is the Welcome screen of the installation package for the Omnia Server components:
OM0807E18SG
To solve this you have to launch the appropriate file batch, install32.bat or install64.bat
according to the SO used and then proceed with the installation of Omnia Server.
These files are available on the page of the SWARCO Download Center
http://products.miz.it/DownloadCenter/OmniaPackages/lastrev.html in the “Setup Tools” item
as “ExtensionsErrorOmniaServer.zip”.
3. If the configuration is correct, Connection state field under Connection info section
reports the state “Active”.
Before beginning any upgrade of the Omnia components, make sure you have the latest
version of the Omnia Installer application. The latest version of the Installer can be found on
the SWARCO Mizar Download Center page:
http://products.miz.it/DownloadCenter/OmniaPackages/lastrev.html
To verify the current version of the Omnia Installer from the folder “C: \ InstallOmnia”; open
up the Omnia Installer and click on the computer icon on the upper corner of the window:
In case the version in use were older than the one available at the Download Center, then
firstly download the latest version and replace (overwrite) the old “OmniaInstaller.exe” (in C: \
InstallOmnia \ OmniaInstaller.exe) with the new one.
Before you begin any upgrade, make sure that all components to be upgraded are already
installed. Use the Windows tool to check the installed programs ("Program and Features").
OM0807E18SG
The column “Version” displays the individual version number of every installed component.
Updates must be done on the server where Omnia has been installed.
Updates must be done on each server that is part of the distributed installation.
Actions
Before doing any action to install / update Omnia, make sure that the version of
OmniaInstaller.exe is lined up with the one available from the download page of the Omnia
Download Center.
Open the Web Browser of your choice and go to the SWARCO Mizar Download Center
(Mizar release server) at:
http://products.miz.it/DownloadCenter/OmniaPackages/lastrev.html
Then, check the latest distributed version:
Check the version of OmniaInstaller.exe in C: \InstallOmnia\ by doing one of the two possible
ways:
Launch the application and double click on the image located at the top of the screen
on the right hand side (the “About” window will be displayed with information about
OM0807E18SG
the version)
Right click on the executable file in order to see its properties. Look into the “Details”
section.
In case the version in use were older than the one available at the Download Center, then
download first the latest version and replace the old one (in C:\ InstallOmnia \
OmniaInstaller.exe).
Next, run the OmniaInstaller.exe located into C: \ InstallOmnia and open the tab “Packages
Downloader” in order to download the latest releases from the SWARCO Mizar Download
Center.
After a few seconds of downloading, depending on your internet connection speed, the
program will display a list of files and updated installation packages available for download.
Select all files from the list by ticking the checkbox available on top of the list at the left hand
side, as it is shown below:
OM0807E18SG
Note:
OM0807E18SG
The application OmniaInstaller.exe displays the list of all files available on the SWARCO
Mizar Download Center; however, only the obsolete files (on the local machine) will be
downloaded.
This means that all items in the list can be selected without having to worry about including
or excluding particular items from the list.
At the end of the download process, the application will display the following:
Tab “Packages Downloader” will show the status of “Completed” for all files
Tab “Packages Launcher” will display the list of packages to be installed.
At this point it is possible to proceed with the installation as if you were installing the platform
from the beginning, following its own use case.
Install only the components shown by the Omnia Download Center with a higher version to
the one currently installed (check the programs installed in Windows).
Before proceeding with the installation, write down which of the following steps must be
carried out by checking the current version and the new version available from the Download
Center:
Note:
Any update errors are protected by the verification procedures inherent in the update
packages. This means that the installation of previous versions, obsolete versions or the
installation of a version that already exists is not allowed.
Please continue with the installation packages as if it was a setup from scratch in order to
update the following components:
Follow the instructions described in the chapters according to the components to update and
its corresponding use case.
OM0807E18SG
Since it is a package “update” instead of a “new installation” the wizard will not ask for the
server names again for the packets that require them.
Note:
When the databases are updated through the OmniaDbBuilder.exe application, the data is
preserved by the update operations. The operations performed by the application concern
only to update the database structure and do not modify the data contained in it. However, it
is highly advisable to backup all databases prior to any updates.
OM0807E18SG
Before starting any upgrade action, please carefully check the details reported in the
following sections.
In every section are listed special actions and configurations eventually required to perform
the update in the proper way from that specific software release to any newer release.
Then open Windows Explorer and identify the destination folder (local or network) containing
the Web components (e.g. C:\Omnia\Web) and rename it to “__Web”.
Continue installing the OMNIA WEB Components (refer to the installation from scratch
described in the chapter "6.4.5 STEP 4.3 – Installing the web components" of this document)
and finally proceed with the manual operations described in the following chapters.
1. Open Windows Explorer and identify the destination folder (local or network) containing
the Web Services (e.g. C:\Omnia\Web\WebServicesApp).
2. The automated installation provide to assign the correct database server name and
instance name in the Omnia connection string in the config file, but doesn’t change the
name of database if it is different from the default “Omnia”.
Therefore, you have to copy the “Web.Config” file from the old Web Services folder
(“__Web\WebServicesApp”) to the updated folder
3. Restart the Internet Information Service (IIS).
4. Remove the old WebServicesApp folder (“__Web\WebServicesApp”).
2. Install new OMNIA Web Connection Manager release following the instructions available
in section 6.4.7 STEP 4.4 – Installing OMNIA Web Connection Manager (WCM) of this
document.
Actions
Note:
The notation <drive> must always be replaced with the actual installation drive.
OM0807E18SG
9 Troubleshooting
9.1 Internet Information Service (IIS)
In the “Select features“ view of the “Add Roles and Features Wizard”, disable .NET
Framework 3.5 features and repeat the setup
OM0807E18SG
In the “Select role services“ view of the “Add Roles and Features Wizard”, locate Application
Development and disable .NET Extensibility 3.5 and ASP .NET 3.5
From the Internet Information Service Window, using Firefox to browse the file
“WS_Access2.asmx” from the list of files in the “WebService” directory, the error in the
following figure is displayed.
3. In the “WebServices Properties” view, select the “Directory” tab and enable the “Directory
browsing”. Click on “OK” button to confirm the modification.
OM0807E18SG
From the Internet Information Service Window, using Internet Explorer to browse the file
“WS_Access2.asmx” from the list of files in the “WebService” directory, the view that
appears invoking the WEB service for the ‘admin’ user does not return any data (see figure
below).
1
NB: For DATABASE SERVER key, enter ‘Server Name’ (e.g. localhost) for SQL Server®
Standard Edition, ‘Server Name’\MSSMLBIZ for Small Business Edition or ‘Server
Name’\SQLEXPRESS for SQL EXPRESS Edition
SWARCO MIZAR S.R.L. a socio unico
Via Nizza, 262/57, I-10126 Torino, T. +39-011-6500411, F. +39-011-6500444, E. [email protected]
Tribunale di TORINO 189/82 - Capitale Sociale Euro 200.000 i. v. - C.C.I.A.A. Torino 606099 – C.F. e P.I. IT03972050011
Direzione e coordinamento: SWARCO AG 72/78
SWARCO MIZAR S.R.L.
Using Internet Explorer to log into Omnia, the system reports the following Server Error in
‘/Omnia/WebDesktop’ Application:
1. The request failed with HTTP status 404: Not Found
The error occurs after an update or an installation and is determined by Permissions Error
When opening signal group diagram recording, to select the date and time 4 error messages
popup every time selection is changed.
When this error occurs, check that the OMNIA folder and all its subfolders have the user
“Everyone” defined with full control rights
The error occurs clicking on the “Export data to excel” button in the Traffic data form, with
traffic data correctly loaded.
Error is determined by a bug in .NET framework release 3.5 and is fixed in the release 1.2.0
of OMNIA.
OM0807E18SG
Signal Group Diagram export to PNG or PDF could crash in case the “InkScapeExecutable”
key in the webdesktop\web.config file is not set properly.
The Fault management functionality is not able to retrieve data from the database, and a
error box appears (see next image).
3. Restart IIS
4. Try again
OM0807E18SG
The error has been documented on a Windows 2008 server 64 edition running IIS 7.
When OMNIA is started on Firefox or Internet Explorer, launching the Calendar Editor from
the shortcut provided in the Map View selection tree, the following error is displayed.