iChain abends in SSO.NLM when auto-posting a form with FormFill

When attempting to automatically post a form with iChain FormFill using the , the iChain server abends right after requesting the page.

Attempts to use also result in the same abend.

Removing the tag allows the page to be displayed with the appropriate form data filled in by iChain.

The form attempting to be filled is as follows:

The FormFill policy being used is as follows:

The HTML Form on the page is improperly formatted. Problems with the Form elements include the following:

Modifying the Form as follows prevents iChain from abending, and allows the FormFill processing to complete successfully.

New Form:

For more information on the proper formatting for HTML Form elements, see the latest HTML Specification available at: http://www.w3.org/

Details from the DEBUG.LOG file:

*********************************************************

Server ICS_SERVER halted Thursday, July 27, 2006 10:51:08.732 am
Abend 1 on P00: Server-5.60.05: Page Fault Processor Exception (Error code 00000000)

Registers:
CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0010 SS = 0010
EAX = 00000000 EBX = 3CD94904 ECX = 0000006E EDX = 8019E996
ESI = 8095C640 EDI = 8019EE72 EBP = 823C4D10 ESP = 823C4CF8
EIP = 81801F7E FLAGS = 00010282
81801F7E FF7004 PUSH dword ptr [EAX+04]=?
EIP in SSO.NLM at code start +00008F7Eh
Access Location: 0x00000004

The violation occurred while processing the following instruction:
81801F7E FF7004 PUSH dword ptr [EAX+04]
81801F81 8B4508 MOV EAX,[EBP+08]
81801F84 50 PUSH EAX
81801F85 E80D5B9C47 CALL LIBC.NLM|strcpy
81801F8A 83C408 ADD ESP,00000008
81801F8D 8B4508 MOV EAX,[EBP+08]
81801F90 803800 CMP [EAX],00
81801F93 7408 JZ 81801F9D
81801F95 8B4508 MOV EAX,[EBP+08]
81801F98 FF4508 INC dword ptr [EBP+08]

Running process: Server 44 Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: 823C4B3C
OS Stack limit: 823BD040
Scheduling priority: 67371008
Wait state: 5050030 Blocked on Semaphore
Stack: --00000000 ?
--00000000 ?
--00000000 ?
-8019EE72 (SSO.NLM|(Data Start)+2E72)
--8095C640 ?
--3CD94904 ?
--823C4D94 ?
81803EC8 (SSO.NLM|fillSilent+6E1)
--8259115C ?
--3CB9EA24 ?
--00000000 ?
--81E973A0 (JNET.NLM|psi_addressID+1558)
--00000000 ?
--00000246 ?
--823C4D98 ?
--823C4D50 ?
-801A1AE8 (SSO.NLM|enhancedProtectPassword+1C)
--823C4D58 ?
--822750A4 ?
--825910D8 ?
--3CB9EA24 ?
--822797F0 ?
--3CC69204 ?
--3CC693A4 ?
--3CB7EA04 ?
--00000000 ?
--3CB9EA24 ?
--3CC52BE4 ?
--3CB73DE4 ?
--00000002 ?
--00000000 ?
--00000000 ?
--00000000 ?
--3CB9EA24 ?
--822750A4 ?
--CD9C8F40 (NWUTIL.NLM|InternalIPXNetNumber+8294)
--82279D26 ?
--8095C640 ?
--3CD94904 ?
--823C4E70 ?
818037AE (SSO.NLM|fillHtml+E4C)
--3CC52BE4 ?
--3D0CDA04 ?
--3CF09E04 ?
--3CFA6EC4 ?
--8259114F ?
--822791F0 ?
--00000000 ?
--00000002 ?
--4D416F99 ?
806B3DAA (PROXY.NLM|FFMemoryFree+A)
--823C4E14 ?
--3CC438D1 ?
--8095C640 ?
--0000000D ?
CD996B6A (NWUTIL.NLM|NWUtilAlloc+1A)
--0000000D ?
--8095C760 ?
--00000000 ?
--3CC52BE4 ?
--00000000 ?
--000010CF ?
--00000000 ?
--822750A4 ?
--82279D25 ?
--00000000 ?
--825910D8 ?
--00000000 ?
--00000000 ?
--8095C640 ?
--3CD94904 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000002 ?
--3CF0DBE4 ?
--3CDE6988 ?
--3CF2CD84 ?
--3F0FA5E4 ?
--823C4E58 ?
81807937 (SSO.NLM|setValue+7D)
--FFFFFFFF (LOADER.EXE|KernelTempAliasesEnd+FFF)
--3CC438C4 ?
--3CF0E8E4 ?
--00000000 ?
--00000000 ?
--00000000 ?
--3CBEF964 ?
--00000000 ?
8180D5F9 (SSO.NLM|setUserAttributeValue+23)
--3CBEF964 ?
--4D416F99 ?
--8095C640 ?
--3CD94904 ?
--823C4EB8 ?
817FE34E (SSO.NLM|performActions+3A4)
--3CC52BE4 ?
--3D0CDA04 ?
--3CF09E04 ?
--3CFA6EC4 ?

Additional Information:
The CPU encountered a problem executing code in SSO.NLM. The problem may be in that module or in data passed to that module by a process owned by SERVER.NLM.

<<< BEGIN CUSTOM DATA >>>

EIP: 81801F7E (SSO.NLM|writeTag1+71)