Release Notes
Engineering design productivity tool focused on rapid automation application development leveraging (ACM)
Version 4.01.00 (released 12/2020)
Catalog Number Studio 5000 Application Code Manager
These release notes describe version information for Studio 5000 Application Code Manager, version 4.01.00 (released 12/2020).
Requirements
This release has the following requirements.
To run Application Code Manager software version 4.01.00, the host computer must meet the hardware
and software requirements. For the latest compatibility information, refer to the Product Compatibility
and Download Center.
|
Important:
|
Application Code Manager requires a Codemeter
license to activate the product in Standard mode,
however the product will still operate in Lite mode
without a license but some features will not be
available.
|
Hardware requirements
- Processor – Intel Core i5
- Speed – 2.4 GHz
- RAM memory – 8 GB
- Hard Disk Space – 20 GB free
Minimum Requirements: Intel® Core™ 2 Duo, 2.8 GHz, 4 GB, with 16 GB free space
Software requirements
- Studio 5000 Logix Designer® version 27 or higher (up to and including version 33) for Logix
Library Development
- Studio 5000 Logix Designer version 20 or higher (up to and including version 33) for Logix
Project Development
- Microsoft® Office 2010 or higher for Logix Project Development
Application Code Manager is supported on computers with 64-bit operating systems. This version of
Application Code Manager was tested on these operating systems:
- Windows 7 Professional (64-bit) with Service Pack 1
- Windows 10 Enterprise (64-bit) 1909
- Windows 10 Professional (64-bit) 1903, 1909, and 2004
See the Windows Lifecycle FAQ and Windows as a Service (WaaS) topics on the Microsoft®
Website for details regarding servicing requirements and other important information.
- Windows Server® 2008 R2 Standard Edition with Service Pack 1
- Windows Server 2012 R2 Standard (64-bit)
- Windows Server 2016 Standard (64-bit)
- Windows Server 2019 Standard
Application Code Manager was tested on these Microsoft® SQL Server® versions:
- SQL Server 2008 Express (64-bit) (Microsoft SQL Server 2008 R2 SP2 – Express Edition)
- SQL Server 2012 Express (64-bit) (Microsoft SQL Server 2012 Service Pack 4)
- SQL Server 2016 Standard (64-bit) (Microsoft SQL Server 2016 Service Pack 2)
- SQL Server 2016 Express (64-bit) (Microsoft SQL Server 2016 Service Pack 2)
- SQL Server 2017 Express (64-bit) (Microsoft SQL Server 2017 – Express Edition)
Application Code Manager was not tested on these Microsoft SQL Server versions:
- SQL Server 2012 Express (64-bit) (Microsoft SQL Server 2012-Express Edition)
- SQL Server 2014 Standard (64-bit) (Microsoft SQL Server 2014 Service Pack 3)
This version of Application Code Manager is expected to operate correctly on all other editions and
service packs of these operating systems but was not tested:
- Windows 10 Enterprise (64-bit) 1803, 1809, 1903, and 2004
- Windows 7
- Windows 8
- Windows 8.1 Professional (64-bit)
- Windows Server 2012
- Windows Server 2012 R2
|
Important:
|
Windows 8 and later operating systems run on
many touch-enabled devices, various features of
the application may not be touch-enabled. Most
functions are expected to work with touch, but the
software has only been tested with a keyboard and
mouse.
|
When you install Application Code Manager this software is installed if not already present:
- FactoryTalk Diagnostics version 6.20.00
- FactoryTalk Activation Manager 4.04.14
- Logix Designer Compare Tool 8.12
- .NET Framework 4.6
- SQL Server 2012 Express (only in Windows 7)
- SQL Server 2016 Express
Preferred operating systems
Preferred operating systems are prioritized for support, testing, and post-release patch qualifications.
These operating systems are preferred for this release:
- Windows 10 Professional (64-bit)
- Windows Server 2016 Standard (64-bit)
- Windows Server 2012 R2 Standard (64-bit)
High Resolution Display Support
Windows 10 v1703 or later is the recommended operating system if running this software with a 2K or
4K High Resolution Display with scaling up to 125%.
Rockwell Automation Test Environment
Rockwell Automation tests software products under a standard configuration of operating systems and
antivirus software. For additional information see the Knowledgebase Document ID: PN24 - Rockwell
Software Products and Antivirus Software.
Supported browsers
The following web browsers have been tested and are supported for use with this release:
- Google® Chrome™ browser
- Internet Explorer® 11
- Mozilla® Firefox®
Security requirements
To help meet secure system design requirements review these publications:
Features
This release includes the following system features.
Application Code Manager version 4.01.00 has these new and enhanced features:
New features
Application Code Manager
- There are no new features in this release.
Library Designer
- Add a Max Length attribute
This release adds a Max Length attribute to the object scope to string type parameters. Configure
this value for the user-defined parameters to limit the length of the strings.
Library Object Manager
- There are no new features in this release.
Application Code Manager Console
Library Object Import Wizard
- There are no new features in this release.
Enhanced features
Application Code Manager
- Automatically open the destination folder
In this release, after exporting a library or extracting attachments from the Registered Libraries
tree, the destination folder is opened automatically.
- Navigate to the library
This release supports navigating to the library in the Registered Libraries tree by right-clicking the
library in Class View.
- Match the version of Studio 5000 Logix Designer
In this release, when generating a controller and there is no matching version of Studio 5000 Logix
Designer with the selected SoftwareRevision, the CreateACD checkbox is disabled.
- Enhance Windows Authentication
This release supports using Windows Authentication to create, delete, update, backup, and restore
databases in the Database Manager dialog box.
Library Designer
- Select rungs using the keyboard
This release supports selecting rungs in the Rung Decorator dialog box using the Up and Down
arrow keys on the keyboard.
- Select multiple Linked Libraries
This release supports selecting multiple Linked Libraries and interfaces when deleting libraries on
the Linked Libraries tab.
- Enhance tooltips
In this release, the tooltip of predefined functions in Expression Builder will be shown in a dialog
box.
- Enhance the deleting confirmation
In this release, the confirmation prompts once when deleting one or multiple libraries from Library
Objects.
- Validate predefined values
This release adds the validation of predefined instances values against the parameter datatype in
the SubObject Builder.
- Warning message of container mode
This release adds a warning message when a Task, Program, or Routine is in the container mode.
Library Object Manager
- There are no enhanced features in this release.
Application Code Manager Console
- There are no enhanced features in this release.
Corrected Anomalies in This Release
This release corrects the following anomalies.
Corrected anomalies introduced in Application Code Manager version 4.01.00:
Application Code Manager
- In the previous version, it was not possible to add a remote library repository using Windows
Authentication in the connection string. First identified in Application Code Manager version
4.00.00. [Jira 961425]
In this release, remote library repositories are added successfully.
- In the previous revision, after copying and renaming an object with a parameter configuring the
ObjectName as the default value, the value of the ObjectName will not be updated. First
identified in Application Code Manager version 4.00.00. [Jira 971082]
In this release, the value will be updated.
- In the previous revision, after copying a Routine type object instance that the TaskName and
ProgramName are substituted, the Task column will disappear. First identified in Application
Code Manager version 4.00.00. [Jira 967037]
In this release, the Task column will be shown.
- In the previous revision, if a project record has an invalid ObjectID that does not exist in the
ACM database, the project cannot be opened or deleted. First identified in Application Code
Manager version 4.00.00. [Jira 971094]
In this release, a warning message reminds you to delete the invalid project.
- In the previous revision, the Find button and the Replace All button in Document Template
Editor are in inappropriate sizes. First identified in Application Code Manager version 4.00.00.
[Jira 964204]
In this release, these two buttons are in appropriate sizes.
- In the previous revision, quotation marks in Repeat instructions were not validated in Document
Template Editor. First identified in Application Code Manager version 4.00.00. [Jira 887428]
In this release, Document Template Editor validates quotation marks.
- In the previous revision, when updating library instances using the Library Update form, the
mouse pointer did not show the correct status. First identified in Application Code Manager
version 4.00.00. [Jira 887099]
In this release, the mouse pointer shows the loading status.
Library Designer
- In the previous revision, when publishing a library or after closing the Publish Library dialog
box, the mouse pointer did not show the correct status. First identified in Application Code
Manager version 4.00.00. [Jira 938740]
In this release, the mouse pointer shows the loading status.
- In the previous revision, when double-clicking a rung in the Decorator panel, the Substitution
Builder did not start. First identified in Application Code Manager version 4.00.00. [Jira 887419]
In this release, the Substitution Builder starts.
- In the previous revision, after selecting Show Dependencies, the mouse pointer did not show
the correct status. First identified in Application Code Manager version 4.00.00. [Jira 938742]
In this release, the mouse pointer shows the loading status.
- In the previous revision, the tabs in the New/Edit SubObject dialog box are out of order. First
identified in Application Code Manager version 4.00.00. [Jira 887280]
In this release, these tabs are in the correct order.
- In the previous revision, when removing rungs from the Decorator panel, the mouse pointer did
not show the correct status. First identified in Application Code Manager version 4.00.00. [Jira
943075]
In this release, the mouse pointer shows the loading status.
Library Object Manager
- There are no corrected anomalies in this release.
ACM Console
- In the previous revision, when generating a script file, the order of programs is incorrect. First
identified in Application Code Manager version 4.00.00. [Jira 956393]
In this release, the order is updated to the correct one.
- In the previous revision, configuring a program name using the "{ObjectName}xxx" format will
create two programs. First identified in Application Code Manager version 4.00.00. [Jira 942819]
In this release, ACM console creates one program that configured the correct name.
Known Anomalies in This Release
This release has the following known anomalies.
The following list identifies the known anomalies or limitations of Application Code Manager version 4.01.00 at the time of the release.
- The Library Object Import Wizard does not support importing SFC library contents
When importing a library instance contains an SFC routine using the Library Object Import Wizard
or importing an existing program in the ACD contains an SFC routine, the import operation stops
to prevent an exception in Studio 5000 Logix Designer.
To avoid this issue, use the ACM Target ACD or Sync ACD to import a library instance contains SFC
contents.
- An exception occurs in Studio 5000 Logix Designer if any FBD routine is open in the background
when importing library contents using the Library Object Import Wizard.
To avoid this issue, ensure all FBD routines are closed in Studio 5000 Logix Designer before running
the Library Object Import Wizard.
- Context-sensitive Help in Library Designer.
If Library Designer is opened from Studio 5000 Logix Designer, when pressing F1 to open the Help,
the Help files for Studio 5000 Logix Designer are opened instead. Use the Help button or the
Help menu within Library Designer to open the Library Designer Help.
- Include conditions on Tasks and Programs.
When the controller is generating in Application Code Manager, the Include conditions applied to
Tasks and Programs will be ignored.
- When running the Studio 5000 Application Code Manager Installer, an error might occur in
certain environments.
A known issue exists for the SQL Server installer where an existing (installed) SQL Native Client
installation is not detected by the main (SQL Server) installer and an attempt is then made to
re-install the SQL Native Client. The installer then produces an error stating that the installation
files for the SQL Native Client cannot be found.
To resolve the blocking error to ensure that the Studio 5000 Application Manager Installer runs
successfully, remove the existing Microsoft SQL Server 2012 Native Client manually using the
Add\Remove Programs. The installer can then be run again and the issue should be resolved.
- After installing Studio 5000 Logix Designer, a Logix service error might occur when mounting an
ACD file in Library Object Manager or generating an ACD file from Application Code Manager.
To resolve this issue, reinstall Application Code Manager.
- After installing Application Code Manager for the first time, a Logix service error might occur
when generating an ACD file from Application Code Manager for some Operating System
Regional Language settings.
To resolve this issue, run Library Object Manager, and then regenerate the ACD file in Application
Code Manager.
- When using Studio 5000 Logix Designer version 31 or earlier, an error might occur when using
Library Object Import Wizard to insert library objects that contain Custom Properties.
To avoid this issue, remove the Custom Properties in the controller, or use the Target ACD in the
Application Code Manager to insert library objects, or use a higher version of Studio 5000 Logix
Designer.
- When the PlantPAx tasking model is enabled in the controller, using Library Object Import
Wizard to insert library objects will fail.
To avoid this issue, use the Target ACD to add library objects in Application Code Manager.
- When adding module instances to an ACD file using the Library Object Import Wizard or the Target ACD, use drag\drop or double click functionality instead of right click, Add New option to avoid launching the Object Configuration Wizard as the ChassisName attribute may remain disabled or Read Only.
Functional Changes
This release has the following functional changes from the previous release.
Application Code Manager version 4.01.00 has no changes in functionality since the last release.
Application Notes
This release has the following application notes.
These are the application notes for Application Code Manager version 4.01.00
Launching of the Library Designer as a 64-bit application
When Library Designer is launched from the Library Object Manager it launches as a 64-bit application
and can utilize much more memory which will prevent Out of Memory errors currently observed on large
files, however if the Library Designer is launched from Studio 5000 Logix Designer it will only run as a
32-bit application.
Recommended SQL connection settings
When connecting to an ACM database, applying the recommended settings as defined on the ACM
help page for the Advanced Properties will improve performance, especially for network connections.
Updating or adding a new controller from a Logix Designer Project
If an ACM controller project is linked to a Logix Designer Project file to improve performance and
reduce loading time upon opening Application Code Manager or switching between projects, it is
recommended that the L5X file format be used instead of the ACD file format. If using an ACD file is
required, it is recommended that the ACM controller project be detached from the ACD file prior to
closing Application Code Manager or switching projects.
Unattended or silent install
Use command-line parameters to perform an unattended or silent installation of the software.
Command-line parameters
The following table identifies the installation command-line parameters. Command-line parameters are
case-insensitive. However, if a specified value includes a space, be sure to enclose the value in
quotation marks (for example, "value with spaces").
|
Parameter
|
Description
|
|
/?
|
Displays the usage options for installation parameters.
|
|
/Q
|
Silent Install, install runs in a quiet mode without any user interface.
This parameter is recommended when deploying the software installation
using an IT tool or script, and don’t expect any error or restart messages.
When using this parameter, check the error codes, and respond as needed.
For example, if the installation returns error code 1641, then the IT tool or
script should restart the computer and relaunch the installation after restart.
This parameter is required if /QS is not specified.
|
|
/QS
|
Unattended Install, install runs in a quiet simple mode and shows progress
through the UI, it does not accept any input but still shows error or restart
messages.
When using this parameter, the installation will stop and display a prompt if
there are error or restart messages. For example, if an immediate restart is
required to complete the install, a restart message will be displayed to confirm
the restart. Installation resumes automatically from the point of interruption
after restart.
This parameter is required if /Q is not specified.
|
|
/IAcceptAllLicenseTerms
|
Acknowledges acceptance of the license terms.
This parameter is required for /Q or /QS parameters.
|
|
/AutoRestart
|
Automatically restarts the computer after the installation is complete. Used
when a restart is required to complete the installation.
This parameter is optional. If this parameter is not used silent install (/Q) will
return either error code 1641 or 3010 if a restart is required, and unattended
install (/QS) will result in a confirmation prompt that must be agreed to before
the installation is completed.
|
|
/SetupLanguage="value"
|
Specifies which language will be displayed during install process.
The value must be the one of the following:
- ENU
- CHS
- DEU
- ESP
- FRA
- ITA
- JPN
- KOR
- PTB
This parameter is optional. If this parameter is not used, the default language
is the current user or operating system user interface language.
|
|
/Product="value"
|
Specifies which sub-products will be installed.
Only required if sub-products are included with the install package.
If the software does not include sub-products this parameter is not available.
|
|
/ProductLanguage="value"
|
Specifies the language version of the software being installed.
The value must be the one of the following:
- ENU
- CHS
- DEU
- ESP
- FRA
- ITA
- JPN
- KOR
- PTB
This parameter is optional. If this parameter is not used, the default language
is the same as the setup language.
If the software does not support multiple languages this parameter is not
available.
|
| /InstallLocation="value"
Or
/InstallDrive="value"
|
Specifies the install location or install drive respectively.
This parameter is optional. If this parameter is not used, the default install
location is "C:\Program Files (x86)\Rockwell Software".
Some software restricts the installer to only change the drive the software is
installed on. Use /? to determine which parameter is supported.
|
|
/SerialNumber="value"
|
Specifies the serial number of the software being installed. This is used to
activate the software during installation.
This parameter is optional. If it is not specified the software must be activated
manually after installation if activation is required.
Some software does not require activation. If activation is not required this
parameter is not available.
|
|
/ProductKey="value"
|
Specifies the product key used to get activation keys during installation.
This parameter is optional. If it is not specified the software must be activated
manually after installation if activation is required.
Some software does not require activation. If activation is not required this
parameter is not available.
|
|
/Version="value"
|
Specifies the version of the software to activate which corresponds to the
product version associated with the SerialNumber and ProductKey.
This parameter is optional. If it is not specified the installer will use the most
recent product version available.
Some software does not require activation. If activation is not required this
parameter is not available.
|
Examples
The following examples show how to use the installation commands.
- To install the software with no user interface using the default settings during the installation
process. (Silent install)
Setup.exe /Q /IAcceptAllLicenseTerms
- To install the Chinese language version of the software on the D: drive and display the progress,
error, or complete messages during installation and restart the computer if necessary.
(Unattended install)
Setup.exe /QS /IAcceptAllLicenseTerms /AutoRestart /SetupLanguage=CHS
/InstallDrive=D:
Error codes
The following table identifies the error codes that can be returned by an installation.
|
Error Code
|
Value
|
Description
|
|
ERROR_SUCCESS
|
0
|
The installation completed successfully.
|
|
ERROR_INVALID_PARAMETER
|
87
|
One of the parameters was invalid.
|
|
ERROR_INSTALL_USEREXIT
|
1602
|
The installation was cancelled by the user.
|
|
ERROR_INSTALL_FAILURE
|
1603
|
A fatal error occurred during installation.
|
|
ERROR_BAD_CONFIGURATION
|
1610
|
The configuration data for this product is corrupt. Contact your
support personnel.
|
|
ERROR_SUCCESS_REBOOT_INITIATED
|
1641
|
The installer has initiated a restart. After restart installation will
continue.
|
|
ERROR_SUCCESS_REBOOT_REQUIRED
|
3010
|
A restart is required to complete the installation. After restart the
product is successfully installed.
|
|
ERROR_SUCCESS_RELAUNCH_REQUIRED
|
3011
|
Restart of setup needed before installation can continue.
|
VeriSign Universal Root Certification Authority certificate
If the VeriSign Universal Root Certification Authority certificate does not exist on the local computer, the
certificate is installed while installing Rockwell Automation software. Use Microsoft Management
Console (MMC) to view the certificate in Console Root > Certificates (Local Computer) > Trusted
Root Certification Authorities > Certificates.
Rockwell Automation recognizes that some of the terms that are currently used in our industry and in this publication are not in alignment with the movement toward inclusive language in technology. We are proactively collaborating with industry peers to find alternatives to such terms and making changes to our products and content. Please excuse the use of such terms in our content while we implement these changes.
Copyright © 2026 Rockwell Automation, Inc. All rights reserved.
Rockwell Automation, Allen-Bradley, and FactoryTalk are trademarks of Rockwell Automation, Inc.
To view a complete list of Rockwell Automation trademarks please
click here.Trademarks not belonging to Rockwell Automation are property of their respective companies.