Page 1 of 1 1
Topic Options
#121230 - 2004-06-15 12:47 AM KIXTART produces an event ID 1789 in clients
Ringonz Offline
Lurker

Registered: 2004-06-15
Posts: 2
The description for Event ID ( 1789 ) 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. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: LookupAccountSid failed Error : The trust relationship between this workstation and the primary domain failed. (0x6fd/1789).

It seems to happen when people log in, only found on Windows XP machines as Win9x has no event viewer.

Cheers for your help.

Top
#121231 - 2004-06-15 09:24 AM Re: KIXTART produces an event ID 1789 in clients
robp Offline
Lurker

Registered: 2004-06-15
Posts: 3
Loc: Dunedin, New Zealand
Sounds like I'm having the same problem, on w2k TS and XP, I have tried rejoining one of the computers to the domain, but it still has the problem. Our logon script works with 3.62 of Kixtart with these Event errors, but after upgrading to 4.22 INGROUP fails, so we're still on 3.62 with the Event errors. It is a Microsoft problem I believe!

We also get Event ID: 15 "AutoEnrollment" errors in our XP client event logs. MS KB indicates it could be related to DNS, perhaps!

Note We have 2 historical issues that may be the root cause: 1: Our DNS server used to be on our Linux server, and was not moved until after upgrade to W2k. 2: Our NT4 Domain name was PSS and the server was upgraded to w2k using the zone name pso.org.nz. After moving the DNS to the w2k server several changes had to be made to the DNS to add "PSS" to the forward lookup zones (I think). I only want a bleedin file server not all this agro with huge consultant expenses! (yes I've used MS experts) Anything sound familiar?


Edited by robp (2004-06-15 09:28 AM)

Top
#121232 - 2004-06-15 03:13 PM Re: KIXTART produces an event ID 1789 in clients
Lonkero Administrator Offline
KiX Master Guru
*****

Registered: 2001-06-05
Posts: 22346
Loc: OK
as a start, MS can't help you.
they have never even got their own docs approved by themselfes, how could they know what their softs do then?
_________________________
!

download KiXnet

Top
#121233 - 2004-06-17 04:25 AM Re: KIXTART produces an event ID 1789 in clients
Ringonz Offline
Lurker

Registered: 2004-06-15
Posts: 2
So I guess we have to put up with the error until someone gives in and finds a way around the problem????
Top
#121234 - 2004-06-17 06:39 AM Re: KIXTART produces an event ID 1789 in clients
jpeachman Offline
Fresh Scripter

Registered: 2002-11-18
Posts: 39
The error message pretty much sums it up: the action LookupAccountSid failed with an error code of 1789. The Microsoft Knowledgebase article 262958-Lookup of Permissions on ACLs Shows Only SIDs explains the problem, and the resolution.

Joe

Top
#121235 - 2004-06-17 07:41 AM Re: KIXTART produces an event ID 1789 in clients
Lonkero Administrator Offline
KiX Master Guru
*****

Registered: 2001-06-05
Posts: 22346
Loc: OK
oh...
so, it's just hand made tightened security tweak thingie...
_________________________
!

download KiXnet

Top
#121236 - 2004-06-17 08:43 AM Re: KIXTART produces an event ID 1789 in clients
Kdyer Offline
KiX Supporter
*****

Registered: 2001-01-03
Posts: 6241
Loc: Tigard, OR
Here is an interesting page that lists this error on it as well - View All Error Codes

Kent

_________________________
Utilize these resources:
UDFs (Full List)
KiXtart FAQ & How to's

Top
#121237 - 2004-07-06 02:22 AM Re: KIXTART produces an event ID 1789 in clients
robp Offline
Lurker

Registered: 2004-06-15
Posts: 3
Loc: Dunedin, New Zealand
Thanks jpeachman! The solution to my problem was related to the Windows 2000 server config. I had the following Event Errors: 15, 534, 1000, 1053, 1789. Microsoft KB 262958 resolved them and the InGroup problem for me. I had actually printed this KB article off for our local computer shop for when they visited to look at the problem, but they went off on some other unsuccessful tangent. So I fixed it myself, what a waste of money on consultants! .... but I still don't know who, what or where the fault came from!
Top
Page 1 of 1 1


Moderator:  Jochen, Allen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Arend_, Mart 
Hop to:
Shout Box

Who's Online
0 registered and 628 anonymous users online.
Newest Members
Raoul, Timothy, Jojo67, MaikSimon, kvn317
17875 Registered Users

Generated in 0.062 seconds in which 0.026 seconds were spent on a total of 12 queries. Zlib compression enabled.

Search the board with:
superb Board Search
or try with google:
Google
Web kixtart.org