Aspen Engineering
Known Issues in V7.3
Version Number: V7.3
March 2011
Copyright (c) 2011 by Aspen Technology, Inc. All rights reserved.
Aspen Acol+™, Aspen Adsim®, Aspen Adsorption , Aspen Air Cooled Exchanger, Aspen Basic Engineering, Aspen
Batch Process Developer, Aspen Batch Distillation, Aspen Batch Plus®, Aspen BatchSep™, Aspen Capital Cost
Estimator, Aspen CatRef®, Aspen Chromatography®, Aspen COMThermo®, Aspen Custom Modeler®, Aspen
Distillation Synthesis, Aspen Dynamics®, Aspen Energy Analyzer, Aspen FCC®, Aspen Fired Heater, Aspen
FiredHeater, Aspen Flare System Analyzer, Aspen FLARENET™, Aspen HTFS Research Network™, Aspen HX-Net®,
Aspen Hydrocracker®, Aspen Hydrotreater™, Aspen HYSYS Amines™, Aspen HYSYS Dynamics™, Aspen HYSYS
OLGAS 3-Phase™, Aspen HYSYS OLGAS™, Aspen HYSYS PIPESYS™, Aspen HYSYS RTO™ Offline, Aspen HYSYS
Upstream Dynamics™, Aspen HYSYS Upstream Dynamics™, Aspen HYSYS Upstream™, Aspen HYSYS Upstream™,
Aspen HYSYS®, Aspen HYSYS® Thermodynamics COM Interface, Aspen HYSYS®, Aspen HYSYS® Pipeline
Hydraulics - OLGAS 2-Phase, Aspen HYSYS® Pipeline Hydraulics - OLGAS 3-Phase, Aspen HYSYS® Pipeline
Hydraulics - PIPESYS, Aspen HYSYS® Offline Optimizer, Aspen HYSYS® Hydrocracker, Aspen HYSYS® Reformer,
Aspen HYSYS® CatCracker, Aspen HYSYS® Petroleum Refining, Aspen Icarus Process Evaluator®, Aspen Icarus
Project Manager®, Aspen In-Plant Cost Estimator, Aspen Kbase®, Aspen MINLP Optimization, Aspen Mixed Integer
Optimizer, Aspen Model Runner™, Aspen MPIMS™, Aspen MUSE™, Aspen Online Deployment™, Aspen OnLine®,
Aspen OnLine®, Aspen OTS Framework, Aspen PIMS Advanced Optimization™, Aspen PIMS Submodel Calculator™,
Aspen PIMS™, Aspen Plate Exchanger, Aspen Plate+™, Aspen Plus Optimizer™, Aspen Plus®, Aspen Plus®
CatCracker, Aspen Plus® Dynamics, Aspen Plus® Hydrocracker, Aspen Plus® Hydrotreater, Aspen Plus®
Reformer, Aspen Polymers, Aspen Polymers Plus™, Aspen Process Economic Analyzer, Aspen Process Manual™,
Aspen Process Tools™, Aspen Properties®, Aspen Properties Mobile, Aspen Rate-Based Distillation, Aspen
RateSep™, Aspen Reaction Modeler, Aspen RefSYS Catcracker™, Aspen RefSYS Hydrocracker™, Aspen RefSYS
Reformer™, Aspen RefSYS™, Aspen Shell & Tube Exchanger, Aspen Shell & Tube Mechanical, Aspen Simulation
Workbook™, Aspen Solubility Modeler, Aspen Split™, Aspen Tasc+™, Aspen Teams®, Aspen Utilities On-Line
Optimizer, Aspen Utilities Operations™, Aspen Utilities Planner™, Aspen Zyqad™, SLM™, SLM Commute™, SLM
Config Wizard™, the Aspen leaf logo, and Plantelligence are trademarks or registered trademarks of Aspen
Technology, Inc., Burlington, MA.
All other brand and product names are trademarks or registered trademarks of their respective companies.
This documentation contains AspenTech proprietary and confidential information and may not be disclosed, used,
or copied without the prior consent of AspenTech or as set forth in the applicable license agreement. Users are
solely responsible for the proper use of the software and the application of the results obtained.
Although AspenTech has tested the software and reviewed the documentation, the sole warranty for the software
may be found in the applicable license agreement between AspenTech and the user. ASPENTECH MAKES NO
WARRANTY OR REPRESENTATION, EITHER EXPRESSED OR IMPLIED, WITH RESPECT TO THIS DOCUMENTATION,
ITS QUALITY, PERFORMANCE, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
Aspen Technology, Inc.
200 Wheeler Road
Burlington, MA 01803-5501
USA
Phone: (1) 781-221-6400
Toll Free: (1) (888) 996-7100
URL: http://www.aspentech.com
Contents
Contents.................................................................................................................iii
Introduction ............................................................................................................5
Aspen Engineering Workflows.................................................................................7
Process Engineering Console V7.3 ......................................................................7
Process Modeling (Aspen Plus) ...............................................................................9
Aspen Plus V7.3 ...............................................................................................9
OLI Interface V7.3.......................................................................................... 11
Aspen Properties V7.3..................................................................................... 11
Aspen Properties Mobile .................................................................................. 12
Aspen Custom Modeler V7.3 ............................................................................ 12
Aspen Model Runner V7.3 ............................................................................... 13
Aspen Plus Dynamics V7.3 (formerly Aspen Dynamics) ....................................... 13
Aspen Adsorption V7.3 (formerly Aspen Adsim) ................................................. 14
Aspen Utilities Planner V7.3 ............................................................................. 14
Aspen Reaction Modeler V7.3........................................................................... 15
Process Modeling (HYSYS) ....................................................................................17
Aspen
Aspen
Aspen
Aspen
HYSYS
HYSYS
HYSYS
HYSYS
V7.3 ......................................................................................... 17
Dynamics V7.3........................................................................... 18
Upstream V7.3 ........................................................................... 19
Petroleum Refining V7.3 (formerly Aspen RefSYS) .......................... 19
Exchanger Design and Rating................................................................................21
All Exchanger Design and Rating Products V7.3.................................................. 21
All Exchanger Design and Rating Products V7.3.1............................................... 21
Aspen Air Cooled Exchanger V7.3.1 (formerly Aspen ACOL+) .............................. 22
Aspen Fired Heater V7.3.1 (formerly Aspen FiredHeater)..................................... 23
Aspen Shell & Tube Exchanger V7.3.1 (formerly Aspen TASC+) ........................... 23
Aspen Shell & Tube Mechanical V7.3.1 (formerly Aspen TEAMS)........................... 24
Aspen Plate Exchanger V7.3.1 (formerly Aspen Plate+)....................................... 25
Aspen HTFS Research Network V7.3.1 .............................................................. 25
Aspen MUSE V7.3........................................................................................... 26
Aspen Plate Fin Exchanger V7.3.1 .................................................................... 26
Contents
iii
Economic Evaluation .............................................................................................27
All Economic Evaluation V7.3 Products .............................................................. 27
Aspen Process Economic Analyzer V7.3 (formerly Aspen Icarus Process Evaluation) 32
Aspen In-Plant Cost Estimator V7.3 (formerly Aspen Icarus Project Manager) ........ 32
Aspen Capital Cost Estimator V7.3 (formerly Aspen KBase) ................................. 34
Icarus Evaluation Engine V7.3 ......................................................................... 36
Energy and Flare Analysis .....................................................................................37
Aspen Energy Analyzer V7.3 (formerly Aspen HX-Net) ........................................ 37
Aspen Flare System Analyzer V7.3 (formerly Aspen FLARENET) ........................... 38
Aspen HYSYS Thermodynamics COM Interface V7.3 (formerly Aspen COMThermo). 39
Aspen Simulation Workbook .................................................................................41
Aspen Simulation Workbook V7.3 ..................................................................... 41
Process Development ............................................................................................43
Aspen Batch Process Developer V7.3 (formerly Aspen Batch Plus) ........................ 43
Aspen Solubility Modeler V7.3 .......................................................................... 44
Advanced Modeling Options (Process Development).............................................45
Aspen
Aspen
Aspen
Aspen
Batch Distillation V7.3 (formerly Aspen BatchSep) .................................... 45
Chromatography V7.3 ........................................................................... 46
Process Tools V7.3 ............................................................................... 46
Process Manual V7.3 ............................................................................. 47
Aspen Basic Engineering .......................................................................................49
Aspen Basic Engineering V7.3 (formerly Aspen Zyqad) ....................................... 49
Operations Support ...............................................................................................51
Aspen Online Deployment V7.3 ........................................................................ 51
Aspen OTS Framework V7.3 ............................................................................ 52
Aspen Online V7.3.......................................................................................... 52
Aspen Plus Based Refinery Reactors .....................................................................53
Aspen
Aspen
Aspen
Aspen
Plus
Plus
Plus
Plus
Catcracker V7.3 (formerly Aspen FCC) .............................................. 53
Hydrocracker V7.3 (formerly Aspen Hydrocracker) ............................. 54
Hydrotreater V7.3 (formerly Aspen Hydrotreater)............................... 54
Reformer V7.3 (formerly Aspen CatRef) ............................................ 55
Aspen Open Object Model Framework ...................................................................57
Aspen Open Object Model Framework ............................................................... 57
PE/PD Console ......................................................................................................59
PE/PD Console ............................................................................................... 59
iv
Contents
Introduction
This document contains a summary of known issues or limitations relating to
this release. Workarounds are suggested where possible.
Known issues are listed as those relating to:

Coexistence issues (different versions of products on the same computer).

Installation issues (potential problems arising during the install or uninstall
procedure).

Usability issues.
Please refer to the tables in each product section for issues relating to the
products you are using.
Note: For additional information about Known Issues, see the AspenTech
Support web site (http://support.aspentech.com). For additional information
about issues relevant to the complete product line, see the aspenONE Known
Issues on the Documentation DVD.
Introduction
5
6
Introduction
Aspen Engineering
Workflows
Process Engineering Console
V7.3
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Aspen Engineering Workflows
7
8
Aspen Engineering Workflows
Process Modeling (Aspen
Plus)
Aspen Plus V7.3
Coexistence Issues
Workaround/Comment
Aspen Plus will freeze when it is
trying to display the start page
when it is running on a Citrix client
connected to a server running
Windows Server 2003, and the
user account does not have
administrator privileges.
Install the patch provided by Microsoft in their
knowledge base article KB955692, which can
found at:
If multiple versions of Economic
Evaluation are installed and then
one is uninstalled, the toolbar
button and menu command to
Activate Costing may fail with an
error "Failed initializing costing. Be
sure that Economic Evaluation is
installed."
Reinstalling Economic Evaluation should fix the
problem. The Repair option from the installer
may also work.
http://support.microsoft.com/kb/955692
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
Sometimes, property tables, which
reference streams, are not regenerated
after making changes to a run.
This happens when the changes you
make are handled via an Edit Run. To
force the tables to update, reinitialize the
simulation and re-run it. You can turn off
Interactively Load Results on the
Tools | Options | Run tab to ensure
this is always updated.
Process Modeling (Aspen Plus)
9
10
General Usability Issues
Workaround/Comment
Copying and pasting the table on an
Object Manager screen (which normally
displays the names of objects, their
types, and their solution status) does
not work correctly.
The list of names of the objects copies
correctly.
Attempting to view a Custom Stream
Summary with more than 40,000 cells
might cause Aspen Plus to freeze.
Avoid doing this. Instead, use the
Results Summary | Streams form, or
use the Custom Stream Summary forms
within individual blocks, or specify
Include Streams under Setup |
Report Options | Streams to limit
which streams are reported, or move
some streams and blocks into Hierarchy
blocks so that there are not too many
streams present at any one level of
hierarchy.
When you specify a News Feed URL for
the Start Page, if you fail to include the
prefix (such as http://), Aspen Plus will
crash.
Be sure to include this prefix when
entering the News Feed URL.
When using the Heat Exchanger Design
button in the Analysis toolbar to send
heat exchanger data to EDR, if you have
a Heater block in the simulation with the
wrong type of utility specified on one
side (such as Steam for cooling or Water
for heating) then EDR may crash.
When this crash occurs, you will see the
message "Import from Aspen Plus:
Error generating PSF file. Make sure the
block is already solved," followed by an
additional error from HTFSPSF.
A ConSep block appears in the
Columns tab of the Model Library, but if
you add this ConSep block to the
flowsheet, it does not work.
Ignore this ConSep block and use the
one on the Conceptual Design tab of
the Model Library after following the
instructions in the help topic
Configuring Aspen Plus for ConSep.
When using Excel Calculator blocks, if
you define variables using the Define
tool provided in the Excel Add-in, Excel
may crash.
Define variables on the Define sheet in
Aspen Plus before opening Excel.
If this occurs, verify the type of utility
and direction of temperature change for
each Heater block in the simulation.
Process Modeling (Aspen Plus)
OLI Interface V7.3
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Aspen Properties V7.3
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Process Modeling (Aspen Plus)
11
Aspen Properties Mobile
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
Upgrading a V7.2.1 Aspen Properties
Mobile server to the V7.3 version
overwrites any customizations to the
web.config file.
Save a copy of the web.config file before
upgrading. If Aspen Properties V7.3 has
been installed, the new web.config will
be configured to use this version and the
latest databanks, along with the LDAP
configuration entered during the
installation. Any other changes to the
web.config will need to be manually
copied into the file provided by the new
version.
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Aspen Custom Modeler V7.3
12
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
You can export Structures from Aspen
Custom Modeler for use in Aspen Plus.
However if you attempt to use these in
Aspen Plus it does not work reliably, and
may cause a crash. Exporting of Models
for use in Aspen Plus works fine.
Do not export Structures for use in
Aspen Plus. You can still instance
Structures within models that you export
to Aspen Plus.
Process Modeling (Aspen Plus)
General Usability Issues
Workaround/Comment
The PolyPlus example contains Aspen
Plus input files that can no longer be
loaded by Aspen Plus V7.3. The
following files: hpde.inp, nylon6.inp,
pp.inp and ps.inp contain references to
the PURE10 databank which is no longer
supported by Aspen Plus.
Open the files in Notepad and change all
instances of the string PURE10 to
PURE25. The edited files should now
load in Aspen Plus.
On some systems, the Regen example
might fail when you click on the Launch
ACM button in the Regen Control Panel.
Open the file RegenDemo.sln in Visual
Studio and rebuild the project. The new
version of the program RegenDemo.exe
should now launch ACM.
Aspen Model Runner V7.3
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Aspen Plus Dynamics V7.3
(formerly Aspen Dynamics)
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Process Modeling (Aspen Plus)
13
Aspen Adsorption V7.3
(formerly Aspen Adsim)
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Aspen Utilities Planner V7.3
14
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Process Modeling (Aspen Plus)
Aspen Reaction Modeler V7.3
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Process Modeling (Aspen Plus)
15
16
Process Modeling (Aspen Plus)
Process Modeling (HYSYS)
Aspen HYSYS V7.3
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
Importing a MUI file into HYSYS Plate
Fin link only partially completes and LNG
unit op fails to solve.
You should import the MUI file before
mapping LNG passes to EDR stream
numbers.
Using the Beggs and Brill correlation
(1973 or 1979) for inclined segments in
the HYSYS Pipe operation can give
incorrect pressure drops if the same
correlation is not selected for horizontal
pipes.
To use a Beggs and Brill correlation for
the inclined segments within a HYSYS
pipe operation, the same correlation
must also be selected for the horizontal
segments. This is necessary because the
wrong flow regime correlation is used,
which causes an incorrect pressure drop
calculation. However, if the other
correlations (HTFS, OLGAS,
Gregory/Aziz/Mandhane) are used for the
inclined segments, then any correlation
can be selected for the horizontal
segments.
Valve in Steady State Rating Mode
Cannot Determine Choking Conditions
This happens because the current steady
state solver cannot solve the pressure
drop and choking conditions
simultaneously.
Component Splitter Is Slow in Solving A
Large Sparse Split Specification Matrix
Try to avoid such a large and sparse
setup.
Process Modeling (HYSYS)
17
General Usability Issues
Workaround/Comment
Use of Aspen Properties from HYSYS
(Retired Databanks)
When a fluid package is created by
importing an Aspen plus/Aspen
Properties backup file which contains the
retired databanks (PURE10, PURE93,
PURE856, AQU92), the fluid package
may not have the necessary pure
component databanks required for a
meaningful simulation. This is because
the retired databanks (which no longer
exist in the default APV73 database) are
not automatically upgraded to the latest
pure-component databanks (i.e., PURE25
and AQUEOUS). As a result, some or all
of the components specified in the
backup file may not have access to the
necessary property parameters. This can
cause the simulation to fail or to give
inaccurate results. The workaround is to
select the latest pure component
databanks (PURE25 and AQUEOUS) on
the Enterprise Databases tab of the
Component List View.
Export Heat Exchanger Heat Curves to
ABE:
None
a) Tube-side vapor-phase thermal
conductivity values are incorrect.
Shell-side values are transferred
instead of tube-side values.
b) Vapor-phase mass-density values
are incorrect: molar density is
transferred instead of mass
density.
Aspen HYSYS Dynamics V7.3
18
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
No known issues
Process Modeling (HYSYS)
Aspen HYSYS Upstream V7.3
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
Conceptual Design Builder: Profiles plots
do not to show correctly in the excel
profile report.
Profile data is correctly exported to Excel
so it can be used to generate the plots
manually.
Conceptual Design
Builder/Stabilizer Column: When
using crudes from the Assay Library
together with an RPV specification, the
stabilizer column has difficulties
converging.
It is recommended in this case to select
the TVP specification.
Aspen HYSYS Petroleum
Refining V7.3 (formerly Aspen
RefSYS)
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
If you are using a reformer,
hydrocracker, or an FCC, or a flowsheet
with one of these models, HYSYS may
crash due to the extra memory
requirements for the new start page.
You should disable the start page if you
are using one of the reactor models. When
HYSYS opens, the start page will show. In
the lower-left-hand corner of the start
page, uncheck Show Start Page Next
Time. Exit and restart HYSYS.
Process Modeling (HYSYS)
19
20
General Usability Issues
Workaround/Comment
The Petroleum column does not
calibrate when calibration is triggered by
FCC flowsheet.
You should calibrate the FCC reactor first
and then the petroleum column. This will
require you to enter the calibration data
directly into the petroleum column
calibration environment since data may
have been improperly transferred from
the FCC.
When you try to save big Petroleum
Refining cases as XML, the application
will crash, giving a message that it is
low on memory
In general XML is not supported for
Petroleum Refining cases.
The Healy method for RON/MON
blending gives unrealistic numbers and
the problem is apparent either in stream
properties or in the product blender.
Select the Volume Blending method in
Petroleum Assay Manager view > Property
Blending Methods for RON / MON option.
If you attach a product stream to the
reformer or hydrocracker and then
delete the stream, it will also delete the
internal stream. At that point, you will
no longer be able to connect a product
stream to the model and HYSYS may
hang or crash when solving the model.
You should always disconnect the product
stream from the reformer or hydrocracker
before deleting the stream.
Process Modeling (HYSYS)
Exchanger Design and Rating
All Exchanger Design and
Rating Products V7.3
This section contains a summary of known issues or limitations relating to this
release. Workarounds are suggested where possible.
All Exchanger Design and
Rating Products V7.3.1
This section contains a summary of known issues or limitations relating to this
release. Workarounds are suggested where possible.
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
CQ00392063 – Labels are missing in
Headings / Remarks
Select Tools | Program Settings,
Headings/Drawing tab and click OK.
This only need be done one time;
thereafter, the labels are present.
In Input | Problem Definition |
Headings/Remarks, the labels such as
Company:, Location:, Service of Unit:,
etc., are missing for new cases.
Affects all EDR applications.
CQ00294553 – There is a HYSYS closedown error after EDR-Shell&Tube or
EDR-AirCooled results have been
viewed.
There is no corruption of data.
Affects HYSYS used with EDR
Exchanger Design and Rating
21
General Usability Issues
Workaround/Comment
CQ00413119 – Aspen properties fails to
work after transfer from AirCooled to
Plate.
After doing a Run-Transfer from Aspen
Air Cooled Exchanger to Aspen Plate
Exchanger, EDR appears to hang while
Aspen Properties starts. The workaround
is to save and close EDR and then reopen
only the Aspen Plate Exchanger case.
Affects all EDR applications.
CQ00397130 – File-Open crashes if EDR
has exported to Excel.
Affects all EDR applications.
CQ00378264 – EDR fails to identify the
property method specified in the Aspen
Properties aprbkp file.
Affects all EDR applications.
If an EDR file has been exported to Excel
and then File-Open is selected, EDR will
crash. The workaround is to export to
Excel and then close and reopen EDR.
EDR does not display the Aspen
Properties property method in imported
.aprbkp or referenced .aprpdf files;
EDR always displays AMINES. This is a
display issue only; the Aspen Properties
method specified in the Aspen Properties
file is used.
Aspen Air Cooled Exchanger
V7.3.1 (formerly Aspen ACOL+)
22
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Exchanger Design and Rating
Aspen Fired Heater V7.3.1
(formerly Aspen FiredHeater)
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Aspen Shell & Tube Exchanger
V7.3.1 (formerly Aspen TASC+)
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
CQ00430263 – Import from an Aspen
Plus block, such as HEATER, shows a
negative pressure drop in EDR Process
data.
If the inlet stream pressure is less than
the block pressure, a negative pressure
drop will be imported. The workaround is
either to specify a pressure drop for the
block or change the inlet and/or block
pressures to ensure a positive pressure
drop.
Affects Shell&Tube.
For a block with multiple feed streams,
the lowest stream pressure is used in the
EDR Process data. One workaround is to
add a mixer block upstream of the block
and make sure a positive pressure drop
results.
Exchanger Design and Rating
23
The Advanced method is not yet
available for kettles or double pipe
exchangers.
None. The Standard Method gives wellproven results.
Affects Shell&Tube.
The warning messages to show the
estimate of the required number of
intermediate supports (for no-tube-inwindow exchangers) and U-bend
supports do not appear.
Affects Shell&Tube
The messages should appear when the
required number of supports to prevent
serious vibration warnings exceeds the
input values.
The vibration output will still indicate that
there is a vibration problem when the
input number of supports is insufficient.
The number of supports required to
eliminate the problem can easily be
found by trial and error.
The tube pitch on the tube pattern
schematic on the Tube Layout diagram
is incorrect.
The error is in the schematic only, the
tube layout and related calculations use
the correct value and are not affected.
Affects Shell&Tube and Shell&Tube
Mechanical.
The similar schematic in Shell&Tube
Mechanical – TEAMS_Tube_Layout – is
correct.
Aspen Shell & Tube Mechanical
V7.3.1 (formerly Aspen TEAMS)
24
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
The tube pitch on the tube pattern
schematic on the Tube Layout diagram
is incorrect.
The error is in the schematic only, the
tube layout and related calculations use
the correct value and are not affected.
Affects Shell&Tube and Shell&Tube
Mechanical.
The similar schematic in Shell&Tube
Mechanical – TEAMS_Tube_Layout – is
correct.
Exchanger Design and Rating
Aspen Plate Exchanger V7.3.1
(formerly Aspen Plate+)
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Aspen HTFS Research Network
V7.3.1
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Exchanger Design and Rating
25
Aspen MUSE V7.3
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Aspen Plate Fin Exchanger
V7.3.1
26
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Exchanger Design and Rating
Economic Evaluation
All Economic Evaluation V7.3
Products
The following section describes known issues that can apply to all Evaluation
V7.3 Products.
Coexistence Issues
Workaround/Comment
Users running Microsoft Windows with
Windows Installer 3.1 may experience
coexistence issues with Economic Evaluation
V7.2 and previous versions as described
below:
1. Update Windows Installer to
version 4.5, which can be
downloaded from the following
site.
1. The following aspenONE applications are
installed on a machine:
http://www.microsoft.com/downl
oads/details.aspx?FamilyID=5a58
b56f-60b6-4412-95b954d056d6f9f4&displaylang=en
o
EEV7.2.1 (or EEV7.2), EEV7.3
o
HYSYS and/or Aspen Plus V7.2+EPs
2. Invoking the Export to EE feature in
either HYSYS or Aspen Plus invokes
EEV7.2.1 (or EEV7.2) instead of EEV7.3.
This may occur if none of the EE installed
software versions are run after
installation. This is due to the windows
installer resiliency behavior. Once the
problem occurs in one user environment,
it is observed with all other users on that
machine.
Note: See the installation guide on
how to check which version of
Windows Installer is present on
your system.
1. Ensure EE V7.2.1 (or EEV7.2)/V7.3
is executed as standalone
application before invoking EE via
HYSYS V7.2 (or Aspen Plus V7.2).
2. In cases where the problem
occurs, an upgrade/repair
installation of EE V7.3 can be
performed by running the EE V7.3
installation again. The procedure
allows the EE V7.3 to be reset as
the default costing feature w/
HYSYS /Aspen Plus V7.2.
Comment: Following the steps below
on the system where EE V7.3 is
installed alongside previous versions of
EE can avoid the aforementioned
issues.
Economic Evaluation
27
1. Update the Windows Installer to
version 4.5
2. Launch EE V7.2.1 (or EEV7.2) and
allow the EE V7.2.1 Windows
Installer resiliency to go through, if
this the first time EE V7.2.1 is
being launched under this user
account.
3. After c;psomg EE V7.2.1, launch
EE V7.3 and allow the EE V7.3
Windows Installer resiliency to go
through, if this is the first time EE
V7.3 is being launched under this
user account.
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
The Manpower Productivity Expert (MPE) is
not supported on 64 bit operating systems
(for example, Microsoft Windows 7 or Vista 64
bit). Users running these operating systems
will not be able to run this feature. All other
Economic Evaluation features are functional
within these environments.
None.
Retrieval of stream pricing specified in a
HYSYS simulation cannot be retrieved by
APEA at this time.
None.
Note: Support for retrieval of HYSYS stream
pricing is available in the V7.3.1 release of
APEA. Refer to the What’s New Section of the
V7.3.1 APEA Release Notes for further
information.
CQ418712
Aspen Basic Engineering (ABE) V7.2 (+ EPs)
will not function with ACCE V7.3.
Note: This EP is not required in order for ABE
V7.3 to function with ACCE V7.3 (or ACCE
V7.3.1).
Comment:
An emergency patch has been issued
for ABE V7.2 to integrate with ACCE
V7.3. Please refer to Solution ID#
130686 on the Aspen Technology
Support Site and follow the
instructions on installing this EP. Once
installed, ABE V7.2 will function with
ACCE V7.3.
Note: The new equipment models contained
in EE V7.3 do not have corresponding class
views in either ABE V7.2 or V7.3. Thus, data
for these components will not flow between
the applications via the Cost Mapper.
28
Economic Evaluation
General Usability Issues
Workaround/Comment
CQ425673
In order to see the Last Mappings, an
insignificant change can be made in
the simulator and after
running/reloading the data, the
Mapping process will default to Last
Mapping and the previous mappings
will now appear.
When using integrated sizing and costing in
Aspen Plus or HYSYS, if a Mapping process is
completed without Sizing and the Mapping
process is again initiated without a simulation
change, the Mapping GUI will not show the
Last Mappings made (even if the Last
Mappings box is checked). Although, the
system ‘remembers’ the Last Mappings, the
GUI will not show them. This means if the
user tries to map the unit ops once again,
duplicate components will be created.
CQ425575
Projects created in EE V7.2 (not EE V7.2.1)
containing air dryers will lose the flowrate
specification when the project is opened in
either EE V7.2.1 or V7.3. The field will be
blank and if a project evaluation is made, this
item will not be included in the estimate.
Note: This defect has been corrected
in the V7.3.1 release of APEA.
The flowrate will need to be
respecified when projects containing
this component are opened in either
V7.2.1 or V7.3.
Note: This defect has been corrected
in the V7.3.1 release of EE.
Projects created in EE V7.1 and earlier will
see a ? in the flowrate field when these
projects are opened in EE V7.2.1 or V7.3. In
this case when a project evaluation is run, a
warning message will be generated indicating
a ? is present in the input.
CQ - 425863
The current systems V7.2, V7.2.1, and V7.3
will allow projects to be merged onto
themselves. When this is run, data in the
iccache may be replaced by the data in the
project selected to merge from (due to the
fact both projects have the same name).
Thus, it is not recommended this action be
performed as there may be more recent
entries or specifications in the Target project
that will get overwritten when selecting the
“old” project of the same name to merge
from.
Projects selected to be merged from
should be closed before the Merge
process is initiated.
Note: This issue has been corrected in
the EE V7.3.1 release. Refer to the
What’s New Section of the V7.3.1 EE
Release Notes for further information.
In addition, since multiple EE processes are
now supported in V7.3, users can merge or
import data from a project already open in a
different instance. This is not recommended
and may lead to data base errors and lose of
data in the projects that are selected to
merge from
Economic Evaluation
29
General Usability Issues
Workaround/Comment
CQ429417
This workflow cannot be supported. If
a mechanism is imposed to lock out
the source project (e.g. to prevent
opening in another instance), then it
will not be possible for the drag/drop
to work. If it is required to open the
source project in another instance, the
target project (from which the source
project was initially opened) will have
to be closed. This will enable the
source project to be opened in the
same or new instance.
If a ‘target’ project is opened and another
project is opened to be used as a ‘source’
project via drag/drop methods, opening of
this ‘source’ project in another instance will
not be supported. In order to open the ‘source
project’ in another instance, the original
target project should be closed.
CQ404999
Source media may be required when
Resiliency is triggered.
The software will trigger Resiliency to
configure the application for a new or
Restricted user on a machine. This will occur
the first time any EE application is launched
(by the user) and will not occur again once it
has successfully completed. Thus, in order for
the system to behave as designed, it is
important to let the Resiliency process
complete. Under normal situations, Resiliency
can be completed without requiring the
Source Media from which the application was
installed from. However, there have been
complications where a request is made during
the Resiliency Process for the source media.
During testing, we have determined potential
cause for the source media requirement. If
another user on the same machine ran MS
Excel from within the EE system, even if the
Excel spreadsheet is merely opened and
closed without saving, some file attributes
change in Excel that cause the installer to
think the installation has changed (the
attributes that are changed are invisible to
the user). Once this happens, the source
media requirement is made by the installer.
If the source media is available, the
user should make it available during
this process. This media can be the
download location, network drive, or
DVD (when available).
If the source media is not available,
the original user that ran MS Excel
from the EE application will need to
run the same test (under the original
account).
If the Reporter was run, the user
should open the corresponding
template xls file in Excel and save the
file (w/o any changes). This will
change the time stamp on the file and
the installer will ignore it when the
Resiliency process is run. The Excel
template files are located in:
\Documents and Settings\All
Users\Documents\AspenTech\Shared
Economic Evaluation
V7.3\Reporter\Templates
The root cause of this issue is a Microsoft
Excel 2003 design issue (it does not happen
with Word 2003 or Excel 2007) and cannot be
fully address within the application or
installer. As a reference, the following MS KB
link describes the Excel behavior.
http://support.microsoft.com/kb/840169
30
Economic Evaluation
General Usability Issues
Workaround/Comment
CQ426039
An emergency patch has been issued
for EE V7.3 to correct this issue.
Please refer to Solution ID# 130686
on the Aspen Technology Support Site
and follow the instructions on
installing this EP. Once installed,
metric projects used or created in
either ACCE or AICE V7.3 will not see
a crash when the application is closed.
Users having metric projects with custom pipe
specs files attached will see a crash when the
application (either ACCE or AICE) is closed. It
is a nuisance crash that does not affect
project or application performance as the
project/application can be used in the
customary manner (that is, evaluated/saved
in the normal way). The crash does not
happen when IP projects containing custom
pipe specs are used. The issue does not
pertain to APEA as this product does not
permit custom pipe specs from being used.
CQ00420283
When scheduling data is transferred to
Primavera, a new calendar is created along
with the project. The name of the Calendar
starts with the project name. If while loading
the calendars a corrupted calendar object is
encountered, the Primavera Integration API
will generate an error. This generally
happens when the Primavera database has a
corrupted calendar. When this error is
generated, AICE stops transferring scheduling
data to P6. In EEV7.3.1 this behavior has
been changed and it will now skip loading the
calendars from the Primavera database if it
encounters any problem during loading the
calendars. The application will make use of
the default Primavera calendar in such error
conditions and data transfer to P6 will not be
stopped. However, it will ignore “Number of
Days/Week” and “First Day of the Week” field
specified under Schedule settings Specs and
following message will be displayed:
Note: This issue has been corrected in
the V7.3.1 EE release.
To correct this issue:
1. User needs to adjust default
Primavera Calendar to make
the schedule consistent with
the IPM Schedule Settings
Specs.
2. Install a new database to
permanently fix the issue.
The Primavera project will use “Number of
Days/Week” and “First Day of the Week”
defined in the default Primavera calendar.
In order to support HYSYS Stream Pricing
within APEA V7.3.1 (see What’s New
documentation), APEA V7.3.1 will no longer
support earlier versions of HYSYS (V7.2 and
earlier).
Economic Evaluation
HYSYS users will be required to use
HYSYS V7.3 to integrate with APEA
V7.3.1.
31
Aspen Process Economic
Analyzer V7.3 (formerly Aspen
Icarus Process Evaluation)
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Aspen In-Plant Cost Estimator
V7.3 (formerly Aspen Icarus
Project Manager)
32
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
Economic Evaluation
General Usability Issues
Workaround/Comment
CQ00420283
To correct this issue:
Headline: Scheduling data transfer from
AICE to P6 fails if it encounters a
corrupted calendar object in Primavera
database while loading the Primavera
calendars.
1. User needs to adjust default
Primavera Calendar to make the
schedule consistent with the IPM
Schedule Settings Specs.
When scheduling data is transferred to
Primavera, a new calendar is created
along with the project. The name of the
Calendar starts with the project name. If
while loading the calendars a corrupted
calendar object is encountered, the
Primavera Integration API will generate
an error. This generally happens when
the Primavera database has a corrupted
calendar. When this error is generated,
AICE stops transferring scheduling data
to P6. In EEV7.3.1 this behavior has
been changed and it will now skip
loading the calendars from the Primavera
database if it encounters any problem
during loading the calendars. The
application will make use of the default
Primavera calendar in such error
conditions and data transfer to P6 will
not be stopped. However, it will ignore
“Number of Days/Week” and “First Day
of the Week” field specified under
Schedule settings Specs and following
message will be displayed:
2. Install a new database to
permanently fix the issue.
The Primavera project will use “Number
of Days/Week” and “First Day of the
Week” defined in the default Primavera
calendar.
Economic Evaluation
33
Aspen Capital Cost Estimator
V7.3 (formerly Aspen KBase)
Coexistence Issues
Workaround/Comment
Users running Microsoft Windows with
Windows Installer 3.1 may experience
coexistence issues with Economic
Evaluation V7.2 and previous versions as
described below:
1. Update Windows Installer to version
4.5, which can be downloaded from
the following site.
1. The following aspenONE
applications are installed on a
machine:

EEV7.2.1 (or EEV7.2),
EEV7.3

HYSYS and/or Aspen Plus
V7.2+EPs
2. Invoking the Export to EE feature
in either HYSYS or Aspen Plus
invokes EEV7.2.1 (or EEV7.2)
instead of EEV7.3. This may
occur if none of the EE installed
software versions are run after
installation. This is due to the
windows installer resiliency
behavior. Once the problem
occurs in one user environment,
it is observed with all other users
on that machine.
http://www.microsoft.com/downlo
ads/details.aspx?FamilyID=5a58b5
6f-60b6-4412-95b954d056d6f9f4&displaylang=en
Note: See the installation guide on
how to check which version of
Windows Installer is present on your
system.
2. Ensure EE V7.2.1 (or EEV7.2)/V7.3 is
executed as standalone application
before invoking EE via HYSYS V7.2 (or
Aspen Plus V7.2).
3. In cases where the problem occurs, an
upgrade/repair installation of EE V7.3
can be performed by running the EE
V7.3 installation again. The procedure
allows the EE V7.3 to be reset as the
default costing feature w/ HYSYS
/Aspen Plus V7.2.
Comment: Following the steps below
on the system where EE V7.3 is
installed alongside previous versions of
EE can avoid the aforementioned
issues.
1. Update the Windows Installer
to version 4.5
2. Launch EE V7.2.1 (or EEV7.2) and
allow the EE V7.2.1 Windows
Installer resiliency to go through, if
this the first time EE V7.2.1 is
being launched under this user
account.
3. After closing EE V7.2.1, Launch EE
V7.3 and allow the EE V7.3
Windows Installer resiliency to go
through, if this the first time EE
V7.3 is being launched under this
user account.
34
Economic Evaluation
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
CQ00420283
It doesn’t affect ACCE users, the only
difference is that the scheduling project
will use the default Primavera calendar.
When scheduling data is transferred to
Primavera a new calendar is created
along with the project. The name of the
Calendar starts with the project name.
If while loading the calendars a
corrupted calendar object is
encountered, the Primavera Integration
API will generate an error. This generally
happens when the Primavera database
has a corrupted calendar. When this
error is generated, ACCE stops
transferring scheduling data to P6. In
EEV7.3.1 this behavior has been
changed and it will now skip loading the
calendars from the Primavera database if
it encounters any problem during loading
the calendars. The application will make
use of the default Primavera calendar in
such error conditions and data transfer
to P6 will not be stopped. The following
message will be generated if these
conditions exist:
Economic Evaluation
To correct this issue, Install a new
database to avoid above message box and
permanently fix the issue.
35
Icarus Evaluation Engine V7.3
36
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Economic Evaluation
Energy and Flare Analysis
Aspen Energy Analyzer V7.3
(formerly Aspen HX-Net)
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Energy and Flare Analysis
37
Aspen Flare System Analyzer
V7.3 (formerly Aspen
FLARENET)
38
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
Automation Support: Only .fnwxml and
.fnw cases can be loaded into Aspen
Flare System Analyzer thru OLE
automation interfaces.
The cases in .fnwx format as well as
new cases need to be saved in .fnwxml
format first.
Automation Support: Failure to run Flare
System Analyzer cases in rating/
design/ or debottlenecking mode from
the automation interface directly.
Following dlls : Fnacalc32.dll,
MslBasiclib.dll, MathSolver.dll need to be
copied to the path of the executable. For
example, if the you are trying to run a
case from a Microsoft excel macro, the
above mentioned dlls need to be copied
to the location where excel is installed,
for example: \Microsoft
Office\Office12\EXCEL.EXE
Information in the estimate page of the
scenario editor is not saved to the
.fnwxml file and also cannot be
exported to .xml/.mdb/.xls files. This
field also does not dirty case or scenario
when modified.
Make sure that these fields are initialized
correctly after importing a Flarenet case
previously saved as xml, access or as an
excel file.
All process data is saved in metric units
when a Flare System Analyzer case is
exported to .xml/.mdb/.xls files
None.
Aspen Flare System Analyzer fails to
import the composition while importing
sources from text files.
None.
Energy and Flare Analysis
Estimation of Tc and Pc of a hypo
component can be wrong after saving
and reloading a case.
If possible when creating a new case you
can generate the hypo components
before closing the case. If this is not
applicable you can save the case to xml
and reload it. After this the estimated Tc
and Pc of newly created hypo
components will be correct again.
PFD Printing: The All Tail option for the
PFD is not printing correctly (although
the preview is correctly generated).
No workaround.
Aspen HYSYS Thermodynamics
COM Interface V7.3 (formerly
Aspen COMThermo)
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Energy and Flare Analysis
39
40
Energy and Flare Analysis
Aspen Simulation Workbook
Aspen Simulation Workbook
V7.3
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Aspen Simulation Workbook
41
42
Aspen Simulation Workbook
Process Development
Aspen Batch Process Developer
V7.3 (formerly Aspen Batch
Plus)
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
If you are working on the English XP
operating system, you cannot enter
Chinese characters into the Rename
dialog box when an Operations dialog
box is also open. The Chinese character
preview box freezes.
Access the Rename dialog box through
a different data form, for example Data
| Pure Components | Rename.
If your language is set to a Language
other than English, you might see errors
when trying to produce the Message
Summary Excel Report or when
exporting data to a custom Excel
Report.
The language of Excel must match the
language setting in Windows. For Excel
2003, this means that a language
specific version of Excel needs to be
installed. For Excel 2007 and Excel 2010,
the Excel Language Pack must be
installed.
Vapor Pressure calculations beyond the
temperature bounds of the Antoine
equation have a new calculation
procedure. This might change results for
air emissions and mixture bubble point
temperatures.
The new procedure matches the Aspen
Properties procedure to extrapolate ln p
versus 1/T when outside the temperature
bounds of the Antoine equation.
Process Development
Note: This workaround does not work for
renaming streams. To rename streams,
delete the stream and re-enter it as a
new stream.
43
The Recipe Document report may show
reaction coefficients before and after the
molecular structure image in the
reaction.
Delete the extra reaction coefficients that
appear after the image.
Aspen Solubility Modeler V7.3
44
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Process Development
Advanced Modeling Options
(Process Development)
Aspen Batch Distillation V7.3
(formerly Aspen BatchSep)
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Advanced Modeling Options (Process Development)
45
Aspen Chromatography V7.3
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Aspen Process Tools V7.3
46
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
FDFit incorrectly performs a unit
conversion operation on the Volume
Steady value.
A possible work around is to use a
Volume Steady value of 0 (zero).
FDFit fails to perform a unit conversion
correction on the user entered filtration
pressure in scale-up calculations using
multiple test data.
Enter the filtration pressure value with
units of Pa (i.e. 1000x that indicated in
UI, which requests the pressure in kPa).
Advanced Modeling Options (Process Development)
Aspen Process Manual V7.3
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Advanced Modeling Options (Process Development)
47
48
Advanced Modeling Options (Process Development)
Aspen Basic Engineering
Aspen Basic Engineering V7.3
(formerly Aspen Zyqad)
Coexistence Issues
Workaround/Comment
ABE Version V7.3 cannot exchange data
with HYSYS Version V7.2 or lower. It
also cannot exchange data with ACCE
Version V7.2 or lower.
ABE Version V7.3 will exchange data with
HYSYS V7.3 and ACCE V7.3.
Installation Issues
Workaround/Comment
When upgrading existing V7.1 or V7.2 to
V7.3, the upgrade installation
unregisters the (VB6) knowledgebase
rules (KBs) from versions V7.1 and V7.2
replacing them with a new set of (.NET)
KBs referenced in the new config files
(StandardLibrarySet.cfg and
TEFLibrarySet.cfg). If you have
customized the VB6 KBs and wish to use
them in V7.3 they will have to be reregistered.
The VB6 KBs can be manually registered
from the command line, e.g.:
Regsvr32 Filters162.dl
Repeat this command for each of the
*162.dll files
Alternatively you could download a bat file
from the Customer Support website
knowledge base solution:
http://support.aspentech.com/webteamcgi
/SolutionDisplay_view.cgi?key= 131212
This file can be copied to the folder
containing the VB6 KBs and invoked to reregister all the VB6 KB DLLs.
You are allowed to use a combination of
the old VB6 and new .NET KBs in a
workspace library, but you cannot
implement the same module more than
once. The .NET KBs should not be
registered, they need to be placed in the
folder referenced by the config file e.g.
ManagedKBsDirectory= "KBS". See the
Administration help (zyadminapp.chm) in
the section:
Managing Workspaces | Migrating
Workspaces to V7.1 and Later | Migrating
Aspen Basic Engineering
49
Workspaces to V7.1 and Later. If you are
referencing the managed KBs in your
config file, be sure to remove these
modules from the DataServiceModules
keyword.
50
General Usability Issues
Workaround/Comment
Excel Datasheet Editor:
enumerations: The drop-down lists on
Excel datasheets, which display
available choices for enumeration fields
including units of measurement, have a
maximum of 255 characters.
This is a Microsoft Excel limitation.
Excel Datasheet Editor: Not all fields
can be edited after object claimed
from Excel: You can edit the value
fields on the current page, but other
field types and other pages cannot be
edited.
Close and reopen the datasheet to make
all fields editable.
Excel Datasheet Editor: Sub object
data is not editable if the main
object is not claimed: For example, in
a project if the motor is claimed but the
pump is not, you cannot edit data for
the motor.
Claim the parent object
Excel Datasheet Editor: Filter
Continuous List: There are blank lines
added to the end of the list.
Close and reopen the datasheet – the
blank lines will be removed.
Aspen Basic Engineering
Operations Support
Aspen Online Deployment V7.3
Coexistence Issues
Workaround/Comment
Simulator support.
Aspen Online Deployment V7.3 supports
versions V7.1, V7.2, and V7.3 of Aspen
Plus, Aspen HYSYS, Aspen Custom
Modeler, Aspen Model Runner, and
Exchanger Design and Rating.
Earlier versions are not supported.
Simulator version specification.
A specific simulator version cannot be
specified for Exchanger Design and
Rating (EDR) cases; the default version
of EDR is used.
A specific version can be specified for
Aspen Plus, Aspen HYSYS, Aspen Model
Runner and Aspen Custom Modeler.
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Operations Support
51
Aspen OTS Framework V7.3
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Aspen Online V7.3
52
Coexistence Issues
Workaround/Comment
Aspen Online V7.3 can coexist with
earlier version of Aspen Online.
Aspen Online V7.3 requires Aspen Plus
V7.3.
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
SQL error dialog when using Chinese
OS.
Acknowledge error and continue. This
error message does not stop the normal
functioning of the user interface.
Operations Support
Aspen Plus Based Refinery
Reactors
Aspen Plus Catcracker V7.3
(formerly Aspen FCC)
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Aspen Plus Based Refinery Reactors
53
Aspen Plus Hydrocracker V7.3
(formerly Aspen Hydrocracker)
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Aspen Plus Hydrotreater V7.3
(formerly Aspen Hydrotreater)
54
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Aspen Plus Based Refinery Reactors
Aspen Plus Reformer V7.3
(formerly Aspen CatRef)
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Aspen Plus Based Refinery Reactors
55
56
Aspen Plus Based Refinery Reactors
Aspen Open Object Model
Framework
Aspen Open Object Model
Framework
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
Aspen Open Object Model Framework
57
58
Aspen Open Object Model Framework
PE/PD Console
PE/PD Console
PE/PD Console
Coexistence Issues
Workaround/Comment
No known issues
Not applicable
Installation Issues
Workaround/Comment
No known issues
Not applicable
General Usability Issues
Workaround/Comment
No known issues
Not applicable
59
60
PE/PD Console