DMC3 Builder fails to deploy controllers after applying V11 CP1.
Download as pdf :
Products:
Aspen DMC3 Builder
Last Updated:
22-Oct-2020
Last Updated:
22-Oct-2020
Versions:
Article ID:
000097771
Article ID:
000097771
Primary Subject:
Attachments (1)
Attachments (1)
Problem Statement
After applying the CP1 patch for V11 in the Online server, the controller fails to deploy. When deploying, an error message appears saying to check various items but all of them look correct.
Solution
The problem occurs when there are V11 EP’s applied in the Online server and CP1 is applied above. On the other hand, this does not happen if CP1 was applied on a V11 installation with no EP’s.
The installer fails to update the ACESAppTemplate.xml file to the CP1 version, leaving the EP version. Therefore, the engine recognizes the version of the ACESAppTemplate does not match with CP1, and outputs an error message when trying to deploy the controller.
The workaround is to replace the attached ACESAppTemplate.xml. Here is the procedure:
Close all DMC3 Builder windows in the Online server (DMC).
Stop all the RTE controllers.
Stop the RTE service
Replace the attached ACESAppTemplate.xml file in the following locations.
C:\Program Files (x86)\AspenTech\APC\V11\Builder
C:\Program Files (x86)\AspenTech\RTE\V11\APC.
If you get an error “access denied”, make sure to log in with an administrator account, and copy the xlm file into the server and then to the locations mentioned.
Restart the RTE service. The application should deploy successfully.
Fixed in
Emergency patch 1 for CP1
Keywords
…Aspen DMC3 Builder, CP1, Online Server, VSTS 563037
Attachments
Filename
Date Added
ACESAppTemplate.zip
22-Oct-2020