#42673 - 2003-07-09 08:03 PM
Failed to Set DACL Returns
|
Darvin
Lurker
Registered: 2003-07-09
Posts: 1
Loc: Dallas Texas
|
I'm working with a customer that has two NT 4.0 SP/6a DC's. If they get validated by the BDC the Kixtart script runs and maps the drives to both of their file servers with no error. If they get validated by the PDC then the drive mapping works but the mapping to the other file server fails with an event ID of 0 and an error that it failed to set the DACL. If you map the drive with a NET USE from the client you can map with no problem. Have had them upgrade to version 4.21 but it still fails. Does anyone know what the cause of the error is or what the workaround was that is part of the 4.02 upgrade where this problem was first resolved ?
Thanks!
|
|
Top
|
|
|
|
#42676 - 2003-07-10 04:07 PM
Re: Failed to Set DACL Returns
|
cyeranojones
Lurker
Registered: 2003-07-10
Posts: 4
Loc: Toronto
|
Eurekaa!!!! This morning we have the answer to our woes.
The PDC had KIX version 4.1 which is a our DC and didn't give the drive mappings to users. On the BDC we had KIX version 3.62 and that's the DC which gave the drive mappings without a problem. When we upgraded both DCs KIX to version 4.21 none of the DCs gave the drive mappings per Microsoft's Technical Experts, the new version of KIX didn't work and made matters worse. Then this morning we downgraded KIX on both DCs to version 3.62 things went beautifully and users now are getting their drive mappings, Yippeee Kiyahhhhh Cowboy!.
My explanation for this: the Microsoft security patches which we implemented over the last weekend had some dependancy that KIX 4 and higher is sensitive too. Causing a conflict with newer versions of KIX. We will stay with Kix Version 3.62 for now? As to a fix for 4 and higher that's a question for Microsoft to answer. "Deploy and cross your fingers guys" [ 10. July 2003, 16:22: Message edited by: cyeranojones ]
|
|
Top
|
|
|
|
#42678 - 2003-07-10 04:25 PM
Re: Failed to Set DACL Returns
|
cyeranojones
Lurker
Registered: 2003-07-10
Posts: 4
Loc: Toronto
|
Hi Shawn,
Microsoft has a complete dump of all DC's, logs, conifg's. It is up to them now, we have all patches up to todate except yesterdays announcement.
All NT 4.0 SP6a patch before July 5.
Cyerano
|
|
Top
|
|
|
|
#42680 - 2003-07-10 07:25 PM
Re: Failed to Set DACL Returns
|
cyeranojones
Lurker
Registered: 2003-07-10
Posts: 4
Loc: Toronto
|
I would recommend they look at MS01-048. In conjunction with 4.0.1 and 4.2.1.
|
|
Top
|
|
|
|
#42681 - 2003-07-14 01:20 PM
Re: Failed to Set DACL Returns
|
Ruud van Velsen
Developer
   
Registered: 1999-05-06
Posts: 391
Loc: Amsterdam, The Netherlands
|
In order to investigate the issue, I'd really need detailed information on the complete configuration (client OS, KXRPC service version, events logged on client, events logged on server, runtime errors (@ERROR), batchfiles used, scripts used, etc).
As for MS01-48: this is a very old (september 2001) fix, so I assume you installed this long ago, and not just this weekend?
Regards,
Ruud
|
|
Top
|
|
|
|
#42682 - 2003-07-14 10:49 PM
Re: Failed to Set DACL Returns
|
cyeranojones
Lurker
Registered: 2003-07-10
Posts: 4
Loc: Toronto
|
MS has all the data you asked about. We are awaiting an answer. I will keep everyone posted.
|
|
Top
|
|
|
|
Moderator: Jochen, Allen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Arend_, Mart
|
1 registered
(mole)
and 1300 anonymous users online.
|
|
|