[ISS Support Case] Unknown Error
Last updated: March 7th, 2025Description
Unknown errors in the logger: Error Focus WWPackageServer Failed to deploy code modules for object[4140] Error: "'Error failed to deploy code modules to target" when deploying objects to another node. The AppServer Enterprise PC's have fixed IP addresses, are part of a workgroup, and there are no WINS or DNS or Host files. Reinstall AppServer on target node. This will redeploy the bootstrap and resolve the IP address issues. From aaPim Access Denied. (80030005) raised at line 4283 in PimPF.cpp (in D:\BldSrc1\178\s\src\PlatformInstallManager\WWPim\). Summary As previously noted in Tech Note TN10225, security improvements made in System Platform 2017 Update 3 included changes made to the user accounts and groups to utilize Virtual Service Accounts. These accounts and groups are needed for Wonderware products to function properly. Some customers have policies to eliminate unrecognized accounts and groups. This Tech Alert highlights information about the importance of the aaPim account's group membership. Situation aaPIM is the platform installation manager that is responsible for installing platforms. In previous versions aaPIM is launched on demand as a process with Adminintrator privilege. However, in System Platform 2017 Update 3, it is changed into a windows service and added to the Administrators group as a service account. It's important not to remove the NTService\aaPim account from the Administrators group unless you follow recommendations outlined in TN10297 Managing Service Accounts with Group Policy for System Platform 2017 Update 3. Symptoms If aaPim is removed from the Administrator group on System Platform 2017 Update 3, AppServer Deployment will fail. The error message will be similar to this: Error: Failed to deploy RemotePlatformName : Remote Node's UserId/Password don't match GR Node's Action Use exceptions in your IT Policies or Scripts to not delete the required Virtual Service Accounts or follow workaround recommendations outlined in TN10297. From
- Author: Kevin Modlin
- Published: March 7th, 2025
Details:
Product: Application Server |
Version: 2020 R2 |
Solution: [Solution is visible below when you're logged in and have a current subscription] |
Date Created: | 10/13/2023 |
Case: | 85318 |
Recommended articles
[ISS Support Case] Synchronize Views is not working correctly in the IDE
Read More[ISS Support Case] Historian Data Gap On Appengine Failover In SP Version 2023 R2 P1
I am seeing an issue with SP2023 R2 P1 related to appengine failovers. When I cause an appengine failover, data (primarily analog) has a gap in the trend until the data changes. Sometimes the gap stays but sometimes the gap is "filled" in for some reason. I'm having a bit of a consistency issue trying to replicate this problem. Every time I cause a failover, the results are slightly different but I do see bad results. To demonstrate this, I created two videos to show what I'm seeing. If someone can create a problem ticket and reach out to me, I can forward the videos to InSource to show what I'm seeing.
Read More[ISS Support Case] MQTT setup crashes OCMC
MQTT server - CDP 2023 check encryption/validate security - no issue port validates enable user identity/try to bring certs in shuts down OCMC nothing in OCMC logs event viewer shows an app crash for mmc with cfg_mqtt_plctype1.dll as the faulting module advised repair after conferring with aveva - called client to discuss and confirm New SR960455477 (requesting) Log file Config Files Do Not upgrade Stay @ the same version of CDP Call in on 9/12/2024 No success on the MQTT server with the antivirus turned off, and it was even worse this time. Could not hook to AWS server. Proceeded to step 2, entered certificate in case it needed to log in to AWS server, but the OCMC shut down. Restarted OCMC acted strange, restarted computer. OCMC behaved normally after, but still no success with MQTT. Wants a call back whenever you're available, doesn't have to be tonight. CDP shows 2023
Read More