Quote:

---

From: Kirk
Sent: Monday, November 28, 2005 8:39 PM
To: Kent Dyer; Ruud van Velsen
Subject: RE: odd issue with KiXtart

Here is a recap of events and my input since I worked with the local engineer to help resolve his issue.

Series of events:
1. The local engineer accidentally uninstalled DHCP (DNS was not an issue other than clients not able to obtain DHCP info which included DNS server IP's)
2. A temp DHCP scope was setup and clients retrieved addresses
3. A conflicting DHCP scope came online after the old server was rebooted that night, and I found scopes overlapping
4. I flushed all the DHCP leases on the overlapping scope and de-activated the scope. All clients refreshed there addresses with the original server

Another recent addition to this mix is that the server was recently upgraded to Windows 2003 SP1 as has every other site (hence the reboot that evening), but I thought I would note it. If I run either of these scripts on the DC itself at this remote site or from another server at that site or from any machine at my site (XP SP2) it works

\\server\netlogon\wkix32 \\server\netlogon\branch.kx
\\server\netlogon\kix32 \\server\netlogon\branch.kix

My guess is that it is something on the client side that coincided with the local engineer removing DHCP that same week as the only clients that cannot run this script from the DC are these clients. All the script does it map one drive, so there is not much to go on from the KiX side of things. A bat file works fine, hence the gpo work around.

-Kirk

---

Quote:

---

From: Ruud van Velsen
CC: Kirk
Sent: Tuesday, November 22, 2005 6:16 AM
To: Kent Dyer
Subject: RE: odd issue with KiXtart

Thanks for the update.

Actually, just now I noticed the Exception type: inpage error. This type of exception and possible causes are described in the manual:

Application error c0000006H / ‘IN_PAGE_ERROR’ / ‘SWAP_ERROR’ or an Invalid Page Fault is generated intermittently. The operating system has failed to read code from executable file(s) because the KiXtart startup drive has become unavailable. Make sure that you do not, in any way, disconnect or re-redirect the drive from which KIX32.EXE was started. Also, these faults can be caused by antivirus software. If you use antivirus software, make sure you are using the latest version and if the problem persists, test if disabling the antivirus software solves the problem.
Lastly, if you are using the Windows version of KiXtart (WKIX32.EXE) in a batchfile, please make sure to run it using the START command with the /W and /B options.

Basically, this error occurs if a process is started and when the Windows memory manager tries to read additional code from the executable file it suddenly finds the source (ie: the NETLOGON share containing WKIX32) to be inaccessible (or hideously slow).

The thing to investigate now is when/how/why the network connection is lost during the logonsequence. Best thing to do is get a network trace.

Note: in the past, a common cause for this exception were (bugs in) antivirus packages.

Hope this helps!

--Ruud

---