DrillNET Installation Guide
DrillNET Installation Guide
Version 2.0.2
Installation Guide
Rev. 12
Trademarks
PetrisWINDS® is a registered trademark of Petris Technology, Inc., in the United States and other countries. Other
parties’ trademarks or service marks are the property of their respective owners, and should be treated as such.
Disclaimer
The instructions and descriptions contained in this document are accurate as of the document’s first printing.
Succeeding products and documents are subject to change without notice. Petris Technology, Inc. assumes no
liability for damages incurred directly or indirectly from errors or omissions in this document, or from discrepancies
between the product and this document. Any parameters that the customer uses beyond those indicated in this
document may have unpredictable results.
Documentation
Samantha Royder
Alastair Doyle
Last Revision
August 29, 2012
4. FAQ ..................................................................................................................................................... 67
4.1 THE SYSTEM ADMINISTRATOR HAS SET POLICIES TO PREVENT THIS INSTALLATION. ................ 67
4.2 WHEN I RUN DRILLNET, I GET A MESSAGE “CANNOT CONNECT TO THE LICENSE SERVER
SYSTEM.” OR “ERROR IN FLEXLM - -1.” ................................................................................................ 67
4.3 EXCEEDING THE NUMBER OF LICENSES FOR MODEL .................................................................... 67
4.4 EXCEED THE NUMBER OF DRILLNET LICENSES ............................................................................ 68
4.5 NOT LICENSED TO USE A PARTICULAR DRILLNET MODEL ........................................................... 68
4.6 UNABLE TO OPEN FILES ON NON-ENGLISH INSTALLATIONS .......................................................... 69
Revision History
Rev. Date Of Issue Author Scope
12 29-Aug-2012 David Jones Added 3rd-party attributions.
11 5-Jul-2012 Alastair Doyle Update for v2.0.1
10 15-Mar-2012 Alastair Doyle More 2.0 updates
09 12-Jan-2012 Alastair Doyle More 2.0 updates.
08 17-Nov-2011 Alastair Doyle Update for v2.0
07 12-Jul-2010 Samantha Royder Version change to encompass all 1.7
releases.
06 30-Mar-2010 Samantha Royder Framework requirements update.
05 18-Mar-2010 Alastair Doyle Screenshot changes and adjustments to
installation procedure.
04 2010/03/15 Samantha Royder Formatting.
03 2010/03/05 Alastair Doyle Updates to procedure.
02 2009/12/09 Samantha Royder Screenshot replacements for FLEXlm
and LMTools. Removal of Setup.ini
file reference.
01 2009/10/23 Samantha Royder Addition of XP instructions and
Borrowing License Key sections.
00 2009/10/21 Samantha Royder Initial Creation from previous docs.
DrillNET application
DrillNET application
DrillNET application
DrillNET application
Database Server
DrillNET application
Windows XP 32 Bit
.NET 3.5, SP1
.NET 4 (Extended)
Microsoft Installer 4.5
Microsoft PowerShell
SQL Server Express 2008, R2
SQL Server System CLR
SQL Management Objects (SMO)
Windows 7, 32 Bit
.NET 4 (Extended)
SQL Server Express 2008, R2
SQL Server System CLR
SQL Management Objects (SMO)
Windows 7, 64 Bit
.NET 4 (Extended)
SQL Server Express 2008, R2
SQL Server Compact Edition SP2 – x86
SQL Server Compact Edition SP2 – x64
SQL Server System CLR
SQL Management Objects (SMO)
2. Click Continue to launch a web browser with the correct URL to download .NET
Framework from the Microsoft Download site. A second small popup will also be
displayed which prompts you to click on Continue once .NET has been installed which
will then continue through the rest of the DrillNET installation.
4. From the File Download popup you can either run the exe directly or save the file to a
local folder. In case the exe is needed again at a later date, use the save option and once
saved, run the exe to install .NET Framework 4.
Click Continue on the dialog box launched by the DrillNET installation to continue with the
installation process.
1. Click Install Sql Express to launch a web browser with the correct URL to download
SQL Server Express R2008 R2 from the Microsoft Download site for the OS that you
are using. In the example below, this version of SQL is for 32 bit Windows XP. You can
either run the SQL install directly or save to disk in case it is required at some future
date.
Note : You will need to have installed .NET Framework 3.5 SPI, Windows Installer 4.5 and
Windows Powershell if installing on Windows XP. If .NET and Installer are not detected you
will get the following message displayed.
2. A second small popup will also be displayed which prompts you to click Continue after
the SQL Server installation has completed.
5. The following images show most of the typical screen you will see during the software
installation.
9. Next click Continue on the dialog box launched by the DrillNET installation to continue
with the DrillNET installation.
Installing DrillNET v2 on XP
Having installed .NET Framework 4 and SQL Server Express Server 2008 R2 plus its associated
pre-requisites, when you launch or continue the DrillNET installation you will initially be
prompted to install Microsoft SQL Server System CLR Types and SQL Management
Objects (SMO).
When you click on install a link to the required file is launched where you can click on Run to
install the software.
You will then be prompted to install the SQL Management Objects (SMO). Click on Install to
install this product.
1. After all required software has been installed the InstallAnywhere Introduction screen is
displayed. Click Next to continue with the installation.
3. On the DrillNET Install Folder screen either accept the default directory (recommended) or
use the Choose option to browse to an alternative folder. Once selected click Install.
4. Enter the instance name of the SQL Server Express and the database name in the Database
Wizard. Click Next to accept the defaults or continue after making your selection.
5. Accept the default to Use Windows authentication for the User and click Next.
If the database is successfully installed the Database Wizard indicates this with green text to
say that the Database installation succeeded. If there are any issues the error message will be
displayed in red text. Click Finish to complete the DrillNET installation.
Click install to access the Microsoft Download Center where the required software can be
downloaded.
Save the software to a temporary folder unless you wish to retain it for a future installation.
Navigate to the location where the software was stored where you will find files for 32 (x86) and
64 (x64) bit OS’s.
If you run the 32 bit file SSCERuntime_x86-ENU you will usually only get options to either
Repair or Remove which suggests that the software is already installed on 64 bit Windows and
there will be no need to proceed further with the x86 process so you can cancel from that part of
the installation.
When you run the 64 bit version SSCERuntime_x64-ENU follow the prompts as detailed to
install this software.
If you also want to remove .NET Framework 3.5, SP1 and SQL Server Express R2008 R2 then
these can be removed using the Add or Remove Programs option.
The “Database server” field is initialized with the list of SQL Server instances in the local
machine, defaulting to the “SQLEXPRESS” instance if it exists; otherwise, the first instance in
alphabetical order is selected.
The database server has the syntax “ServerName”\”InstanceName”. The previous image shows
the “SQLEXPRESS” instance in the “DSEGURA” server. If no instance is created, that part can
be ignored, leaving only the server name. That is called the default instance. The “DSEGURA”
items is an example of such an instance in this image.
To connect to a remote server and instance, it must be entered in the “Database server” field.
The next image shows the DatabaseWizard pointing to a remote database which in this example
is on the node vtdwdb39.
DrillNET makes a distinction between a “Local” and “Central” database. The DatabaseWizard
determines that a database is local if it is located on a machine whose name is the same as the
local machine name. If the machine name is not the same as the local machine then the database
is considered to be central.
The “Database name” field is initialized with the string “DrillNet”, but it can be any database
name.
The “Make this the default database” check box is checked by default. This means that DrillNET
will connect to this database automatically. If this box is cleared, the database can be
created/updated, but the name of the database DrillNET connects to automatically will not be
changed.
<Config>
<Databases currentConnection="Local">
<CentralDatabase authenticationType="WindowsAuthentication” userPassword=""
userName="" databaseName=DrillNET20” serverName=”vtdwdb39"/>
<LocalDatabase authenticationType="WindowsAuthentication” userPassword=""
userName="" databaseName=DrillNet205_1”
serverName=”DSEGURA\SQLSRV2K8"/>
</Databases>
The “Databases” node contains two children: “CentralDatabase” and “LocalDatabase”, with the
necessary information to connect to either database.
The attribute “currentConnection” of the “Databases” node indicates what database to connect to
when DrillNET is started. In this case, it reads
currentConnection="Local"
Clicking “Next” shows the “User” dialog where the user authenticates to the Sql server.
The “Use Windows authentication” box is selected by default. This indicates that the account
used to log in to Windows will be passed to Sql server to authenticate the user.
Unchecking that box will enable the “User name” and “Password” fields where a sql account can
be entered to authenticate the user.
Sql server defaults to allow only Windows authentication when being installed; it can be changed
to allow both “Sql server” and “Windows” authentications during the installation or at a later
point.
Clicking “Next” attempts to connect to that server with the given credentials to retrieve the path
where the databases are usually stored in that server.
The first three items in the list below show the default, the “SQLEXPRESS” and the
“SQLSRV2K8” instances in this machine.
They are all started. If the “SQLEXPRESS” instance is stopped while DatabaseWizard attempts
to connect to it, the following message is displayed …
and the wizard will not proceed. On some occasions the user authenticated to the server may not
have all of the necessary rights to access the objects needed by the wizard, which will result in
the following message being displayed.
In that case, the wizard continues, but tries to use the temporary folder “%TEMP%” to store the
database in the server. In the image below, note that the path to the temporary folder contains the
user name “dsegura” in this case, so it is user specific.
The DrillNet.mdf file is known as the database data file. The “DrillNet.ldf” is the log file. These
files can be renamed and placed in any folder in the server.
The path for the new database can be changed if its data and log files are desired in a different
location. It is important to note that these paths are relative to the machine hosting the sql server,
which might not be the local machine. A path that exists in the local machine might not exist in a
remote server. If the DatabaseWizard can obtain those paths from the server, then they actually
exist.
If the database already exists in the server, the “Data file” and “Log file” fields are disabled and
shown as grey text as shown below, since their name and location cannot be changed once the
database is created. In this case an upgrade operation is performed instead.
Once the installation has concluded, a green message informs of the success of the operation.
If the database operation fails, a red message informs of the failure. This image shows a failure
due to the lack of memory in the machine. A minimum of 2 GB of RAM are needed for
DatabaseWizard to work successfully.
DrillNET contains the CurrentValue for the DBVersion it can work successfully with, and it
checks it when a connection is opened to the database.
When a database change is introduced, the DBVersion is updated to match the DrillNET file
version when the change was made. This file version can be seen in the “File Version” column in
Windows Explorer. The following image shows the 2.0.1.5 file version.
If the database structure has not changed, its DBVersion does not change, even though the
DrillNET file version keeps changing as new builds are created. DrillNET 2.0.1.5 works with a
database whose DBVersion is 2.0.1.4 – the last time a change was introduced.
During the DrillNET installation, DatabaseWizard is launched to give the user a chance to create
or upgrade a database. If DatabaseWizard is closed without succeeding, the installation warns
about the possibility of DrillNET not working correctly with the following message:
If an already existing and updated database is going to be used by DrillNET, there is no need to
run DatabaseWizard. Nevertheless, if needed, it can be launched from the DrillNET installation
folder e.g. “C:\Program Files\Petris\DrillNET20” at any time. This application is the only
supported mechanism to create and upgrade DrillNET databases. No database scripts or separate
applications are supported at this time.
FROM LMTOOLS:
A graphical user interface to the license server manager tools is provided with this
installation called LMTOOLS. Some of the functions LMTOOLS performs include:
Starting, stopping, and configuring FLEXnet License server systems.
Setting system information, including host ids.
Getting server status.
Run LMTOOLS.EXE (default path is C:\Program Files\Petris\DrillNET20). Click
the System Settings tab. There you will find your Computer/Hostname and Ethernet
Address. Send this information to Petris. It should look something like this:
4. You will then be asked to enter the full path where the license file is located.
You may use the browse button to navigate to the location of the DrillNET
license file. After entering the appropriate path click Next.
Some critical elements of the license file that would be worth being aware of are …
Once DrillNET has been installed, if you do not put a valid license file in place the model
options in the application will display as greyed out text strings when you attempt to run
the application.
You may also see the following error message if you attempt to run DrillNET without a
valid license file
After installing DrillNET we would recommend that the license file that you are sent by
the Petris Houston office is copied to the folder
C:\Program Files\Petris\DrillNET20
which will be the default location for your software installation. It makes it easier to
manage your system if you keep the files in one location and as previously detailed, if
you do copy your license file to this location you will not be prompted to specify the
location when you run the software for the first time.
The first time you run DrillNET or if this is an upgrade and the license file cannot be
found in the expected location which is stored in the PC’s Registry, a pop up dialog box
will appear which will allow you to browse to the location of your new license file (this
was illustrated earlier in this chapter). Once the correct license has been selected and you
have finished the license file selection dialog, when you start DrillNET it will show the
models with valid license keys in black text.
To resolve this problem you need to setup the DrillNET executable to be run as an
administrator. Navigate to the DrillNET installation folder, right click on the DrillNET
executable and select Properties.
Choose the Compatibility tab and check the option “Run this program as an
administrator”. Restart DrillNET and the application should now run without an error
messages.
3. Select the Action menu option and Properties from the pulldown list.
4. Select the Advanced tab and click on Settings beneath Environment variables
7. Run DrillNET and confirm that the license key is being read correctly.
4. In the Path to the lmgrd.exe file field, verify the license server system path. If
incorrect or blank, enter or browse to lmgrd.exe for this license server system.
(Default path is C:\Program Files\Petris\DrillNET20\)
5. In the Path to the license file field, verify the license file field path. If incorrect or
blank, enter or browse to the license file for this license server system. (Default
path is C:\Program Files\Petris\)
6. Leave the Path to the debug log file blank.
7. Check the Use Service check box first, then the Start Server at Power Up check
box to set the service to start when the computer powers up. When the machine is
rebooted, the license server manager will start automatically as a Windows
service.
8. To save the new Petris License Manager Service, click Save Service. Click Yes.
2. Once the Server has started successfully you will see a Using License File
path at the bottom of that screen.
3. Petris License Manager License server system starts and writes its debug log
output to C:\Program Files\Petris\DrillNET\DrillNET.log.
2. A dialog box will be displayed that will allow you to input the Computer name of the
License Server System. Enter the License Server Status name that was obtained in
section 3.4.5 above in the field provided and click Next.
3. A dialog box indicating that the License Finder was successful in finding the
Server and will launch the DrillNET application.
Answer : You have no program installation privilege to install DrillNET, ask your system
administrators to install DrillNET.
Answer : License server has not started yet. You must start the license server to run DrillNET.
Contact you System Administrator to check the License Server.
Answer : If you run DrillNET and all the licenses for a particular module are in use, this error
will occur. Clicking OK will run the DrillNET application but will display only the Data Sheet
in the model area of the application. By selecting a different Model, one where the number of
licenses is not exceeded, that module will run properly.