I've come to my wits end trying to deduce the reason for the 1332 Kixtart errors we've been seeing.

code:
1332 Kixtart 
Event Type:	Error
Event Source:	KIXTART
Event Category:	None
Event ID:	1332
Date:		4/29/2003
Time:		10:21:40 PM
User:		N/A
Computer:	<ComputerName>
Description:
The description for Event ID ( 1332 ) in Source ( KIXTART ) cannot be 
found. The local computer may not have the necessary registry information
or message DLL files to display messages from a remote computer. The 
following information is part of the event:  [B]Failed to resolve SID(s) Error : No 
mapping between account names and security IDs was done. (0x534/1332)[/B] .
These errors appear consistently in application logs on all NT/2k/XP PC's when processing logon scripts.

The problem is related to the use of the Ingroup command and Kix32 v4.20. If we comment out the Ingroup command, or use an older version of kix32, the errors are not produced. Yet all Ingroup calls appear to be using the correct syntax and are processed correctly.

We have installed and are running the v4.20 kxrpc service on all DCs to no avail. We've implemented the kixtart.ini in both the netlogon share or where kix32 is called from, the kxrpc registry key, set variable, etc. and have use the /r=lei etc. switches to direct the client to the kxrpc services but none of these changes eliminate the error.

I've seen some mention about the ability to suppress this error, but I have't been able to find any specifics on this. None of the other posts regarding 1332 errors really address the issue either.

The power in using Kixtart has always been its ability to process scripts based on group membership. Is this a unique situation or doesn't anyone else use the ingroup command???

Any assistance would be appreciated!

[ 05. May 2003, 18:23: Message edited by: chelget ]