Sunteți pe pagina 1din 16

Aspen Production Record Manager

V9

Release Notes
Version Number: V9
May 2016
Copyright (c) 2016 by Aspen Technology, Inc. All rights reserved.

Aspen Production Record Manager, Aspen Audit and Compliance Manager, Aspen InfoPlus.21, the aspen leaf logo,
and Plantelligence & Enterprise Optimization are trademarks or registered trademarks of Aspen Technology, Inc.,
Bedford, MA.

All other brand and product names are trademarks or registered trademarks of their respective companies.

This document is a guide for 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.


20 Crosby Drive
Bedford, MA 01730
USA
Phone: +(781) 221-6400
Toll Free: (1) (888) 996-7100
URL: http://www.aspentech.com
Contents
About these Release Notes......................................................................................1
Related Documentation .....................................................................................1

New Features ..........................................................................................................3

Software Fixes ........................................................................................................5


Fixed Defects...................................................................................................5

Known Issues..........................................................................................................7
MSXML4 is Available from AspenTech Support Website .........................................7
Aspen Audit & Compliance Manager and Event.21 are no longer supported by the
Extractor.........................................................................................................7
Extractor source database login needs to be updated after upgrading APRM Batch
Extractor.........................................................................................................8
Characteristic Browser shows characteristics with commas as "& strName &" ..........8
User cannot create, modify, or delete a characteristic if imported with Autoconfigure9
Batch does not open in the Batch Detail Display...................................................9
Characters not supported in characteristic names.................................................9
When you attempt to click a button to print an object model from the API Help, no
object model appears ..................................................................................... 10
DCOM settings for Production Record Manager install.......................................... 10
The APRM API and BCU API Help do not appear or appear without the ability to
navigate in Excel when using F1....................................................................... 10
No value in Data Source drop down list in Production Record Manager home page
(Windows Server 2008) .................................................................................. 12
Automated Reports not printing on Windows Server 2012 ................................... 12

Aspen Production Record Manager V9 Release Notes iii


iv Aspen Production Record Manager V9 Release Notes
About these Release Notes

These Release Notes describe Aspen Production Record Manager V9. This
document includes:
 New Features
 Software Fixes
 Known Issues

Related Documentation
In addition to these Release Notes, AspenTech provides the following
documentation for Aspen Production Record Manager V9.

Guides and Manuals


Aspen Production Record Manager Installation Guide
Aspen Batch Connect for OpenBatch User’s Guide
Aspen Production Record Manager Configuration Guide
Aspen Production Record Manager Getting Started Guide

Help Files
Aspen Production Record Manager Help
Aspen Audit and Compliance Manager Help
Aspen InfoPlus.21 Help

Aspen Production Record Manager V9 Release Notes 1


2 Aspen Production Record Manager V9 Release Notes
New Features

There are no new features for Aspen Production Record Manager V9.

Aspen Production Record Manager V9 Release Notes 3


4 Aspen Production Record Manager V9 Release Notes
Software Fixes

Aspen Production Record Manager V9 includes a number of software fixes that


further improve the product.
If you are interested in a particular defect that you do not see listed here,
contact your Support representative.

Fixed Defects
CQ Number Description
CQ00691576 ODBC 64bit driver configuration issue
CQ00602606 The schedule frequency is being ignored and
the schedule extracts continuously, rather
than waiting the configuration time
CQ00608392 When importing into APRM Spec files or BCU
files, the browse button always starts in
Program Files
CQ00596736 Referential integrity check to include the
BCU_PROCESSING_GATES table
CQ00610238 BCU skipping batch handles when the trigger
designator tag gets updated. Error messages
in BCU log
CQ00586784 Unit Plot hangs when adding units
CQ00590543 When APRM database server is down, Batch
Extractor will not handle the exception
properly
CQ00593369 APRM Excel Add-In not properly
generating .Bcu for triggers with constant
values
CQ00601541 After applying patch from solution ID 141697,
got error (see attached for details)
CQ00608238 Extractor is creating many batches of the
same designator values
CQ00611354 Failed to create batch report when web server
and APRM server are on different machine
CQ00696720 Unit Plot does not return units

Aspen Production Record Manager V9 Release Notes 5


6 Aspen Production Record Manager V9 Release Notes
Known Issues

This section describes the Known Issues in Aspen Production Record Manager
V9.

MSXML4 is Available from


AspenTech Support Website
MSXML4 is not installed during the installation process. However, MSXML4
SP2 is required if you install and use Aspen Production Record Manager
Legacy Excel Configuration Add-in. Go to https://support.aspentech.com to
get MSXML4 SP2.

Aspen Audit & Compliance


Manager and Event.21 are no
longer supported by the
Extractor
CQ00582943
The Aspen Audit & Compliance Manager and Event.21 tabs are not used any
more in the Configure Extraction Rules dialog box.

Aspen Production Record Manager V9 Release Notes 7


Extractor source database login
needs to be updated after
upgrading APRM Batch
Extractor
CQ00529569

Problem
After upgrading APRM Batch Extractor, if you do not update the Extractor
source database login, you may not able to use existing source database
connection.

Workaround
If you want to use existing source database connection after upgrading APRM
Batch Extractor, execute the following to update Extractor source database
login for the Extractor:
1. Launch Aspen Production Record Manager Batch Extractor.
2. Select the database you want to connect.
3. Select Admin | Configure Source Extraction Servers from the menu,
the Configure Source Extraction Servers dialog box appears.
4. Select an extraction server and click Properties, the Extractor Server
Properties dialog box appears.
5. Re-enter the Login Information and click OK.
Repeat steps 4 and 5 until you update source database connection for all the
extraction servers.

Characteristic Browser shows


characteristics with commas as
"& strName &"
CQ00221177

Problem
Commas are not recommended within characteristic names.

Workaround
Rename the characteristic without an embedded comma.

8 Aspen Production Record Manager V9 Release Notes


User cannot create, modify, or
delete a characteristic if
imported with Autoconfigure
CQ00202889

Problem
You cannot create, modify, or delete a characteristic in the same batch XML
submission. This causes an invalid state for the characteristic you submitted.

Batch does not open in the


Batch Detail Display
CQ00189901

Problem
A batch does not open in Batch Detail Display and the Oracle database and
displays a Multiple-step operation generated errors error message. This
occurs because characteristics are limited by the Oracle database drivers for
very large values (namely, e+205 for an ODBC driver and e+28 using an OLE
DB driver). The Oracle database drivers can write very large values, but not
read them.
Contact Oracle at http://www.oracle.com for a resolution.

Characters not supported in


characteristic names
CQ00187286

Problem
The following characters are not supported within subbatch and characteristic
names: open ("[") and closed ("]") brackets and commas (“,”).

Aspen Production Record Manager V9 Release Notes 9


When you attempt to click a
button to print an object model
from the API Help, no object
model appears
CQ00292492

Problem
From Aspen Production Record Manager Help, you cannot launch PDF files.
Therefore, you cannot view and print the Aspen Production Record Manager
and BCU object models.

Workaround
You can navigate to and print the Aspen Production Record Manager API and
BCU API object models from the Online Documentation Center or the
AspenTech Support Center.

DCOM settings for Production


Record Manager install
CQ00266540
An anonymous logon account is necessary for Aspen Production Record
Manager Services access permissions starting in version 2006. If you do not
have the account, then you cannot expand the data source object.

The APRM API and BCU API


Help do not appear or appear
without the ability to navigate
in Excel when using F1
Note: This defect applies equally to the Aspen Audit and Compliance Manager
API 2006.5. For details, see the “Known Issues” section of the Aspen Audit
and Compliance Manager Release Notes.

10 Aspen Production Record Manager V9 Release Notes


CQ00293372

Problem
When you:
1 Click Tools > References to open a Visual Basic Editor in Excel
2007 within Windows Vista.
2 Select either an available reference for Production Record Manager API or
BCU API and click OK.
3 Press F2 and select an API object, property, method, or event from the
object browser.
4 Press F1 to view help. You would expect to see a context-sensitive help
topic for that object, property, method, or event, but instead you see the
Microsoft Excel Help.
Or when you:
1 Click Tools > References to open a Visual Basic Editor in Excel within
Windows.
2 Select either an available reference for Production Record Manager API or
BCU API and click OK.
3 Press F2 and select an API object, property, method, or event from the
object browser.
4 Press F1 to view help. You do see context-sensitive help topic for that
object, property, method, or event; only the details pane of the help
appears. The Contents, Index, Search, or Favorites tabs do not
appear. Therefore, the ability to navigate to other help topics is impaired.

Workaround
To view the Production Record Manager Application Interface Help (sans
context sensitivity), launch the Production Record Manager Help by first
starting Aspen Production Record Manager. Open the Production Record
Manager Help and, from the Contents tab, navigate to the Production
Record Manager Help folder. Open the Interfaces folder and then the
Production Record Manager Application Interface Help folder.
To view BCU Application Interface Help (sans context sensitivity), launch
Production Record Manager Help by first starting Aspen Production Record
Manager. Open Production Record Manager Help and, from the Contents tab,
navigate to the Production Record Manager Help folder. Open the
Interfaces folder and then the Production Record Manager BCU
Application Interface Help folder.

Aspen Production Record Manager V9 Release Notes 11


No value in Data Source drop
down list in Production Record
Manager home page (Windows
Server 2008)
CQ00325146

Problem
Aspen Production Record Manager Web client displays an "Access is denied"
application error when installed on Windows Server 2008 and accessed from
the local server machine using a non-local administrator account. This error is
caused by Microsoft DCOM security configuration issue.

Workaround
1 From the local machine, run Internet Explorer as administrator.
2 Use machines other than the local server machine as the Web client.

Automated Reports not printing


on Windows Server 2012
Problem
Automated reports will not print on Windows Server 2012 systems.

12 Aspen Production Record Manager V9 Release Notes

S-ar putea să vă placă și