XADM: Crash in Srvrmax.exe (RtlQueryInformationAcl) During Setup (152529)
The information in this article applies to:
- Microsoft Exchange Server 4.0
- Microsoft Exchange Server 5.0
This article was previously published under Q152529 SYMPTOMS
When you upgrade Microsoft Exchange Server 4.0 (Enterprise or Standard
edition) to Microsoft Exchange Server 4.0 Service Pack 4 or to Microsoft
Exchange Server 5.0, the process may terminate unexpectedly with an access
violation (Dr. Watson).
CAUSE
A call being made to retrieve the security descriptor on a key in the
registry is returning a NULL parameter. Setup does not handle a NULL
parameter being returned and access violates.
WORKAROUND
To work around this problem:
WARNING: Using the Registry Editor incorrectly can cause serious problems
that may require you to reinstall Windows NT. Microsoft cannot guarantee
that problems resulting from the incorrect use of Registry Editor can be
solved. Use Registry Editor at your own risk.
- Start Registry Editor (Regedt32.exe).
- Under the HKEY_LOCAL_MACHINE subtree, go to the following subkey:
System\CurrentControlSet\Services\EventLog\Application
- Starting with the first key under Application, select Permissions from
the Security menu. Make sure the Windows NT account being used as the
Microsoft Exchange service account is in the list and has FULL CONTROL
rights. Repeat this for each key down the list.
When you find a key that does not contain the service account in its
list, it is the key that is most likely causing the problem.
- Compare the name of this key with what is in the "Raw Stack Dump" of the
Drwtsn32.log. For example, in the sample log in the More Information
section of this article, the stack dump lists:
.......
0012d37c 00 00 00 00 49 00 6e 00 - 74 00 57 00 69 00 72 00
....I.n.t.W.i.r.
0012d38c 65 00 4d 00 73 00 67 00 - 53 00 65 00 72 00 76 00
e.M.s.g.S.e.r.v.
0012d39c 65 00 72 00 00 00 00 00 - 6f 00 6e 00 6e 00 65 00
e.r.....o.n.n.e.
0012d3ac 63 00 74 00 6f 00 72 00 - 00 00 65 00 63 00 74 00
c.t.o.r...e.c.t.
This points to the Integra Wireless Messaging Server Key (in the
registry as IntWireMsgServer) under:
HKEY_LOCAL_MACHINE\
System\CurrentControlSet\Services\EventLog\Application
- In the Permissions dialog box, click Add and select System as Full
Control and Creator Owner as Full Control and click OK. (It is also
possible to delete this particular key to resolve the problem; however, the
consequences must be fully known before proceeding with the deletion)
- Quit Registry Editor.
- Run Microsoft Exchange Server Setup again.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Exchange Server
version 4.0. This problem has been corrected in the latest U.S. Service
Pack for Microsoft Exchange Server version 4.0. For information on
obtaining the Service Pack, query on the following word in the Microsoft
Knowledge Base (without the spaces):
Microsoft has confirmed this to be a problem in Microsoft Exchange Server
version 5.0. This problem has been corrected in the latest U.S. Service
Pack for Microsoft Exchange Server version 5.0. For information on
obtaining the Service Pack, query on the following word in the Microsoft
Knowledge Base (without the spaces):
Modification Type: | Minor | Last Reviewed: | 4/28/2005 |
---|
Keywords: | kbbug kbfix kbusage KB152529 |
---|
|