Aspen Engineering Suite

Known Issues in
AES 2006.5
Version Number: 2006.5
October 2007
Copyright (c) 2007 by Aspen Technology, Inc. All rights reserved.

Aspen ACOL™, Aspen Adsim®, Aspen Advisor™, Aspen Aerotran®, Aspen Alarm & Event™, Aspen APLE™, Aspen
Apollo Desktop™, Aspen Apollo Online™, Aspen AssetBuilder™, Aspen ATOMS™, Aspen Automated Stock
Replenishment™, Aspen Batch Plus®, Aspen Batch.21™, Aspen BatchCAD™, Aspen BatchSep™, Aspen Calc™,
Aspen Capable-to-Promise®, Aspen CatRef®, Aspen Chromatography®, Aspen Cim-IO for ACS™, Aspen Cim-IO
for Csi VXL™, Aspen Cim-IO for Dow MIF™, Aspen Cim-IO for G2™, Aspen Cim-IO for GSE D/3™, Aspen Cim-IO for
Hewlett-Packard RTAP™, Aspen Cim-IO for Hitachi PLC (H04E)™, Aspen Cim-IO for Intellution Fix™, Aspen Cim-IO
for Melsec™, Aspen Cim-IO for WonderWare InTouch™, Aspen Cim-IO for Yokogawa Centum CS™, Aspen Cim-IO
for Yokogawa Centum XL™, Aspen Cim-IO for Yokogawa EW3™, Aspen Cim-IO Interfaces™, Aspen Cim-IO
Monitor™, Aspen Cim-IO™, Aspen Collaborative Demand Management™, Aspen Collaborative Forecasting™, Aspen
Compliance.21™, Aspen Cost Factor Manual™, Aspen Crude Manager™, Aspen Crude Margin Evaluation™, Aspen
Custom Modeler®, Aspen Data Source Architecture™, Aspen Decision Analyzer™, Aspen Demand Manager™,
Aspen Distribution Scheduler™, Aspen DMCplus® Composite, Aspen DMCplus® Desktop, Aspen DMCplus® Online,
Aspen DPO™, Aspen Dynamics®, Aspen eBRS™, Aspen Enterprise Model™, Aspen ERP Connect™, Aspen FCC®,
Aspen FIHR™, Aspen FLARENET™, Aspen Fleet Operations Management™, Aspen Framework™, Aspen FRAN™,
Aspen Fuel Gas Optimizer Desktop™, Aspen Fuel Gas Optimizer Online™, Aspen General Construction Standards™,
Aspen Hetran®, Aspen HX-Net®, Aspen Hydrocracker®, Aspen Hydrotreater™, Aspen HYSYS Amines™, Aspen
HYSYS Crude™, Aspen HYSYS Dynamics™, Aspen HYSYS OLGAS 3-Phase™, Aspen HYSYS OLGAS™, Aspen HYSYS
OLI Interface™, Aspen HYSYS Tacite™, Aspen HYSYS Upstream Dynamics™, Aspen HYSYS Upstream™, Aspen
HYSYS®, Aspen Icarus Process Evaluator®, Aspen Icarus Project Manager®, Aspen InfoPlus.21®, Aspen Inventory
Balancing™, Aspen IQ Desktop™, Aspen IQ Online™, Aspen IQmodel Powertools™, Aspen Kbase®, Aspen LIMS
Interface™, Aspen Local Security™, Aspen LPIMS™, Aspen MBO™, Aspen MIMI®, Aspen MPIMS™, Aspen
Multivariate Server™, Aspen MUSE™, Aspen NPIMS™, Aspen OnLine®, Aspen Operations Manager - Event
Management™, Aspen Operations Manager - Integration Infrastructure™, Aspen Operations Manager -
Performance Scorecarding™, Aspen Operations Manager - Role Based Visualization™, Aspen Order Credit
Management™, Aspen Orion Planning™, Aspen Orion™, Aspen PIMS Blend Model Library™, Aspen PIMS Distributed
Processing™, Aspen PIMS Enterprise Edition™, Aspen PIMS Mixed Integer Programming™, Aspen PIMS Simulator
Interface™, Aspen PIMS Solution Ranging™, Aspen PIMS Submodel Calculator™, Aspen PIMS XNLP Optimizer™,
Aspen PIMS™, Aspen PIPE™, Aspen Planning Accuracy™, Aspen Plant Planner & Scheduler™, Aspen Plant
Scheduler Lite™, Aspen Plant Scheduler™, Aspen Plus OLI Interface™, Aspen Plus®, Aspen Polymers Plus®, Aspen
PPIMS™, Aspen Process Data™, Aspen Process Explorer™, Aspen Process Manual™, Aspen Process Order™, Aspen
Process Plant Construction Standards™, Aspen Process Recipe®, Aspen Process Tools™, Aspen Product Margin &
Blending Evaluation™, Aspen Production Control Web Server™, Aspen ProFES® 2P Tran, Aspen ProFES® 2P Wax,
Aspen ProFES® 3P Tran, Aspen ProFES® Tranflo, Aspen Properties®, Aspen Pumper Log™, Aspen Q Server™,
Aspen RateSep™, Aspen RefSYS CatCracker™, Aspen RefSYS Spiral™, Aspen RefSYS™, Aspen Report Writer™,
Aspen Resource Scheduling Optimization™, Aspen RTO Watch Cim-IO Server™, Aspen RTO Watch Server™, Aspen
Scheduling & Inventory Management™, Aspen SmartStep Desktop™, Aspen SmartStep Online™, Aspen SQLplus™,
Aspen Supply Chain Analytics™, Aspen Supply Chain Connect™, Aspen Supply Planner™, Aspen Tank
Management™, Aspen TASC-Mechanical™, Aspen TASC™, Aspen Teams®, Aspen Terminals Management™, Aspen
TICP™, Aspen Transition Manager™, Aspen Turbo PIMS™, Aspen Utilities™, Aspen Voice Fulfillment Management™,
Aspen Watch Desktop™, Aspen Watch Server™, Aspen Web Fulfillment Management™, Aspen WinRace Database™,
Aspen XPIMS™, Aspen Zyqad Development Version™, 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 document is intended as a guide to using AspenTech's software. 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-4300
Toll Free: (1) (888) 996-7100
URL: http://www.aspentech.com
Contents

Contents..................................................................................................................1

Introduction ............................................................................................................4

Aspen ACOL.............................................................................................................5

Aspen Acol+ ............................................................................................................6

Aspen Adsim ...........................................................................................................7

Aspen Aerotran .......................................................................................................9

Aspen APLE ...........................................................................................................10

Aspen Batch Plus...................................................................................................11

Aspen BatchSep ....................................................................................................12

Aspen Case Analysis..............................................................................................13

Aspen CatRef.........................................................................................................14

Aspen COMThermo Workbench .............................................................................15

Aspen Chromatography .........................................................................................16

Aspen Custom Modeler ..........................................................................................18

Aspen Dynamics ....................................................................................................20

Aspen FCC .............................................................................................................22

Contents 1
Aspen FIHR ...........................................................................................................23

Aspen FiredHeater.................................................................................................24

Aspen FLARENET ...................................................................................................25

Aspen FRAN...........................................................................................................26

Aspen Hetran ........................................................................................................27

Aspen HTFS ...........................................................................................................28

Aspen HTFS+.........................................................................................................29

Aspen HTFS+ Research Network ...........................................................................30

Aspen Hydrocracker ..............................................................................................31

Aspen Hydrotreater...............................................................................................32

Aspen HYSYS.........................................................................................................33

Aspen HYSYS Upstream.........................................................................................34

Aspen HX-Net........................................................................................................35

Aspen Icarus Evaluation Technology .....................................................................36

Aspen Icarus Process Evaluator ............................................................................37

Aspen Icarus Project Manager ..............................................................................40

Aspen Kbase..........................................................................................................42

Aspen Model Runner .............................................................................................45

Aspen MUSE ..........................................................................................................46

Aspen OLI Interface ..............................................................................................47

Aspen OnLine ........................................................................................................48

Aspen Online Deployment .....................................................................................49

2 Contents
Aspen Open Object Model Framework (OOMF)......................................................51

Aspen PIPE............................................................................................................52

Aspen Plus ............................................................................................................53

Aspen Plate+.........................................................................................................55

Aspen Process Tools..............................................................................................56

Aspen Properties...................................................................................................57

Aspen Polymers Plus .............................................................................................60

Aspen Process Manual...........................................................................................61

Aspen RefSYS........................................................................................................62

Aspen Remote Simulation Service .........................................................................64

Aspen Simulation Workbook .................................................................................65

Aspen TASC ...........................................................................................................67

Aspen Tasc+..........................................................................................................68

Aspen Teams .........................................................................................................69

Aspen Zyqad..........................................................................................................70

Contents 3
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 (interface issues that will be addressed in future
releases/hot fixes).
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.

4 Introduction
Aspen ACOL

Coexistence Issues Workaround/Comment

No known issues Not applicable

Installation Issues Workaround/Comment

Microsoft Vista Users If users want to run the example input

files supplied with the product, and they
have a restricted user account (which is
usually the case for Vista but can also be
true for Windows XP), they need to copy
the example files from their installed
location to a folder to which they have
write access. When running the sample
programs, they should select the files
from this location.
In addition, users with Restricted User
status might need to have someone with
administrator privileges set their
Component and Stream databank
locations to a folder to which the user
has write access. This can be done by
using File Preferences and setting the
desired location for the CBANK| files.
This can be done immediately after the
installation.

General Usability Issues Workaround/Comment

No known issues Not applicable

Aspen ACOL 5
Aspen Acol+

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

6 Aspen Acol+
Aspen Adsim

Coexistence Issues Workaround/Comment

After installing version 2006.5, Open a command prompt in the folder

attempting to run simulations in version \Program Files\AspenTech\Aspen Open
2004.1 results in the error message Solvers 12.3\bin
“Initialization failed at time 0” Run the command:
Regsvr32 decompserver.dll
ACM 2004.1 simulations should now run
OK.
After uninstalling version 2006, Open a command prompt in the folder
attempting to run simulations in version \Program Files\AspenTech\Aspen Open
2006.5 may result in the error message Solvers 2006.5\bin
“Initialization failed at time 0” Run the command:
Regsvr32 decompserver.dll
ACM 2006.5 simulations should now run
OK.
After uninstalling version 2006.5 the Go to Start Menu, All Programs,
following two issues may occur in a AspenTech, Aspen Engineering Suite,
2006 installation having Aspen Aspen Properties 2006, Aspen Properties
Properties 2006 correctly installed: Registry Fix Utility. Select Aspen
• Attempting to load simulations in Properties 20.0 and click OK button, then
version 2006 that contain embedded click Yes when asked if you wish to
Aspen Properties files may result in continue.
the error message “Unable to
generate aprpdf file using saved
Aspen Properties input file”.
• Attempting to “Edit using Aspen
Properties” when setting up or
reviewing a Component List with
Properties in version 2006 may result
in the error message “Failed to launch
Aspen Properties, it might not be
installed correctly, or there could be a
licensing problem”

Aspen Adsim 7
 Installation Issues Workaround/Comment

No known issues Not applicable

General Usability Issues Workaround/Comment

The new Global Data feature for viewing None

stream values on the flowsheet does not
work correctly when used within
hierarchy blocks

8 Aspen Adsim
Aspen Aerotran

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 Aerotran 9
Aspen APLE

Coexistence Issues Workaround/Comment

No known issues Not applicable

Installation Issues Workaround/Comment

Microsoft Vista Users If users wishes to run the example input

files supplied with the product, and they
have a restricted user account (which will
more than likely be the case for Vista but
can also occur with Windows XP), they
need to copy the example files from their
installed location to a folder to which
they have write access. When running
the sample programs, they should select
the files from this location.
In addition, users with Restricted User
status might need to have someone with
administrator privileges set their
Component and Stream databank
locations to some folder to which the
user has write access. This can be done
by using the File Preferences and setting
the desired location for the CBANK| files.
This can be done immediately after the
installation.

General Usability Issues Workaround/Comment

No known issues Not applicable

10 Aspen APLE
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

No known issues Not applicable

Aspen Batch Plus 11

Aspen BatchSep

Coexistence Issues Workaround/Comment

After installing version 2006.5, Open a command prompt in the folder

attempting to run simulations in version \Program Files\AspenTech\Aspen Open
2004.1 results in the error message Solvers 12.3\bin
“Initialization failed at time 0” Run the command:
Regsvr32 decompserver.dll
ACM 2004.1 simulations should now run
OK.
After uninstalling version 2006, Open a command prompt in the folder
attempting to run simulations in version \Program Files\AspenTech\Aspen Open
2006.5 may result in the error message Solvers 2006.5\bin
“Initialization failed at time 0” Run the command:
Regsvr32 decompserver.dll
ACM 2006.5 simulations should now run
OK.
After uninstalling version 2006.5 the Go to Start Menu, All Programs,
following two issues may occur in a AspenTech, Aspen Engineering Suite,
2006 installation having Aspen Aspen Properties 2006, Aspen Properties
Properties 2006 correctly installed: Registry Fix Utility. Select Aspen
• Attempting to load simulations in Properties 20.0 and click OK button, then
version 2006 that contain embedded click Yes when asked if you wish to
Aspen Properties files may result in continue.
the error message “Unable to
generate aprpdf file using saved
Aspen Properties input file”.
• Attempting to “Edit using Aspen
Properties” when setting up or
reviewing a Component List with
Properties in version 2006 may result
in the error message “Failed to launch
Aspen Properties, it might not be
installed correctly, or there could be a
licensing problem”

Note: For additional known issues related to running BatchSep within Aspen
Plus, see the Aspen Plus known issues.

12 Aspen BatchSep
Aspen Case Analysis

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 Case Analysis 13

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

14 Aspen CatRef
Aspen COMThermo
Workbench

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 COMThermo Workbench 15

Aspen Chromatography

Coexistence Issues Workaround/Comment

After installing version 2006.5, Open a command prompt in the folder

attempting to run simulations in version \Program Files\AspenTech\Aspen Open
2004.1 results in the error message Solvers 12.3\bin
“Initialization failed at time 0” Run the command:
Regsvr32 decompserver.dll
ACM 2004.1 simulations should now run
OK.
After uninstalling version 2006, Open a command prompt in the folder
attempting to run simulations in version \Program Files\AspenTech\Aspen Open
2006.5 may result in the error message Solvers 2006.5\bin
“Initialization failed at time 0” Run the command:
Regsvr32 decompserver.dll
ACM 2006.5 simulations should now run
OK.
After uninstalling version 2006.5 the Go to Start Menu, All Programs,
following two issues may occur in a AspenTech, Aspen Engineering Suite,
2006 installation having Aspen Aspen Properties 2006, Aspen Properties
Properties 2006 correctly installed: Registry Fix Utility. Select Aspen
• Attempting to load simulations in Properties 20.0 and click OK button, then
version 2006 that contain embedded click Yes when asked if you wish to
Aspen Properties files may result in continue.
the error message “Unable to
generate aprpdf file using saved
Aspen Properties input file”.
• Attempting to “Edit using Aspen
Properties” when setting up or
reviewing a Component List with
Properties in version 2006 may result
in the error message “Failed to launch
Aspen Properties, it might not be
installed correctly, or there could be a
licensing problem”

Installation Issues Workaround/Comment

16 Aspen Chromatography
 No known issues Not applicable

General Usability Issues Workaround/Comment

The Help button does not work on the Open online Help from the Help menu
following forms: and navigate to appropriate entry in
Aspen Chromatography Contents:
• Cycle Organizer form • Chromatographic Processes | Cyclic
• Triangle Theory form Operation
• Streams Configuration form in • Chromatographic Processes |
Chrom_CCC_Separator model Simulated Moving Bed Processes |
Triangle Theory
• Chromatographic Processes |
Simulated Moving Bed Processes |
Streams Configuration form
This issue will be fixed in the next
cumulative patch.
The new Global Data feature for viewing None
stream values on the flowsheet does not
work correctly when used within
hierarchy blocks

Aspen Chromatography 17
Aspen Custom Modeler

Coexistence Issues Workaround/Comment

After installing version 2006.5, Open a command prompt in the folder

attempting to run simulations in version \Program Files\AspenTech\Aspen Open
2004.1 results in the error message Solvers 12.3\bin
“Initialization failed at time 0” Run the command:
Regsvr32 decompserver.dll
ACM 2004.1 simulations should now run
OK.
After uninstalling version 2006, Open a command prompt in the folder
attempting to run simulations in version \Program Files\AspenTech\Aspen Open
2006.5 may result in the error message Solvers 2006.5\bin
“Initialization failed at time 0” Run the command:
Regsvr32 decompserver.dll
ACM 2006.5 simulations should now run
OK.
After uninstalling version 2006.5 the Go to Start Menu, All Programs,
following two issues may occur in a AspenTech, Aspen Engineering Suite,
2006 installation having Aspen Aspen Properties 2006, Aspen Properties
Properties 2006 correctly installed: Registry Fix Utility. Select Aspen
• Attempting to load simulations in Properties 20.0 and click OK button, then
version 2006 that contain embedded click Yes when asked if you wish to
Aspen Properties files may result in continue.
the error message “Unable to
generate aprpdf file using saved
Aspen Properties input file”.
• Attempting to “Edit using Aspen
Properties” when setting up or
reviewing a Component List with
Properties in version 2006 may result
in the error message “Failed to launch
Aspen Properties, it might not be
installed correctly, or there could be a
licensing problem”

Installation Issues Workaround/Comment

No known issues Not applicable

18 Aspen Custom Modeler

 General Usability Issues Workaround/Comment

If you export a file in Aspen Model Always save your file as a .acmf file
Runner (.amrf) format, the file may not before exporting is as a .amrf file
be exported correctly if you have not
first saved the input file to a .acmf file.

The new Global Data feature for viewing None

stream values on the flowsheet does not
work correctly when used within
hierarchy blocks
If you double click on a file saved as an Open .acmd files using the Open
Aspen Custom Modeler Document command on the file menu, or by
(.acmd file), Aspen Custom Modeler will dragging and dropping them onto the
crash on startup. Aspen Custom Modeler window.

Aspen Custom Modeler 19

Aspen Dynamics

Coexistence Issues Workaround/Comment

After installing version 2006.5, Open a command prompt in the folder

attempting to run simulations in version \Program Files\AspenTech\Aspen Open
2004.1 results in the error message Solvers 12.3\bin
“Initialization failed at time 0”. Run the command:
Regsvr32 decompserver.dll
ACM 2004.1 simulations should now run
OK.
After uninstalling version 2006, Open a command prompt in the folder
attempting to run simulations in version \Program Files\AspenTech\Aspen Open
2006.5 may result in the error message Solvers 2006.5\bin
“Initialization failed at time 0” Run the command:
Regsvr32 decompserver.dll
ACM 2006.5 simulations should now run
OK.

Installation Issues Workaround/Comment

No known issues Not applicable

General Usability Issues Workaround/Comment

Sep, Sep2, RYield and Rstoic blocks give Use a mixer block when multiple feeds
incorrect results for true component are required.
electrolyte support if there are multiple
inlet streams.
RGibbs is not supported for true None
component electrolytes.
If ValidPhases is specified as “Vapor- Change Valid Phases to “Vapor-only” for
Liquid” but results are vapor only in a this block.
block where chemistry is defined using
true components, a fatal error may occur
on export, or the simulation may fail to
converge in dynamics.

20 Aspen Dynamics
 General Usability Issues Workaround/Comment

Compr model may not converge for true Turn off chemistry in Compr.
component electrolyte simulation.
MCompr model does not work for true Turn off chemistry in MCompr.
component electrolyte simulation.
RPlug and Pipe currently have None
convergence difficulties with true
component electrolytes.
Pressure relief models do not work for
true component electrolyte simulation.
Reverse Flow is not supported for true None
component electrolyte simulations.
Empty scripts are not available for true None
component electrolyte simulations.
True component electrolytes: Missing Provide missing parameters for the solid
parameters reported for solid components.
components. This occurs because
properties system is attempting to
compute liquid and vapor phase
fugacitities for all components including
solid components
True component electrolytes: For MHeatX Run simulation until it lines out and run in
with multiple zones, the initial condition steady state mode.
may not be at steady state resulting in a
temperature transient until the process
lines out
True component electrolytes: Feed Reconcile the feed stream changing the
streams on a mass flow basis give basis to mole fraction and total mole
incorrect mole flow. flow.

Aspen Dynamics 21
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

22 Aspen FCC
Aspen FIHR

Coexistence Issues Workaround/Comment

No known issues Not applicable

Installation Issues Workaround/Comment

Microsoft Vista Users If users wishes to run the example input

files supplied with the product, and they
have a restricted user account (which will
more than likely be the case for Vista but
can also occur with Windows XP), they
need to copy the example files from their
installed location to a folder to which
they have write access. When running
the sample programs, they should select
the files from this location.
In addition, users with Restricted User
status might need to have someone with
administrator privileges set their
Component and Stream databank
locations to some folder to which the
user has write access. This can be done
by using the File Preferences and setting
the desired location for the CBANK| files.
This can be done immediately after the
installation.

General Usability Issues Workaround/Comment

No known issues Not applicable

Aspen FIHR 23
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

24 Aspen FiredHeater
Aspen FLARENET

Coexistence Issues Workaround/Comment

No known issues Not applicable

Installation Issues Workaround/Comment

No known issues Not applicable

General Usability Issues Workaround/Comment

Previous versions of Flarenet abort the In version 2006, this check has been
calculations if the analysis of the disabled to allow an attempted solution
network topography discovers a for such configurations. The solution
separator unit operation within the body algorithm itself is unchanged and is not
of a looped circuit. (This configuration is expected to be applicable to all possible
indicated by a separator whose fluid scenarios where a looped system is
flow direction is unknown until after modelled. Particularly, you may
calculations are complete.) encounter problems if there is a
significant liquid dropout at the
separator.

Aspen FLARENET 25
Aspen FRAN

Coexistence Issues Workaround/Comment

No known issues Not applicable

Installation Issues Workaround/Comment

Microsoft Vista Users If users wishes to run the example input

files supplied with the product, and they
have a restricted user account (which will
more than likely be the case for Vista but
can also occur with Windows XP), they
need to copy the example files from their
installed location to a folder to which
they have write access. When running
the sample programs, they should select
the files from this location.
In addition, users with Restricted User
status might need to have someone with
administrator privileges set their
Component and Stream databank
locations to some folder to which the
user has write access. This can be done
by using the File Preferences and setting
the desired location for the CBANK| files.
This can be done immediately after the
installation.

General Usability Issues Workaround/Comment

No known issues Not applicable

26 Aspen FRAN
Aspen Hetran

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 Hetran 27
Aspen HTFS

Coexistence Issues Workaround/Comment

No known issues Not applicable

Installation Issues Workaround/Comment

Microsoft Vista Users If users wishes to run the example input

files supplied with the product, and they
have a restricted user account (which will
more than likely be the case for Vista but
can also occur with Windows XP), they
need to copy the example files from their
installed location to a folder to which
they have write access. When running
the sample programs, they should select
the files from this location.
In addition, users with Restricted User
status might need to have someone with
administrator privileges set their
Component and Stream databank
locations to some folder to which the
user has write access. This can be done
by using the File Preferences and setting
the desired location for the CBANK| files.
This can be done immediately after the
installation.

General Usability Issues Workaround/Comment

No known issues Not applicable

28 Aspen HTFS
Aspen HTFS+

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+ 29
Aspen HTFS+ Research
Network

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

30 Aspen HTFS+ Research Network

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 Hydrocracker 31
Aspen Hydrotreater

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

32 Aspen Hydrotreater
Aspen HYSYS

Coexistence Issues Workaround/Comment

No known issues Not applicable

Installation Issues Workaround/Comment

No known issues Not applicable

General Usability Issues Workaround/Comment

HYSYS MDC Optimizer crashes in a To run MDC Optimizer within HYSYS in

Microsoft Vista environment because the Vista, you must not only be an
MDC Optimizer writes to the Program administrator, you must also launch
Files location. HYSYS as an administrator. To launch
HYSYS as an administrator, browse to
hysys.exe, right-click hysys.exe, and
select Run as an administrator. When
prompted, enter an admin user id and
the corresponding password.
HYSYS Property Wizard might not Browse to the support folder under the
launch in certain cases. HYSYS installation folder and double-click
the file PropertyMethodAssistant.amf
In some unit operations (columns, for This problem will be addressed in the
example), the Input Summary tab in the next release of HYSYS.
Flowsheet Summary shows a significant
amount of information not specified by
the user, such as HYSYS default values.

Aspen HYSYS 33
Aspen HYSYS Upstream

Coexistence Issues Workaround/Comment

Aspen Hydraulics 2006 does not work If you require both versions to work on
when installed together with Aspen the same machine, contact Aspentech
hydraulics 2006.5. customer support.

Installation Issues Workaround/Comment

No known issues Not applicable

General Usability Issues Workaround/Comment

Using more than one production No workaround.

allocation utility with different source
streams gives wrong results.
Aspen Hydraulics Compositional Solver Use a combination of simple pipes and
does not work for complex pipes. swages to model the complex pipe.
Aspen Hydraulics Compositional Solver No workaround.
fails to run when the inlet stream is only
liquid.

34 Aspen HYSYS Upstream

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

In the new feature that allows the The extension of this new feature to
transfer of a Heat Exchanger Network include process stream splitters will be
from an Excel table fix format to Aspen addressed in successive Aspen HX-Net
HX-Net, networks that contain process 2006.5 patches and in the next release
stream splitters are not transferred. of Aspen HX-Net.

Aspen HX-Net 35
Aspen Icarus Evaluation
Technology

Coexistence Issues Workaround/Comment

No known issues Not applicable

Installation Issues Workaround/Comment

Aspen Icarus 2006.5 does not support Installation will succeed but Aspen Icarus
installation in a Terminal Server products will not function properly.
environment.
When a user other than the user who This is by design and the process should
installed Aspen Icarus 2006.5 first be allowed to complete without hitting
launches an Aspen Icarus product a the Cancel button. The dialog should
dialog appears saying Aspen Icarus only appear the first time an Aspen
2006.5 is configuring itself. Icarus product is launched. This occurs
typically with a Restricted User since the
Restricted User is not the one who
installed Aspen Icarus 2006.5.

General Usability Issues Workaround/Comment

Values not converted when Drag/Drop The values that are in any customized
item From/To project with Custom Units units of measure are not converted and
of Measure specified. the value is set to 0 in the destination
field. Only workaround at this time is to
not use customized unit specs in projects
that the Drag/Drop feature is expected
to be used.
In German Windows XP, when a project Proceed to evaluate a second time and
is opened, and evaluated for the first work with the estimate.
time, it crashes; subsequent evaluations
do no produce a crash

36 Aspen Icarus Evaluation Technology

Aspen Icarus Process
Evaluator

Coexistence Issues Workaround/Comment

No known issues Not applicable

Installation Issues Workaround/Comment

When Aspen Icarus Process Evaluator is Visit

installed on a machine with MS Office http://support.microsoft.com/kb/907417
2003, the patch for Microsoft KB 907417 to download and install the patch
is required before the product can be manually. Any errors that occur during
installed. This patch can fail in some the installation will be visible. The patch
cases when there is a problem with the may request the original Office
Office installation, and when it does so it installation media to restore damaged or
can send the AspenTech installer into an missing files. If the patch still fails,
infinite loop. consult Microsoft support.
Uninstalling Aspen Icarus 2006 causes A possible workaround is to perform a
error message “Failed to Launch IPE” Repair installation on Aspen Icarus
when using the “Send to IPE” feature in 2006.5 after the uninstall of Aspen
HYSYS. Icarus 2006 is completed.

General Usability Issues Workaround/Comment

A “Server Busy” dialog from Windows is Press the Retry button, wait a bit and if
displayed when multiple applications are necessary repeat. If the issue is not
interchanging data. This is most resolved press the “Switch To” button
common on less capable hardware and once and then repeat the first steps.
when many applications are active.
Examples of when this issue is most
likely are when running the Icarus-
Teams interface, running the simulator
import interface or costing within the
simulators for Aspen Plus or Hysys.
Hysys simulations after Version 2.2 with Remove the unit op before loading, since
a Surge Controller unit op will fail to this is a controller block, it is not

Aspen Icarus Process Evaluator 37

 load. necessary for the costing function.

38 Aspen Icarus Process Evaluator

 General Usability Issues Workaround/Comment

Cannot save project after sizing shell The object database engine that is
and tube heat exchanger using HTFS+ launched during Teams sizing does not
Teams. close and prevents the project from
being saved. The user can shutdown the
database engine manually. In the
Windows taskbar the user will see an
application with “CST_RSLT” in the title
bar. Click on this application and click
the “shut down” button. Click “OK” on
the dialog box that appears. This will
shut down the database engine. After
that the project can be saved.
Not all EN/DIN/JIS materials can be All materials in ICARUS have been
imported from Teams to Kbase when mapped to appropriate ASME materials
sizing shell and tube heat exchangers in Teams. This mapping is not complete
using Teams. for EN/DIN/JIS materials. If user chooses
a material from these databanks in
Teams, they may not be properly
imported into ICARUS. The Teams
design, weight and cost information will
be imported irrespective of the material
selection in Teams. However the user
may not see the appropriate material
name in ICARUS since the material may
not be mapped.
LO11011 Error message appears when The issue seems to be intermittent. As a
using the “Send to” feature in HYSYS or workaround, try performing the action
while using the Utility feature in Aspen again. If a similar result occurs please
Icarus products on a Vista machine. contact support with details of the
actions taken that caused the error
message to occur.
Opening or Attaching a Volumetric The values are saved to the file when
Model Library item with specifications initially specified but are being lost when
for Pipe Item Detail line sizing fields re-opened or attached. No workaround
does not show the values in the GUI. exists.

Aspen Icarus Process Evaluator 39

Aspen Icarus Project
Manager

Coexistence Issues Workaround/Comment

No known issues Not applicable

Installation Issues Workaround/Comment

When Aspen Icarus Project Manager is Visit

installed on a machine with MS Office http://support.microsoft.com/kb/907417
2003, the patch for Microsoft KB 907417 to download and install the patch
is required before the product can be manually. Any errors that occur during
installed. This patch can fail in some the installation will be visible. The patch
cases when there is a problem with the may request the original Office
Office installation, and when it does so it installation media to restore damaged or
can send the AspenTech installer into an missing files. If the patch still fails,
infinite loop. consult Microsoft support.
The IPM Scheduling link is not supported Please refer to Primavera support for
on Vista and in accounts with only issues for configuring and running
restricted user permissions Primavera 3.1 on Vista and with
restricted user permissions. Currently it
is our understanding that Primavea does
not support P3 3.1 on Vista. For issues
with installing and running the
scheduling software in accounts with
restricted user permissions please
contact Primavera.

40 Aspen Icarus Project Manager

 General Usability Issues Workaround/Comment

A “Server Busy” dialog from Windows is Press the Retry button, wait a bit, and if
displayed when multiple applications are necessary repeat this step. If the issue is
interchanging data. This is most not resolved press the “Switch To”
common on less capable hardware and button once and then repeat the first
when many applications are active. steps.
Examples of when this issue is most
likely are when running the Icarus-
Teams interface, running the simulator
import interface or costing within the
simulators for Aspen Plus or Hysys.
Cannot save project after sizing shell The object database engine that is
and tube heat exchanger using HTFS+ launched during Teams sizing does not
Teams. close and prevents the project from
being saved. The user can shutdown the
database engine manually. In the
Windows taskbar the user will see an
application with “CST_RSLT” in the title
bar. Click on this application and click the
“shut down” button. Click “OK” on the
dialog box that appears. This will shut
down the database engine. After that the
project can be saved.
Not all EN/DIN/JIS materials can be All materials in ICARUS have been
imported from Teams to Kbase when mapped to appropriate ASME materials
sizing shell and tube heat exchangers in Teams. This mapping is not complete
using Teams. for EN/DIN/JIS materials. If user chooses
a material from these databanks in
Teams, they may not be properly
imported into ICARUS. The Teams
design, weight and cost information will
be imported irrespective of the material
selection in Teams. However the user
may not see the appropriate material
name in ICARUS since the material may
not be mapped.

Aspen Icarus Project Manager 41

Aspen Kbase

Coexistence Issues Workaround/Comment

Custom Model does not work in Aspen Icarus 2006 is not supported in a
Restricted User with Aspen Icarus 2006 Restricted User environment and should
and Aspen Icarus 2006.5 installed. not be installed. Registering the
ICAPICOM.dll (typically in Program
Files/AspenTech/Aspen Icarus
2006.5/Program/Sys) after 2006 is
uninstalled is a possible workaround.
Another possible workaround is to
perform a Repair installation on Aspen
Icarus 2006.5 after 2006 is uninstalled.

Installation Issues Workaround/Comment

When Aspen Kbase is installed on a Visit

machine with MS Office 2003, the patch http://support.microsoft.com/kb/907417
for Microsoft KB 907417 is required to download and install the patch
before the product can be installed. This manually. Any errors that occur during
patch can fail in some cases when there the installation will be visible. The patch
is a problem with the Office installation, may request the original Office
and when it does so it can send the installation media to restore damaged or
AspenTech installer into an infinite loop. missing files. If the patch still fails,
consult Microsoft support.
When a Graphical PID or Volumetric Make sure the permissions on the *.TBL
Model library is shared between user files in the folder allow users wishing to
accounts(Like an installing administrator edit read/write permissions.
and a regular user), the default
permissions on *.TBL files in the
C:\Documents and Settings\All
Users\Documents\AspenTech\Shared
Aspen Icarus 2006.5
Files\PIDs\Drawings and PIDs\VolMods
can prevent a restricted user from
editing the library.

42 Aspen Kbase
 General Usability Issues Workaround/Comment

As a default, when a PID drawing is The user can use the options menu to
opened, in Kbase, the gridlines should show the gridlines and use the view
be turned on and the drawing view 'zoom in' property to display the drawing
properties should be set so drawing better, but these options are not saved
details cover the entire screen. when another drawing is opened.
Currently, in the 2006.5 Icarus builds
when a PID drawing is opened no
gridlines appear and the drawing is
'smaller'. This appearance is different
from previous Icarus releases (2004,
2004.2, and 2006).
A “Server Busy” dialog from Windows is Press the Retry button, wait a bit, and if
displayed when multiple applications are necessary repeat this step. If the issue is
interchanging data. This is most not resolved press the “Switch To”
common on less capable hardware and button once and then repeat the first
when many applications are active. steps.
Examples of when this issue is most
likely are when running the Icarus-
Teams interface, running the simulator
import interface or costing within the
simulators for Aspen Plus or Hysys.
When a value is set with the Icarus API Pass a non-Double or Double value
function ValueWithConversion using a rounded to only a few(For example 2
Double as the argument and the value decimal places)
has many decimal places, the value is
not rounded correctly. This may impact
values set using the Zyqad Cost Mapper
interface.
The Total cost for non-Design models is None
not returned to the Zyqad Cost Mapper
interface. Non-Design models(Models
that start with E - IE EVS etc) typically
have less than 11 fields on the input
forms
Cannot save project after sizing shell The object database engine that is
and tube heat exchanger using HTFS+ launched during Teams sizing does not
Teams. close and prevents the project from
being saved. The user can shutdown the
database engine manually. In the
Windows taskbar the user will see an
application with “CST_RSLT” in the title
bar. Click on this application and click the
“shut down” button. Click “OK” on the
dialog box that appears. This will shut
down the database engine. After that the
project can be saved.

Aspen Kbase 43
 General Usability Issues Workaround/Comment

Not all EN/DIN/JIS materials can be All materials in ICARUS have been
imported from Teams to Kbase when mapped to appropriate ASME materials
sizing shell and tube heat exchangers in Teams. This mapping is not complete
using Teams. for EN/DIN/JIS materials. If you choose
a material from these databanks in
Teams, they may not be properly
imported into ICARUS. The Teams
design, weight and cost information will
be imported irrespective of the material
selection in Teams. However you may
not see the appropriate material name in
ICARUS since the material may not be
mapped.
Opening or Attaching a Volumetric The values are saved to the file when
Model Library item with specifications initially specified but are being lost when
for Pipe Item Detail line sizing fields re-opened or attached. No workaround
does not show the values in the exists.
application interface.
In some projects, deleting a contractor Only workaround at this time is to export
from a project with multiple contractors the project into a specs file, edit it and
causes a crash upon reopening the import the file again.
contractor tree. However, it does not
happen in all projects
In German Windows XP, when a project Proceed to evaluate a second time and
is opened, and evaluated for the first work with the estimate.
time, it crashes; subsequent evaluations
do no produce a crash
In IPS, first attempt to schedule a This is a Primavera issue, and no solution
project causes error messages; is known at this time.
subsequently, scheduling works Generate the schedule a second time,
correctly. this should correct the issue.

44 Aspen Kbase
Aspen Model Runner

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 Model Runner 45

Aspen MUSE

Coexistence Issues Workaround/Comment

No known issues Not applicable

Installation Issues Workaround/Comment

Microsoft Vista Users If users wishes to run the example input

files supplied with the product, and they
have a restricted user account (which will
more than likely be the case for Vista but
can also occur with Windows XP), they
need to copy the example files from their
installed location to a folder to which
they have write access. When running
the sample programs, they should select
the files from this location.
In addition, users with Restricted User
status might need to have someone with
administrator privileges set their
Component and Stream databank
locations to some folder to which the
user has write access. This can be done
by using the File Preferences and setting
the desired location for the CBANK| files.
This can be done immediately after the
installation.

General Usability Issues Workaround/Comment

No known issues Not applicable

46 Aspen MUSE
Aspen OLI Interface

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 OLI Interface 47

Aspen OnLine

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

48 Aspen OnLine
Aspen Online Deployment

Coexistence Issues Workaround/Comment

No known issues Not applicable

Installation Issues Workaround/Comment

No known issues Not applicable

General Usability Issues Workaround/Comment

Unexpected simulation failures To ensure the largest number of simulations

due to exhaustion of Windows can be run before encountering the desktop
desktop heap. See Microsoft heap limitation, use the Aspen Remote
Knowledge Base articles 126962 Simulation Server in conjunction with Aspen
and 184802. Online Deployment.
You should use the Services control panel
applet to modify the Aspen Remote Simulation
Server service properties to:
a) “Logon as System”
b) “Interact with desktop”
Then configure your Online Deployment
applications to use the Remote Solver.
Why does this work? The default desktop heap
size used by Aspen Online Deployment
applications solving locally is 512KB, and this
non-interactive desktop heap is shared among
many services and so is likely more that half
consumed already. A similar situation exists
for the Remote Simulation Server – however,
by configuring it to “Interact with desktop” the
Remote Simulation Server will use the
interactive desktop heap, which is 3072KB – six
times as large as the non-interactive desktop
heap.

Note: It is OK to run the Remote

Simulation Server service and the online
server for Aspen Online Deployment on

Aspen Online Deployment 49

 the same computer system.

50 Aspen Online Deployment

Aspen Open Object Model
Framework (OOMF)

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 (OOMF) 51

Aspen PIPE

Coexistence Issues Workaround/Comment

No known issues Not applicable

Installation Issues Workaround/Comment

Microsoft Vista Users If users wishes to run the example input

files supplied with the product, and they
have a restricted user account (which will
more than likely be the case for Vista but
can also occur with Windows XP), they
need to copy the example files from their
installed location to a folder to which
they have write access. When running
the sample programs, they should select
the files from this location.
In addition, users with Restricted User
status might need to have someone with
administrator privileges set their
Component and Stream databank
locations to some folder to which the
user has write access. This can be done
by using the File Preferences and setting
the desired location for the CBANK| files.
This can be done immediately after the
installation.

General Usability Issues Workaround/Comment

No known issues Not applicable

52 Aspen PIPE
Aspen Plus

Coexistence Issues Workaround/Comment

No known issues Not applicable

Installation Issues Workaround/Comment

Microsoft SQL Express installation will Before installing Aspen Plus on Windows
fail on Windows 2000 if MDAC 2.8 SP1 is 2000, verify that the required version of
not installed. MDAC is installed. Use Windows Update
to update MDAC, or download from:
http://www.microsoft.com/downloads/
details.aspx?FamilyID=78cac895-efc2-
4f8e-a9e0-3a1afbd5922e&
DisplayLang=en

The property databases for Aspen If possible (enough disk space exists),
Properties Enterprise Database are not uncompress the drive by navigating to
created if the drive where they are the drive in Windows Explorer. Right-
installed is compressed. You may get click it and select Properties, and clear
the following message if you try to the checkbox Compress drive to save
restore them manually: disk space.
The file "C:\Documents and Settings\All
Users\Application Data\AspenTech\APED
2006.5\AP065.MDF" is compressed but
does not reside in a read-only database
or filegroup. The file must be
decompressed.

General Usability Issues Workaround/Comment

Context sensitive help does not work on The topic BatchSep Reference in the Unit
the BatchSep forms when using the Operations Reference help for Aspen
BatchSep block in Aspen Plus. Plus has links to the relevant sections of
BatchSep help.
Time profiles for key results variables in This is planned to be added in
BatchSep are not available. Cumulative Patch 1 for version 2006.5.
A BatchSep column within Aspen Plus An effort will be made to address this

Aspen Plus 53
 takes 2 to 5 times longer to solve than issue in the next version.
an identical column in Aspen BatchSep.
Consistency checking for connecting It is recommended that you attach at
streams is not supported. BatchSep will least one stream to each of the Pot
run without any streams attached. Charge, Final Column Contents, and
Distillate Streams ports.
Accessing BatchSep variables as Block- Use Block-Var to access each element of
Vec in operations such as Design-Specs the vector individually.
is not supported.
Some BatchSep columns initialized at This will be addressed in the next
Empty may fail to converge when run version.
inside Aspen Plus.
Documentation asks users to use the This program is no longer needed, and is
regcounit.exe program to register Visual no longer delivered. Use regsvr32 to
Basic CAPE-OPEN unit operation models, register Visual Basic CAPE-OPEN unit
but the file is not delivered. operation models, in the same way that
is described for C++ models in chapter
26 of Aspen Plus User Models.
Alternatively, use one of the other
methods in that chapter for Visual Basic
models besides regcounit.exe.
You cannot connect to the Aspen Configure the server for SQL Server
Properties Enterprise Database server if and Windows authentication mode.
it is not configured for SQL Server and Detailed instructions are in the topic
Windows authentication mode. This Troubleshooting Connections to a
problem occurs when a pre-existing Database Server in the
server not installed by the Aspen Troubleshooting section of the Aspen
installer is used. Properties Database Manager help.
You cannot connect to the Aspen Microsoft SQL Server Express uses a
Properties Enterprise Database server modified server name. Instead of
when Microsoft SQL Server Express is localhost, use .\SQLEXPRESS as the
used as the server. name of the local server. For a remote
server, add \SQLEXPRESS after the
computer name.
When using Aspen Properties Enterprise A patch from Microsoft will allow you to
Database on Microsoft SQL Server 2005 connect to the server. Visit:
or Microsoft SQL Server Express on a http://www.microsoft.com/downloads/
remote server, if only Microsoft SQL details.aspx?FamilyId=D09C1D60-A13C-
Server 2000 and/or MSDE is installed 4479-9B91-9E8B9D835CDC&
locally, you may be unable to connect to displaylang=en
the server, with this error:
Download the Microsoft SQL Server 2005
Linking to the server failed. Check your Backward Compatibility Components,
input for Login Name, Password, and and install the component SQLDMO from
Server. this package.
Copy-paste links of data into Excel do This issue is expected to be fixed in
not update the values in Excel when the 2006.5 CP1.
data changes in Aspen Plus.

54 Aspen Plus
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 Plate+ 55
Aspen Process Tools

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

56 Aspen Process Tools

Aspen Properties

Coexistence Issues Workaround/Comment

No known issues Not applicable

Installation Issues Workaround/Comment

Microsoft SQL Express installation will Before installing Aspen Properties on

fail on Windows 2000 if MDAC 2.8 SP1 is Windows 2000, verify that the required
not installed. version of MDAC is installed. Use
Windows Update to update MDAC, or
download from:
http://www.microsoft.com/downloads/d
etails.aspx?FamilyID=78cac895-efc2-
4f8e-a9e0-
3a1afbd5922e&DisplayLang=en

The property databases for Aspen If possible (enough disk space exists),
Properties Enterprise Database are not uncompress the drive by navigating to
created if the drive where they are the drive in Windows Explorer. Right-
installed is compressed. You may get click it and select Properties, and clear
the following message if you try to the checkbox Compress drive to save
restore them manually: disk space.
The file "C:\Documents and Settings\All
Users\Application Data\AspenTech\APED
2006.5\AP065.MDF" is compressed but
does not reside in a read-only database
or filegroup. The file must be
decompressed.

General Usability Issues Workaround/Comment

You cannot connect to the Aspen Configure the server for SQL Server
Properties Enterprise Database server if and Windows authentication mode.
it is not configured for SQL Server and Detailed instructions are in the topic
Windows authentication mode. This Troubleshooting Connections to a
problem occurs when a pre-existing Database Server in the
server not installed by the Aspen Troubleshooting section of the Aspen
installer is used. Properties Database Manager help.

Aspen Properties 57
58 Aspen Properties
 General Usability Issues Workaround/Comment
You cannot connect to the Aspen Microsoft SQL Server Express uses a
Properties Enterprise Database server modified server name. Instead of
when Microsoft SQL Server Express is localhost, use .\SQLEXPRESS as the
used as the server. name of the local server. For a remote
server, add \SQLEXPRESS after the
computer name.
When using Aspen Properties Enterprise A patch from Microsoft will allow you to
Database on Microsoft SQL Server 2005 connect to the server. Visit:
or Microsoft SQL Server Express on a http://www.microsoft.com/downloads/
remote server, if only Microsoft SQL details.aspx?FamilyId=D09C1D60-A13C-
Server 2000 and/or MSDE is installed 4479-9B91-9E8B9D835CDC&
locally, you may be unable to connect to displaylang=en
the server, with this error:
Download the Microsoft SQL Server 2005
Linking to the server failed. Check your Backward Compatibility Components,
input for Login Name, Password, and and install the component SQLDMO from
Server. this package.

Copy-paste links of data into Excel do This issue is expected to be fixed in

not update the values in Excel when the 2006.5 CP1.
data changes in Aspen Properties.

Aspen Properties 59
Aspen Polymers Plus

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

60 Aspen Polymers Plus

Aspen Process Manual

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 Manual 61

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

Petroleum Properties with the same Use “Copy Properties” button to transfer
name as user properties will not be the properties from user properties to
imported from PIMS assay. petroleum properties.
Oil Manager oil when imported to Use “Assay Manipulator” to refine TBP
RefSYS petroleum assay has a curves and property curves.
discrepancy in TBP and property curves.

IBP and FBP estimation for intermediate Not available.

stream is poor when lightest boiling and
heaviest boiling hypos have large
composition.
Pure component properties will not be RefSYS/HYSYS will take its own pure
imported from PIMS data. If there are component properties. This will be more
pure component properties such as accurate and consistent. You must
RON/MON/Sulphur etc. in PIMS csv file, remove pure component properties from
wrong property curves are generated. PIMS csv file.
When HYSYS hypos and RefSYS hypos You should create separate fluid package
are together in one fluid package, for each type of hypo.
incorrect results are obtained from
RefSYS unit operations such as
Petroleum column.
When HYSYS hypos and RefSYS hypos Build a new case where HYSYS hypos
are together in one fluid package and and RefSYS hypos are in separate fluid
you delete a blend from the oil packages.
environment, incorrect composition is
assigned to RefSYS hypos.

62 Aspen RefSYS
 Plots in Column Calibration do not Not Available.
update when performing manual tuning.
Spurious inconsistency errors around Re-flash recycle outlet stream by
recycle outlet streams. modifying its operating conditions.
A PIMS assay can be imported only for Not Available.
the default fluid package.

The No Creep and Abort buttons do not Manually create a dmo.msg to turn the
always show up for the FCC, Reformer, creep steps off or abort the run.
and Hydrocracker models. At times,
when they do show up, they can’t get
control from OOMF so they are
ineffective.
The hydrocracker currently does not For operations where you think the
transfer metals or concarbon. For many metals or concarbon will not be
units, this approximation is fine, but for completely removed, you can use an
some units, it is important to have real assay manipulator to reset the curves.
values.

Currently, none of the internal streams Not available.

for a RefSYS reactor model are exposed
in RefSYS.
The feed distillations reported on the Not available.
Feed Blend page of the Hydrocracker
and Reformer are not correct. They
should be based on API correlation
conversions.
It is possible for some compositions for It may be possible to prevent this by
the Reformer and Hydrocracker to go putting appropriate lower bounds on
slightly negative during a recon run. It some calculated variables.
is also possible for the quench flows for
a Hydrocracker to go negative.
There is a limit of 4 beds per reactor for If more than 4 beds are needed for a
the Hydrocracker. Models for reactors reactor, it is possible to move some of
with more than 4 beds will require some the beds to a subsequent or previous
modifications. reactor.
The Hydrocracker model currently You can back calculate a bromine
makes no use of olefin data from an number so that the correct olefin content
assay. If you connect an external is calculated by the model.
stream, you must still enter a bromine
number so that the model can calculate
an olefin content.
API, MW, gravity and distillation are not Not available.
calculated by the reformer transition for
a virtual feed.
The user cannot specify the individual If you want to specify the individual
reactor inlet temperatures for a reactor inlet temperatures, you should
reformer along with WAIT, WABT, C5+ specify the reference inlet temperature.
RON, C6+ RON, or aromatics wt. % of
feed.
RefSYS crashes if you add a reformer Not available.
with a stabilizer tower to a flowsheet
with a petroleum assay.

Aspen RefSYS 63
Aspen Remote Simulation
Service

Coexistence Issues Workaround/Comment

No known issues Not applicable

Installation Issues Workaround/Comment

No Known Issues Not applicable

General Usability Issues Workaround/Comment

No know Issues Not applicable

64 Aspen Remote Simulation Service

Aspen Simulation Workbook

Coexistence Issues Workaround/Comment

No known issues Not applicable

Installation Issues Workaround/Comment

When Aspen Simulation Workbook is Visit

installed on MS Office 2003, the patch http://support.microsoft.com/kb/907417
for Microsoft KB 907417 is required to download and install the patch
before the product can be installed. This manually. Any errors that occur during
patch can fail in some cases when there the installation will be visible. The patch
is a problem with the Office installation, may request the original Office
and when it does so it can send the installation media to restore damaged or
AspenTech installer into an infinite loop. missing files. If the patch still fails,
consult Microsoft support.

General Usability Issues Workaround/Comment

Get ‘Excel waiting’ dialog after clicking Excel may be waiting for you to complete
Enable button. the Aspen Registration dialog which
sometimes is hidden behind Excel. Use
the Alt-Tab key combination to switch to
the registration dialog.
Unexpected simulation failures when This can be caused by exhaustion of
running cases remotely. Windows desktop heap allocated to the
Aspen Remote Simulation Service. See
Microsoft Knowledge Base articles
126962 and 184802.
More desktop heap is available if the
service configuration is changed to
a) “Logon as System” and
b) Enable “Interact with desktop”

Why does this work? The default desktop

heap allocation for a service is 512KB,

Aspen Simulation Workbook 65

 which must be shared with all cases
launched by the Remote Simulation
Service. Aspen Plus and ACM in
particular use a lot of desktop heap.
Configuring the service to “Interact with
desktop” will use the interactive desktop
heap, which is 3072KB – six times as
large as the non-interactive desktop
heap.

The Knowledge Base articles above also

detail how the registry may be modified
allocate more desktop heap to services
which do not “Interact with the desktop”
enabled.

66 Aspen Simulation Workbook

Aspen TASC

Coexistence Issues Workaround/Comment

No known issues Not applicable

Installation Issues Workaround/Comment

Microsoft Vista Users If users wishes to run the example input

files supplied with the product, and they
have a restricted user account (which will
more than likely be the case for Vista but
can also occur with Windows XP), they
need to copy the example files from their
installed location to a folder to which
they have write access. When running
the sample programs, they should select
the files from this location.
In addition, users with Restricted User
status might need to have someone with
administrator privileges set their
Component and Stream databank
locations to some folder to which the
user has write access. This can be done
by using the File Preferences and setting
the desired location for the CBANK| files.
This can be done immediately after the
installation.

General Usability Issues Workaround/Comment

No known issues Not applicable

Aspen TASC 67
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

No known issues Not applicable

68 Aspen Tasc+
Aspen Teams

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 Teams 69
Aspen Zyqad

Coexistence Issues Workaround/Comment

No known issues Not applicable

Installation Issues Workaround/Comment

No known issues Not applicable

General Usability Issues Workaround/Comment

Simultaneous editing of the Coordinate with other users to ensure that a

same drawing in two different drawing is not being edited by more than one user
drawing clients can cause one at the same time.
of the drawing clients to
crash. No data loss occurs.
The Datasheet Definer and Install Visio before installing Aspen Zyqad.
Excel generator cannot be
launched if Visio is installed
after Aspen Zyqad has been
installed.
Search in Help may not work The Help search command requires the creation of
properly. a file in the Program Files\AspenTech\Aspen Zyqad
2006\UserServices\Help folder. The first time the
Search feature is used, the user may need to be
logged in as administrator.
Kanji characters in class Only use ASCII characters in class names.
names are displayed
incorrectly in the CLE
inheritance view.

70 Aspen Zyqad
 General Usability Issues Workaround/Comment

Some customers have Enable automatic retry. To do so, you must set, on
reported issues with multiple the client computer, the following registry keys in:
client connections to a server HKEY_LOCAL_MACHINE\SOFTWARE\AspenTech\A
in network environments spen Zyqad\14.1\ClientTools
where user authentication
tends to be a slow process.

Key Value Description

RpcTimeout Workspace The value in
loading the seconds,
time + 10 after which
seconds first attempt
will be
cancelled and
we will
immediately
try second
time. The busy
dialog
disabled. By
default
RpcTimeout=0
will establish
regular
behavior with
just one
ConnectToWor
kspace call.
RpcTimeoutFoll 10 The timeout
ow value in
seconds for all
attempts
following the
first attempt.
RpcRetries 5 The number of
attempts to
perform,
before
returning
result to the
user.

Print Preview is disabled in None. The item is disabled to prevent a crash

Datasheet Editor. caused by a compiler error. A patch will be supplied
to enable Print Preview once the compiler error is
resolved.
Copy/Paste in Graphics None.
Definer may not work on Vista
OS.

Aspen Zyqad 71