|
|
|||||||
When I browse Shared Folders/Open Files on the domain controller, I see lots of users that have not released kix32.exe. About half of users in the office. Cannot figure out why. All users are running same OS (Windows 7) and same script - there is only one script for the entire office. THANKS |
||||||||
|
|
|||||||
This issue has been brought up before, but with no resolution. See: http://www.kixtart.org/forums/ubbthreads...true#Post199807 |
||||||||
|
|
|||||||
Thank you; appreciate the link as I did not find any posts after trying several searches. |
||||||||
|
|
|||||||
If you find anything please post back. |
||||||||
|
|
|||||||
I've been doing a little eyeball research on this. It appears this is only happening with Window 7 64bit clients. I've seen the kix32.exe file listed in the open files on both Server 2003 DC, and Server 2008 DC, with kix32.exe versions 4.53 and 4.61. Here are my results so far: I have access to Vista x32 with Server 2003, but it will be a week or so before I can test it. If anyone has the other environments, please post your results. |
||||||||
|
|
|||||||
We have the same problem since months. The problem is with Startup-/Logon-Scripts from GPO and Logon-Script for Users. For our students we habe about 300 Win7-64vit PCs, which only use the Startup-Script ( cmd ) which started a KIX-Script. Every mornning we have some PCs which have kix32 opened every time, and othe PCs chaning each day. But its not a KIXtart-Problem. It must be something like timing or so. For testing I create a special Script: %0\..\EVENTC /T success /SO poolstest /ID 99 /L application /D "pingtesta" > nul: ping 127.0.0.1 -n 2 -w 1000 > nul %0\..\pingtest.exe 127.0.0.1 -n 18 -w 1000> nul %0\..\EVENTC /T success /SO poolstest /ID 99 /L application /D "pingteste" > nul: eventc is a copy of eventcreate; pingtest.exe a copy of Win7-ping.exe. With pingtest you got a sleep/wait time of n seconds. If n gt 15 or so all the 300 pcs has testping opened. Between 1 an 10 seconds only a few pcs has kix32 opend. I looked for settings and special GPOs but unitl now; no solution. For a workaround I changed the startup-script: \\naf2.uni-trier.de\domaincomputers\netlogon\kix32.exe \\naf2.uni-trier.de\domaincomputers\netlogon\updates\pools.kix And now only one pc has the trouble !!!!! NAF2 is not a windows server; is a Netapp-Filer!!!! |
||||||||
|
|
|||||||
A little more info. The kix32.exe process does not show up in the process list on the computer that is holding the file open on the server. One office that I checked on the other day, had a number of kix32s open, but now has none. The only thing that has changed is the installation of SP1. Maybe its fixed now. I'll try to do some more confirmation myself, but if anyone else can confirm this, it would be helpful. |
||||||||
|
|
|||||||
I found something new. On 2 DCs I disabled SMB2. Now no open kix32.exe where found. Can this a problem with sm2 function durable_handle? But I didn't find a Reg-Key to disable only this function. |
||||||||
|
|
|||||||
I'm still seeing this problem too. I'm moving this thread to beta so it's more likely Ruud will see it. |
||||||||
|
|
|||||||
Hi, Has anyone tried any of the following Server 2008 hotfixes? http://support.microsoft.com/kb/2473205 http://support.microsoft.com/kb/2625434 looks like it might be particularly relevant... |
||||||||
|
|
|||||||
I've not applied any myself. I run a few server 2008 R2 boxes but for applications - not user access stuff and so far I'm not having any of these issues. |
||||||||
|
|
|||||||
but it wasn't a w2k8R2 issue. it seems by the data given thus far that the problem is windows 7. and 64bit specifically. |
||||||||
|
|
|||||||
This should solve the problem. |
||||||||
|
|
|||||||
Aha! No wonder I can't replicate this issue. The first thing I do at any client is set DelayedDesktopSwitchTimeout to zero on every system at build or deploy time. I do it just because it is annoying as all getout! Glenn |
||||||||
|
|
|||||||
Originally Posted By: Arend_ This should solve the problem. Curious why this would fix it... this doesn't happen on 32bit clients... and only Win 7 x64... I'm willing to give it a try to see though. |
||||||||
|
|
|||||||
Well I only have a few and have not noticed the issue and I've not manually made the change either. Just haven't seen the issue yet. |
||||||||
|
|
|||||||
I haven't had the energy to rebuild my lab on this continent so I can't test the behavior either |
||||||||
|
|
|||||||
Hi, after more testing. I found that starting from our Netapp-Filer the problem was gone. On the filer the option: cifs.smb2.durable_handle.enable was disabled. After disabling smb2 on DCs kix32.exe also not opened. From a german AD maillinglist i got the answer to test the following registry key: HKLM\System\CCS\Services\LanmanServer\Parameters Type: REG_DWORD Name: DisableLeasing Value: 1 After setting this key on all DCs tomorrow only 3 PCs ( from 300 ) holds kix32 open. |
||||||||
|
|
|||||||
Originally Posted By: Klaus-Dieter Meyer After setting this key on all DCs tomorrow only 3 PCs ( from 300 ) holds kix32 open. |
||||||||
|
|
|||||||
lol |
||||||||
|
|
|||||||
This is definitely not an intrinsic KiXtart issue. As apparently disabling SMB2 resolves the issue, it seems it is related to that. I'll do some research to see if I can find any issues like this. Regards, Ruud |
||||||||
|
|
|||||||
Just found a report in one of our databases that sounds suspiciously similar. It is an SMB2-specific issue, and can leave file handles open indefinitely. The issue is scheduled to be addressed in Windows 8. Ruud |
||||||||
|
|
|||||||
Thanks for all the updates Ruud! |