Installing exchange 5.5 sp4 fails

[mike at jurney.org]

Hello,
  I've been poking at this problem for a couple of days, and I've narrowed
the focus on what's going wrong to this:

Exchange 5.5 SP4 install gets most of the way through, but generates a Dr.
Watson near the end exactly the same problem as reported here:

http://lists.samba.org/archive/samba/2003-November/001828.html

Running an ethereal trace, I see this conversation at the time of the
crash:


exchange -> pdc:	NT Create AndX Request, Path: \samr
pdc -> exchange:	NT Create AndX Response, FID: 0x7499
exchange -> pdc:	Bind: call_id: 143 UUID: SAMR
pdc -> exchange:	Bind_ack: call_id: 143 accept max_xmit: 4280 max_recv: 4280
exchange -> pdc:	SamrEnumerateAliasesInDomain request[Malformed Packet]
pdc -> exchange:	Fault: call_id: 145 ctx_id: 0 status: nca_s_fault_context_mismatch
exchange -> pdc:	Close Request, FID: 0x7499
pdc -> exchange:	Close Response

The Exchange SP4 installer seems to be handling the fault response
incorrectly.  This exchange is what occurs when the installation fails.
It looks as though the call_id gets incremented by two, which seems to be
unique to this conversation.  This is the only failure I've seen, though,
so I don't know if that's normal.  I do know that in all successful
conversations the call_id is the same in both the request and the reply.

On the samba side:

[2004/02/20 17:28:33, 4] rpc_server/srv_pipe.c:api_rpcTNP(1502)
  api_rpcTNP: samr op 0xf - api_rpcTNP: rpc command: SAMR_ENUM_DOM_ALIASES
[2004/02/20 17:28:33, 6] rpc_server/srv_pipe.c:api_rpcTNP(1527)
  api_rpc_cmds[6].fn == 0x8118440
[2004/02/20 17:28:33, 5] rpc_parse/parse_prs.c:prs_debug(82)
  000000 samr_io_q_enum_dom_aliases
[2004/02/20 17:28:33, 6] rpc_parse/parse_prs.c:prs_debug(82)
      000000 smb_io_pol_hnd pol
[2004/02/20 17:28:33, 5] rpc_parse/parse_prs.c:prs_uint32(635)
          0000 data1: 00000000
[2004/02/20 17:28:33, 5] rpc_parse/parse_prs.c:prs_uint32(635)
          0004 data2: 00000010
[2004/02/20 17:28:33, 5] rpc_parse/parse_prs.c:prs_uint16(606)
          0008 data3: 0000
[2004/02/20 17:28:33, 5] rpc_parse/parse_prs.c:prs_uint16(606)
          000a data4: 0000
[2004/02/20 17:28:33, 5] rpc_parse/parse_prs.c:prs_uint8s(722)
          000c data5: 0d 82 36 40 93 53 00 00
[2004/02/20 17:28:33, 5] rpc_parse/parse_prs.c:prs_uint32(635)
      0014 start_idx: 00000000
[2004/02/20 17:28:33, 5] rpc_parse/parse_prs.c:prs_uint32(635)
      0018 max_size : 0000ffff
[2004/02/20 17:28:33, 4]
rpc_server/srv_lsa_hnd.c:find_policy_by_hnd_internal(170)
  Policy not found: [000] 00 00 00 00 10 00 00 00  00 00 00 00 0D 82 36 40
........ ......6@
  [010] 93 53 00 00                                       .S..
[2004/02/20 17:28:33, 5] rpc_parse/parse_prs.c:prs_debug(82)
  000000 samr_io_r_enum_dom_aliases
[2004/02/20 17:28:33, 5] rpc_parse/parse_prs.c:prs_uint32(635)
      0000 next_idx    : 00000000
[2004/02/20 17:28:33, 5] rpc_parse/parse_prs.c:prs_uint32(635)
      0004 ptr_entries1: 00000000
[2004/02/20 17:28:33, 5] rpc_parse/parse_prs.c:prs_uint32(635)
      0008 num_entries4: 00000000
[2004/02/20 17:28:33, 5] rpc_parse/parse_prs.c:prs_ntstatus(664)
      000c status: NT_STATUS_INVALID_HANDLE
[2004/02/20 17:28:33, 4] rpc_server/srv_pipe.c:api_rpcTNP(1537)
  api_rpcTNP: bad handle fault return.



I havn't been able to figure out why this is dying, but I'm not very
familiar with the code or the DCERPC protocol.  Does anyone have any
suggestions as to things I can try to fix this?

-- 
Michael D. Jurney
mike at jurney.org