WinXPSP2 Solutions

Using Engineers Desktop
Under Windows XP SP2

2004-2005 Landmark Graphics Corporation
R2003.14 May 2005

2004, 2005 Landmark Graphics Corporation
All Rights Reserved Worldwide
This publication has been provided pursuant to an agreement containing restrictions on its use. The publication is also protected by
Federal copyright law. No part of this publication may be copied or distributed, transmitted, transcribed, stored in a retrieval system,
or translated into any human or computer language, in any form or by any means, electronic, magnetic, manual, or otherwise, or
disclosed to third parties without the express written permission of:
Landmark Digital and Consulting Solutions

2101 CityWest Blvd, Building 2, Houston, Texas 77042-3021, USA
P.O. Box 42806, Houston, Texas 77242, USA
Phone: 713-839-2000
FAX: 713-839-2401
Web: www.lgc.com
Trademark Notice
3DFS, 3D Drill View, 3D Drill View KM, 3DView, 3D Surveillance, Active Field Surveillance, Active Reservoir Surveillance,
ADC, Advanced Data Transfer, ARIES, Asset Development Center, Asset Development Centre, Asset Performance, AssetView,
Atomic Meshing, BLITZPAK, CasingSeat, COMPASS, Corporate Data Archiver, Corporate Data Store, Data Manager, DataStar,
DBPlot, Decision Suite, Decisionarium, DecisionSpace, DecisionSpace AssetPlanner, DecisionSpace AssetView, DecisionSpace
Atomic Meshing, DecisionSpace Decision Management Systems(DMS), DecisionSpace Nexus, DecisionSpace PowerGrid,
DecisionSpace PowerModel, DecisionSpace PrecisionTarget, DecisionSpace TracPlanner, DecisionSpace Well Seismic Fusion,
DepthTeam, DepthTeam Explorer, DepthTeam Express, DepthTeam Express3, DepthTeam Extreme, DepthTeam Interpreter,
Desktop Navigator, DESKTOP-PVT, DESKTOP-VIP, DEX, DFW, DIMS, Discovery, Discovery Asset, Drill-to-the-Earth Model,
Drillability Suite, Drilling Desktop, DrillModel, DSS, Dynamic Reservoir Management, Dynamic Surveillance System, EDM,
eLandmark, Engineers Data Model, Engineer's Desktop, Engineers Link, Executive Assistant, ezFault, ezSurface, ezTracker,
FG+, FastTrack, FieldPlan, FieldWorks, FZAP!, GeoDataLoad, GeoGraphix (stylized), GeoGraphix Exploration System, GeoLink,
GeoProbe, GeoProbe GF DataServer, GES, GESXplorer, GMAplus, GRIDGENR, Handheld Field Operator, I2 Enterprise, iDIMS,
IsoMap, iWellFile, Landmark, Landmark and Design, Landmark logo and Design, Landmark Decision Center, LandScape,
LeaseMap, LMK Resources, LogEdit, LogM, LogPrep, Magic Earth, MagicDesk, MagicStation, MagicVision, Make Great
Decisions, MathPack, Model Builder, MyLandmark, Nexus, Object MP, OpenBooks, OpenExplorer, OpenJournal, OpenSGM,
OpenVision, OpenWells, OpenWire, OpenWorks, OpenWorks Well File, PAL, Parallel-VIP, PetroBank, PetroWorks, PlotView,
Point Gridding Plus, Pointing Dispatcher, PostStack, PostStack ESP, PowerCalculator, PowerExplorer, PowerHub, Power
Interpretation, PowerJournal, PowerModel, PowerSection, PowerView, Production Asset Manager, PRIZM, PROFILE, Project
Administrator, ProMAGIC, ProMAX, ProMAX 2D, ProMAX 3D, ProMAX 3DPSDM, ProMAX MVA, ProMAX VSP, pSTAx,
QUICKDIF, QUIKCDP, QUIKDIG, QUIKRAY, QUIKSHOT, QUIKVSP, RAVE, RAYMAP, RTOC, Real-Time Asset
Management Center, Real-Time Asset Management Centre, Real Time Knowledge Company, Real-Time Operations Center, Real
Time Production Surveillance, Real Time Surveillance, Reference Data Manager, RESev, ResMap, RMS, SCAN, SeisCube,
SeisMap, SeisModel, SeisSpace, SeisVision, SeisWell, SeisWorks, SeisXchange, Sierra, Sierra (design), SigmaView, SimResults,
SIVA, Spatializer, SpecDecomp, StrataAmp, StrataMap, Stratamodel, StrataSim, StratWorks, StressCheck, STRUCT, Surf &
Connect, SynTool, TDQ, Team Workspace, TERAS, Total Drilling Performance, TOW/cs, TOW/cs The Oilfield Workstation,
TracPlanner, Trend Form Gridding, Turbo Synthetics, VIP, VIP-COMP, VIP-CORE, VIP-DUAL, VIP-ENCORE, VIP-
EXECUTIVE, VIP-Local Grid Refinement, VIP-THERM, WavX, Web Editor, Web OpenWorks, Well Seismic Fusion, Wellbase,
Wellbore Planner, Wellbore Planner Connect, WELLCAT, WELLPLAN, WellXchange, WOW, Xsection, You're in Control.
Experience the difference, ZAP!, and Z-MAP Plus are trademarks, registered trademarks or service marks of Landmark Graphics
Corporation.
All other trademarks are the property of their respective owners.
Note
The information contained in this document is subject to change without notice and should not be construed as a commitment by
Landmark Graphics Corporation. Landmark Graphics Corporation assumes no responsibility for any error that may appear in this
manual. Some states or jurisdictions do not allow disclaimer of expressed or implied warranties in certain transactions; therefore,
this statement may not apply to you.
Landmark Using Engineers Desktop Under Windows XP SP2
Contents
High level Summary. ........................................................................ 1

Applications ................................................................................................................. 1
Servers ......................................................................................................................... 1
Client ............................................................................................................................ 1
Firewall Issues ............................................................................................................. 1
OpenWells Firewall Issues .................................................................................... 2
Firewall Issues With Other EDT Applications ...................................................... 2
Miscellaneous Notes Regarding the Firewall .............................................................. 3
Issues With FlexLM License Checkout. ......................................... 4
Problem ........................................................................................................................ 4
Cause ...................................................................................................................... 4
Solution 1 ............................................................................................................... 4
Problem ........................................................................................................................ 6
Cause ...................................................................................................................... 6
Recommended Solution ......................................................................................... 6
Issues With SQL Server/MSDE. ...................................................... 8
Problem ........................................................................................................................ 8
Cause ...................................................................................................................... 8
Solution .................................................................................................................. 8
Issues with OpenWells (and Possibly Other EDT Applications). 10
Problem ........................................................................................................................ 10
Cause ...................................................................................................................... 10
Solution 1 ............................................................................................................... 10
Solution 2 ............................................................................................................... 10
Issues with SAM (Simultaneous Access Monitor). ....................... 12
Problem ........................................................................................................................ 12
Cause ...................................................................................................................... 12
Solution .................................................................................................................. 12
Problem ........................................................................................................................ 13
Cause ...................................................................................................................... 13
Solution .................................................................................................................. 13
Issues with Oracle (Server) ............................................................. 15
Problem ........................................................................................................................ 15
Cause ...................................................................................................................... 15
Solution .................................................................................................................. 15
Issues With Installation ................................................................... 17
Issues with Client/Server Configurations. ..................................... 17
Problem ........................................................................................................................ 17
Cause ...................................................................................................................... 17
4/20/05 i
Using Engineers Desktop Under Windows XP SP2 Landmark
Solution 1 ............................................................................................................... 17
Solution 2 ............................................................................................................... 17
Issues with iWellFile. ....................................................................... 19
Problem ........................................................................................................................ 19
Cause ...................................................................................................................... 19
Solution .................................................................................................................. 19
Problem ........................................................................................................................ 20
Cause ...................................................................................................................... 20
Solution .................................................................................................................. 20
Issues With Field Office Data Transfer........................................... 22
Problem ........................................................................................................................ 22
Cause ...................................................................................................................... 22
Solution 1 ............................................................................................................... 22
Solution 2 ............................................................................................................... 22
Problem ........................................................................................................................ 23
Cause ...................................................................................................................... 23
Solution 1 ............................................................................................................... 23
Solution 2 ............................................................................................................... 24
Problem ........................................................................................................................ 24
Cause ...................................................................................................................... 24
Solution 1 ............................................................................................................... 24
Solution 2 ............................................................................................................... 25
Issues With Some Online Help........................................................ 26
Temporary Solution ............................................................................................... 26
Permanent Solutions .............................................................................................. 26
ii 4/20/05
Landmark Using EDT Under Windows XP SP2
Using Engineers Desktop Under

Windows XP SP2
The following document was written to provide Support analysts with some guidance regarding
the use of the Engineers Desktop under Windows XP with Service Pack 2 loaded.
High level Summary.
Applications
All EDT applications appear to run fine, but the firewall needs to be
configured to allow our applications to communicate using sockets.
Servers
For Servers, the firewall needs to be configured for the LAM, and SAM
services to operate. When connecting to an Oracle Server, Oracle must
also be configured for application access.
Client
For Clients, the firewall needs to be configured to allow our
applications to connect to SAM.
Firewall Issues
To enable the firewall to allow our communications, we create
Exceptions.
We can either specify an application or a specific TCP/IP port

that is allowed to communicate.
It is much simpler to list the applications that are allowed to

communicate.
May 2005 1
Using EDT Under Windows XP SP2 Landmark
There must be consensus that this is an acceptable solution. If

there are security concerns with opening the firewall to specific
applications instead of specific ports, there will likely need to
be some code adjustments. Oracle does specify specific
applications in their configuration instead of specific ports.
This is a good indication that the application configuration is
an acceptable practice.
OpenWells Firewall Issues

OpenWells requires that we make javaw.exe an exception.
This will mean that the specific instance of javaw.exe found in our
EDT directory hierarchy will be allowed to communicate via
sockets.
This will also allow the EDM Admin Utility to create sockets as
required.
Other copies of javaw.exe on the machine will be unaffected.
When OpenWells uses RMI for some of its socket-based

communications, it opens up an seemingly random port for
communications. We can change this in future code, if we wish,
but for the moment it means we need to unblock javaw.exe
rather than specific ports.
Firewall Issues With Other EDT Applications

Each of the other EDT applications needs to be made an exception,
so that it can communicate with SAM.
No exception was required for MSDE to connect remotely and

operate.
Exceptions were required for Oracle, on the Server side only, for
Client applications to connect.
We have not checked the effects of Windows XP SP2 on an Oracle

server.
2 May 2005
Miscellaneous Notes Regarding the Firewall

When an application runs and requests socket access for the first time,
the firewall will pop up and ask Do you want to keep blocking this
program? You can respond with Keep Blocking, Unblock, or
Ask Me Later.
By pressing the Unblock button you are created an Exception

so that the program can create sockets.
When you select to Keep Blocking, the applications are still able
to launch. The risk here is that there are instances where specific
functionality will fail to work. This is not always apparent,
however. For Example, when blocking OpenWells (javea2.exe),
the application will run. SAM functionality will show as active
(the SAM icon is enabled), but the functionality will not work
accordingly (multiple users can edit the same record at the same
time). Our highly recommended solution is to unblock these
applications.
When selecting Ask Me Later, the firewall will not prevent

access, but will continue to prompt the user each time the
application is launched.
May 2005 3
Issues With FlexLM License Checkout.
Problem
Application reports Unable to find a valid EDM license.
Cause
If XP SP2 is installed on a LAM server, it will block TCP access on
ports required to honor license access requests.
Solution 1
Configure the firewall on the LAM server to give access required as an
Application.
Here are the steps to accomplish this:
1. On the LAM Server, log in as an administrator.
2. Open the Windows Firewall found in the Control Panel.
3. Click on the Exceptions tab.
4. Add licsvr.exe as an exception:
Click the Add Program button of the Windows Firewall

dialog.
Click the Browse button of the Add a Program dialog.
Select <install directory>\c:\Landmark\LAM\bin\licsrv.exe,

and click the Open button. (The path on your system may
vary).
Click OK on the Add a Program dialog.
5. Add lmgrd.exe as an exception:

dialog.
4 May 2005
Select c:\Landmark\LAM\bin\lmgrd.exe, and click the Open

button. (The path on your system may vary.)
6. Click OK in the Windows Firewall dialog.
Solution 2
Configure the firewall on the LAM server to give access required as a
Port.
1. On the LAM Server, log in as an administrator.
4. Add Port 2013 as an exception:
Click the Add Port button of the Windows Firewall dialog.
In the Name field, enter Landmark LAM Port 2013.
In the Port number Field, enter 2013.
Select the TCP radio button.
Click OK on the Windows Firewall dialog.
May 2005 5
Problem
Program Startup is Very Slow (~20 Seconds in Our Test) Due to Slow
License Checkout.
Cause
LAM on the client is trying different (slower) mechanisms for license
checkout before it successfully connects.
Recommended Solution
Configure the client to only use a TCP/IP connection to perform the
license checkout.
1. Determine the TCP/IP port number used by the LAM Server.
Using Notepad, open C:\Landmark\LAM\license.dat on the

LAM Server.
Find the line beginning with the word SERVER.
The last number on that line is the port number. On our install
it is 2013. Remember this number for a later step.
Close Notepad.
2. On the Client Machine Server, log in as an administrator.
3. Remove the cached LICSRV_LICENSE_FILE setting in registry:
run regedit.exe.
Navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License
Manager.
If there is a LICSRV_LICENSE_FILE entry, rename it

old_LICSRV_LICENSE_FILE.
Close regedit.exe.
6 May 2005
4. Set LM_LICENSE_FILE Environment variable to connect

directly to LAM server using TCP/IP.
Start the System applet in the Control Panel.
Click the Advanced tab of the System Properties dialog.
Click Environment Variables button.
Locate LM_LICENSE_FILE in the system variables.
Edit LM_LICENSE_FILE and set it contents to <port>@<lam

server name>. For example, my TCP/IP port it 2013 and server
name is LAMSERV, therefore
LM_LICENSE_FILE=2013@LAMSERV.
Click OK to close Environment Variable dialog, and again for

System Properties.
May 2005 7
Issues With SQL Server/MSDE.
Problem
If an outside connection is attempted to the SQL Server (MSDE)
database, access is denied. Therefore, a SQL Server (MSDE) database
located on an XP machine with SP2 installed will not be accessible to
its remote users.
SQL Server Enterprise Note
A corporate SQL Server is NOT affected since SQL Server Enterprise will only
install on Windows 2000 Server or 2003 Server both of which do not use SP2.
Cause
If XP SP2 is installed port 1433 is blocked by default. This port is used
by SQL Server for its communications channel.
Solution
Configure the firewall on the SQL Server to give access to port 1433.
1. On the SQL Server, log in as an administrator.
4. Add port 1433 as an exception:
In the Name field, enter a descriptive name for the port.
In the Port number field, enter the port 1433.
Select the TCP or UDP protocol, depending on what your

program uses.
8 May 2005
Click the Change Scope... button to view or to set the scope

for the port exception, and click OK.
Click OK to close the Add Port dialog.
May 2005 9
Issues with OpenWells (and Possibly Other EDT

Applications).
Problem
When starting OpenWells, the Windows Security Alert Window
Reports Windows Firewall has blocked some features of this program.
Name: javaw, Publisher: Unknown
Cause
OpenWells has created an RMI objects which requires network access.
Solution 1
Click on the Unblock button of the Windows Security Alert dialog.
This will allow the copy of javaw.exe installed with EDM to initiate
network access.
Solution 2
Prior to launching the application, configure the firewall to give access
required for the application. Each application will need to be
configured as such. Only OpenWells (javew.exe) is included in this
solution.
Here are the steps required to accomplish this:
1. On the Application System, log in as an administrator.
4. Add javaw.exe (or the other application path and executable) as an

exception:

dialog.
10 May 2005
Select <install directory>\EDT\Common

Files\JDK\jre\bin\javaw.exe, and click the Open button.
May 2005 11
Issues with SAM (Simultaneous Access Monitor).
Problem
After starting an EDT application (e.g., OpenWells), the SAM icon is
slow to appear, and then has a red X through it.
Cause
The copy of SAM on the server cant get required network access due
to the Windows Firewall.
Solution
You need to give the SAM Service (aka DSRegisteryService.exe) rights
to open TCP port listeners.
1. On the SAM Server, log in as an administrator.
4. Add DSRegisteryService.exe as an exception:

dialog.
Select <install directory>\C:\Landmark\EDT\Common

Files\JDK\jre\bin\client\DSRegistryService.exe, and click the
Open button. (The path C:\Landmark may vary on your
system).
12 May 2005
Problem
After configuring the SAM Server to access TCP ports through the
Windows Firewall, starting EDT applications (e.g. OpenWells), the
SAM icon shows as enabled, but SAM is not functioning. SAM shows
as enabled, but when a record is in use, the in use icon does not display.
Important: This is a huge problem, because the user will be unaware

that SAM is not functioning properly, as the SAM icon will indicate
that the service is functioning! There will be no messages indicating
that another user is modifying the record and there is risk that a user
will overwrite other users work.
Cause
The applications have not been configured in the Windows Firewall. As
a result, SAM messages are not received. The service is running, but
the SAM messages are not received.
Solution
configured as such. Only OpenWells (javew.exe) is included in this
solution.
4. Add javaw.exe (or the other application path and executable) as an

exception:

dialog.
May 2005 13
Select <install directory>\EDT\Common

Files\JDK\jre\bin\javaw.exe, and click the Open button.
14 May 2005
Issues with Oracle (Server)
Problem
After starting an EDT application (e.g., OpenWells), and logging into
an EDM Oracle Database, an error is displayed with: The information
entered is not valid for connecting to the selected data source. Note
that this error can be generated for a number of reasons. Specific to
Windows XP SP2, the solution is provided below,
Cause
This issue only seems to occur when connecting to an Oracle Server
from an Oracle Client machine. It does not seem to happen on the
Oracle Server itself. The Oracle Client does not have access to the
Oracle Server.
Solution
You need to give the Oracle application rights to open TCP port
listeners.
1. On the Oracle Server, log in as an administrator.
4. Add oracle.exe as an exception:

dialog.
Select (%ORACLE_HOME%\oracle.exe) <install

directory>\<ora directory>\bin\oracle.exe, and click the Open
button.
May 2005 15
5. Add tnslsnr.exe as an exception:

dialog.
Select (%ORACLE_HOME%\tnslsnr.exe) <install

directory>\<ora directory>\bin\tnslsnr.exe, and click the Open
button.
16 May 2005
Issues With Installation
No specific issues were found while installing or uninstalling EDT

applications.
Issues with Client/Server Configurations.
Problem
When starting Client/Server applications (OpenWells) from a Client
machine, the Windows Security Alert window reports Windows
Firewall has blocked some features of this program. Name: javaw,
Publisher: Unknown.
Cause
EDT applications (OpenWells) create RMI objects which requires
network access.
Solution 1
This will allow the copy of javaw.exe installed with EDT to initiate
network access.
Solution 2
Prior to launching the application, configure the Client system firewall
to give access required for the application. Each application will need
to be configured as such. Only OpenWells (javew.exe) is included in
this solution.
May 2005 17
4. Add Server instance of the javaw.exe (or the other application path
and executable) as an exception:

dialog.
Navigate to the Server install directory and select <Server

install directory>\EDT\Common Files\JDK\jre\bin\javaw.exe,
and click the Open button. (For example,
\\caltest03xp\e\landmark\EDT\OpenWells\Bin\javaw.exe).
18 May 2005
Issues with iWellFile.
Problem
When attempting to launch an iWellFile session from a Client machine,
an error page is generated, indicating that the Server could not be
found.
Cause
The iWellFile Internet Port on the Web Server has not been configured
for firewall access.
Solution
Configure the iWellFile Internet Port on the Web Server for firewall
access. By default, the iWellFile installation sets the Internet Port to
Port 80. This is configurable though, and may be different, depending
on your installation/configuration. This solution assumes that Port 80 is
the iWellFile Internet Port.
1. On the Web Server, log in as an administrator.
Click OK of the Windows Firewall dialog.
May 2005 19
Problem
After logging into an iWellFile session, selecting the Wellbore
Schematic component generates an error page indicating Access
Denied.
Cause
DCOM configuration has changed with Windows XP SP2. DCOM has
to be reconfigured for the Wellbore Schematic Server.
Solution
You need to reconfigure the Wellbore Schematic Server in DCOM.
1. From Windows Start menu, select Run.
2. Type DCOMCNFG.EXE, click OK.
3. From the selection tree, navigate to Console Root > Component

Services > Computers > My Computer > DCOM Config.
4. Right click Schematic Server, select Properties.
5. Select the Security Tab.
6. Under Launch and Activation Permissions, select the Custom

radio button.
7. Under Launch and Activation Permissions, click the Edit button.
8. Add the Local machine Users group (e.g. <\\caltest03xp\Users>).
9. Select the Local machine Users group (e.g.

<\\caltest03xp\Users>).
10. Select the Local Launch - Allow check box.
11. Select the Local Activation - Allow check box.
12. On the Launch Permission dialog, click OK.
20 May 2005
13. On the SchematicServer Properties dialog, click OK.
14. Close the Component Services window.
May 2005 21
Issues With Field Office Data Transfer
Problem
When starting Field Office Data Transfer, the Windows Security Alert
window reports Windows Firewall has blocked some features of this
program. Name: FOTransfer, Publisher: Unknown.
Cause
Field Office Data Transfer has created an RMI objects which requires
network access.
Solution 1
This will allow the copy of javaw.exe installed with EDT to initiate
network access.
Solution 2
configured as such. Only Field Office Data Transfer (FOTransfer.exe)
is included in this solution.
4. Add FOTrans.exe (or the other application path and executable) as

an exception:

dialog.
22 May 2005
Select <install directory>\EDT\Common Files\Data

Services\FOTrans.exe, and click the Open button.
Problem
When configuring Field Office Data Transfer as a Sender using FTP
protocols, when Testing the Connection, an error is displayed with:
Interner: Connection Reset
Cause
The FTP protocols require access to Port 21. The Sender firewall
prevents the utility from gaining access to the Port.
Solution 1
Open Port 21 in the firewall configuration.
1. On the Application system, log in as an administrator.
In the Name field, enter FTP Port 21.
Select the TCP radio button
May 2005 23
Solution 2
Configure FTP Server access to the firewall.
3. Click on the Advanced tab.
4. Under the Network Connection Settings section, click the Settings

button.
5. Select the Ftp Server checkbox. This will also bring up a Service
Settings dialog.
6. Confirm FTP configuration. Click OK
7. On the Advanced Settings dialog, click OK.
8. Click OK on the Windows Firewall dialog.
Problem
When launching Field Office Data Transfer configured to use FTP
protocols, an error is displayed with: Interner: Connection Reset.
Cause
The FTP protocols require access to Port 21. The Sender Firewall
prevents the utility from gaining access to the Port.
Solution 1
Open Port 21 in the Firewall configuration.
24 May 2005
In the Name field, enter FTP Port 21.
Solution 2
Configure FTP Server access to the Firewall.
3. Click on the Advanced tab.
4. Under the Network Connection Settings section, click the Settings

button.
5. Select the Ftp Server checkbox. This will also bring up a Service
Settings dialog.
6. Confirm FTP configuration. Click OK.
7. On the Advanced Settings dialog, click OK.
8. Click OK on the Windows Firewall dialog.
May 2005 25
Issues With Some Online Help
Windows XP SP2 includes improvements to Internet Explorer security

that are intended to help most users by stopping local web pages that
contain "active content" from accessing your computer maliciously.
"Active content" includes JavaScript, Java applets and ActiveX
controls. Even very innocuous JavaScript such as that found in online
help is deemed by Microsoft to be active content, and will trigger this
security setting. OpenWells and EDM Administration Utility use
WebHelp files of this type.
When you try to open the help file in either of these two applications,
Internet Explorer displays a light-yellow information bar, warning you
that it is blocking active content. (Note that this behavior only occurs in
Internet Explorer, not in other browsers, such as NetScape or Mozilla).
The following graphic illustrates the behavior.
Internet Explorer pops

up this information bar
and blocks the content.
Temporary Solution
If you want to view the help file, click the bar and select Allow
Blocked Content from the drop-down menu. A warning dialog will
appear, which you must acknowledge by clicking Yes. Now you will be
able to view the help page. This will occur each time you access the
help.
Permanent Solutions
You may choose to permanently allow Internet Explorer to view Active
Content on local files. This will prevent the warning from appearing
again. There are two permanent solutions you can choose from:
Solution 1: Turn off the security check for active content in the
Internet Explorer
26 May 2005
Solution 2: Replace the WebHelp provided by Landmark with

FlashHelp provided by Landmark on CD Vol 5 and 6. This
solution requires you to download the Flash plug-in from the
Macromedia website.
Details follow.
Permanent Solution 1
To turn off the active content security check in the Internet Explorer for
the local machine:
1. From the Tools menu in Internet Explorer, select Internet

Options.
2. Navigate to the Advanced tab in the Internet Options dialog and

then scroll down to the Security section.
3. Enable the checkbox labeled "Allow active content to run in files

on My Computer".
Please note that this may allow malicious active content in files on your
local computer to cause problems, so you should only do this if you feel
confident in your computer's security measures.
Permanent Solution 2
You can replace the WebHelp files for OpenWells and EDM Admin
Utility with FlashHelp files (requires Flash plug-in version 6 or higher
to be installed on your machine). To do this, proceed as follows:
Download Flash Plug-in:
1. Find out if you have Flash plug-in version 6 or higher installed:
Open http://www.macromedia.com/shockwave/welcome in
your Internet Explorer browser.
In the Macromedia Flash Player box, move the mouse over

the About box to show the currently installed version.
2. If you already have the Flash plug-in installed, proceed to Step 3.

If not, go to Macromedias website (http://www.macromedia.com/
downloads/) to download the plug-in:
May 2005 27
Under Download Free Players select Macromedia Flash

Player.
Uncheck Yahoo! TOOLBAR (Not required for operation of

Flash Player).
Click Install Now, and follow any prompts.
Replace WebHelp Files with FlashHelp Files:
3. Files for replacing WebHelp with FlashHelp in the EDM

Administration and OpenWells applications can be found on the
Volumes 5 and 6 CDs respectively in the directory
\Products\EDT\Docs. The following outlines the procedure for
replacing WebHelp with FlashHelp for these applications.
Copy the files FlashHelp.exe and InstallFlashHelp.bat to a

temporary directory on the drive containing the Engineers
Desktop 2003.14 applications. For the OpenWells application,
use the files found in the Vol 6
CD\Products\EDT\Docs\OpenWells Help folder on the CD.
For the EDM Administration application, use the files found in
the Vol 5 CD\Products\EDT\Docs\EDM Admin Help folder on
the CD.
Run the InstallFlashHelp.bat file from the temporary location.

This file will rename the current WebHelp folder and extract
the FlashHelp to the applications help folder.
Follow the prompts in the batch file.
Launch the application help system to verify that the new help
system is working.
Now when you access the Help files from EDM Administration Utility
or OpenWells, FlashHelp versions of the help will open, and the
security check will not be triggered.
28 May 2005

WinXPSP2 Solutions

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WinXPSP2 Solutions

Uploaded by

Copyright:

Available Formats

Using Engineers Desktop

Under Windows XP SP2

R2003.14 May 2005

Landmark Digital and Consulting Solutions

All other trademarks are the property of their respective owners.

High level Summary. ........................................................................ 1

Using Engineers Desktop Under

High level Summary.

We can either specify an application or a specific TCP/IP port

It is much simpler to list the applications that are allowed to

There must be consensus that this is an acceptable solution. If

OpenWells Firewall Issues

Other copies of javaw.exe on the machine will be unaffected.

When OpenWells uses RMI for some of its socket-based

Firewall Issues With Other EDT Applications

No exception was required for MSDE to connect remotely and

We have not checked the effects of Windows XP SP2 on an Oracle

Miscellaneous Notes Regarding the Firewall

By pressing the Unblock button you are created an Exception

When selecting Ask Me Later, the firewall will not prevent

Issues With FlexLM License Checkout.

Here are the steps to accomplish this:

1. On the LAM Server, log in as an administrator.

2. Open the Windows Firewall found in the Control Panel.

3. Click on the Exceptions tab.

4. Add licsvr.exe as an exception:

Click the Add Program button of the Windows Firewall

Click the Browse button of the Add a Program dialog.

Select <install directory>\c:\Landmark\LAM\bin\licsrv.exe,

Click OK on the Add a Program dialog.

5. Add lmgrd.exe as an exception:

Click the Add Program button of the Windows Firewall

Click the Browse button of the Add a Program dialog.

Select c:\Landmark\LAM\bin\lmgrd.exe, and click the Open

Click OK on the Add a Program dialog.

6. Click OK in the Windows Firewall dialog.

Here are the steps to accomplish this:

1. On the LAM Server, log in as an administrator.

2. Open the Windows Firewall found in the Control Panel.

3. Click on the Exceptions tab.

4. Add Port 2013 as an exception:

Click the Add Port button of the Windows Firewall dialog.

In the Name field, enter Landmark LAM Port 2013.

In the Port number Field, enter 2013.

Select the TCP radio button.

Click OK on the Add a Program dialog.

5. Add Port 2013 as an exception:

Click the Add Port button of the Windows Firewall dialog.

In the Name field, enter Landmark LAM Port 1166.

In the Port number Field, enter 1166.

Select the TCP radio button.

Click OK on the Add a Program dialog.

Click OK on the Windows Firewall dialog.

Here are the steps to accomplish this:

1. Determine the TCP/IP port number used by the LAM Server.

Using Notepad, open C:\Landmark\LAM\license.dat on the

Find the line beginning with the word SERVER.

2. On the Client Machine Server, log in as an administrator.

3. Remove the cached LICSRV_LICENSE_FILE setting in registry:

If there is a LICSRV_LICENSE_FILE entry, rename it

4. Set LM_LICENSE_FILE Environment variable to connect

Start the System applet in the Control Panel.

Click the Advanced tab of the System Properties dialog.

Click Environment Variables button.