Issues and Restrictions

Possible Issues

AEENV file

An issue may occur if you have duplicate entries in the AEENV file.  It would be advisable to send a complete AEENV file rather than single lines (i.e. if an AEENV.TXT file was used).

 

COM+ Proxies

An issue may occur if a web server cannot access the application server’s drive or share for available proxies.  In this case the old or previous proxies would be re-applied in order to still make the system somewhat useable.

 

Regression

We will usually only require the latest version of any file.  Under extreme circumstances, it may however be required to downgrade or regress a specific patch or file and this would require manual deployment as the INpPatcher does not cater for this.

 

Restrictions

Patches can only be applied from one source (either the Vendor web server, a local folder or the EXTRACTED ZIP folder structure) at a time.  It would be advisable to use the Vendor web server for simpler installations or smaller clients, whereas the folder or EXTRACTED-ZIP option would be best for large corporations, who would first like to test patches in a UAT or QA environment.  There is however no restriction in how the system works and it will run perfectly well in either configuration.