Skip to main content
InSource KnowledgeCenter

TN AppSvr325 Check-list For Troubleshooting Failed Deployment Attempts on Industrial Application Server version 2017 Update 3

Description

 

This article from InSource shows a Checklist for troubleshooting failed deployment attempts on Industrial Application Server version 2017 Update 3

  • Author: Peter Farrell
  • Published: 6/17/2019
  • Applies to: Industrial Application Server 2017 Update 3

Details

Checklist for troubleshooting failed deployment attempts on Industrial Application Server version 2017 Update 3. This is not a complete list of possible causes for a failed deployment, but it should resolve most issues that are causing problems. 

 

To resolve failed to deploy on each of the target platforms

  1. Run the OS Configuration Utility
    From Search look for OSConfiguration
    Reboot
  2. Run the Change Network Account UtilityReboot
  3. Disable User Access Control (UAC) by pulling the slider to the bottom – never notify
  4. Confirm that DCOM is enabled from within DCOMcnfg navigate to Component Services > Computers > My Computer
    Right-click on My Computer and click Properties.
    On the Default Properties tab click the option for “Enable Distributed COM on this computer”
  5. Check to ensure that each of the following services are running and set to automatic
    ArchestrA Bootstrap
    ArchestrA Watchdog Service
  6. Check the network adapter priority settings (formally network binding order). The Interface Metric from within IPv4 Properties > Advanced settings should be the lowest of all interfaces on the machine.
  1. Disable IPv6
  2. Flush DNS – Start a command prompt and enter the following

     ipconfig /flushdns
 

  1. Use Wonderware Tech Alert number TA385 available on the Aveva Technical Support site at the URL shown below to add the following folders if missing:

 

https://sw.aveva.com/support/wonderware

Login as a user with administrative rights.
Check to see if the following directory exists:  C:\Windows\Serviceprofiles\aaPIM. If it does, check to see if it has the following sub-directory: \AppData\Local\Temp. It will appear as shown here:

C:\Windows\Serviceprofiles\aaPIM\AppData\Local\Temp.

If the sub-directories do not exist, create them.

Repeat the above steps for the following directories.
C:\windows\Serviceprofiles\AIMToken
C:\windows\Serviceprofiles\ArchestrADataStore
C:\windows\Serviceprofiles\AsbServiceManager
C:\windows\Serviceprofiles\InTouchDataService
C:\windows\Serviceprofiles\InTouchWeb
C:\windows\Serviceprofiles\Watchdog_Service
C:\windows\Serviceprofiles\aahClientAccessPoint
C:\windows\Serviceprofiles\aahSupervisor

Reboot the machine
 

  1. Enabling "everyone permissions" for anonymous users. To enable these permissions, go to: Local Security Policy > Local Policies > Security Options > Network Access: Let everyone permissions apply to anonymous


Right-click and enable “Network Access: Let everyone permissions apply to anonymous”
 

  1. If running Windows 10 or Windows Server 2016, from within the IDE > Platform configuration > General tab ensure that the platform network address does NOT include an underscore in the server name.


Note that naming conventions for server name is more rigid that it once was.  See the following article for more information:

https://en.m.wikipedia.org/wiki/Hostname

“While a hostname may not contain other characters, such as the underscore character (_), other DNS names may contain the underscore.”