MW 2.19 multi node upgrade patching fails on second, third, etc node.

Question

When using Maintenance Wizard 2.19 with multi-node configuration patching will fail after the first node with an error in the adpatch log that states invalid options as seen below.
"AutoPatch warning:
Ignoring unrecognized option: "options".
Connecting to APPS......Connected successfully.
AutoPatch error:
You must be in Maintenance Mode to apply patches.
You can use the AD Administration Utility to set Maintenance Mode."
Please update this forum if you hit this issue and I can send you the fix until Maintenance Wizard 2.20 is released.
Thanks

Answer 1

As requested here's a paste of the command log, I can just see entries for the admin node and not the forms/web node.
Many Thanks
INFO - Help on monitoring when multiple drivers and nodes are applied.
If the web window times out, click on the x and rerun it to view the updated log
file. It will change as the patch continues to run in background. Just keep marking it
success until it is complete or check the active patch node manually:
$ tail -f $APPL_TOP/admin/${TWO_TASK}/log/patches_PRE_1703_1_patchit11i*.log
Each node, if multi-node, will be determined and the patch drivers will be applied
on the right nodes in the right order. Look for the ACTION: statement.
ACTION: execute on node: apps , patch=patches_PRE_1703_1 driver=u_merged.drv
patchit11i.sh REMOTE SIZE: 47535 LOCAL SIZE: 47535
OK - no update needed for patchit11i.sh, same size as on EOF: 47535 bytes.
Found release REL=11.5.10.2 from fnd_product_groups.
Starting adpatch for: patch=patches_PRE_1703_1 force= driver=u_merged.drv
Using defaults file /u10/orafun/appl/admin/FUN/adalldefaults.txt.
Starting patch with the following command:
/u10/orafun/appl/ad/11.5.0/bin/adpatch defaultsfile=/u10/orafun/appl/admin/FUN/adalldefaults.txt logfile=patches_PRE_1703_1_patchit11i.log patchtop=/u10/orafun/appl/patch/patches_PRE_1703_1 driver=u_merged.drv workers=6 interactive=no options=hotpatch,novalidate,nocompilejsp,nocompiledb,nomaintainmrc,nogenerateportion restart=n
Confirms adpatch is not still active, and views Check patch log times.
... PROCESS LISTING of adpatch
... ls -l of patches_PRE_1703_1_patchit11i.log to see date/time stamp
-rw-r--r-- 1 orafun dba 53761 Aug 30 14:41 /u10/orafun/appl/admin/FUN/log/patches_PRE_1703_1_patchit11i.log
... last 20 lines of log file: /u10/orafun/appl/admin/FUN/log/patches_PRE_1703_1_patchit11i.log
for details.
Purging timing information for prior sessions.
sqlplus -s APPS/***** @/u10/orafun/appl/ad/11.5.0/admin/sql/adtpurge.sql 10 1000
Done purging timing information for prior sessions.
AutoPatch is complete.
AutoPatch may have written informational messages to the file
/u10/orafun/appl/admin/FUN/log/patches_PRE_1703_1_patchit11i.lgi
Errors and warnings are listed in the log file
/u10/orafun/appl/admin/FUN/log/patches_PRE_1703_1_patchit11i.log
and in other log files in the same directory.
SUMMARY - patchit11i.sh - Completed application of patch: patches_PRE_1703_1, driver: driver=u_merged.drv
OK - adpatch completed successful.
INFO: Not starting patch alert monitor, to start: Login Engineer, User Admin, Update Profile
Redo the Action
Completed Successfully Post Hour Minute