Actually. I'd be surprised if this has anything to do with CC per se. This
error has some complex roots and the 'fix' depends on who or what causes it
and what user context is involved etc etc. However, don't be alarmed - the
error usually looks nastier than it is and typically doesn't indicate
anything wrong with the OS as such. The error message could be better
though...
Basically, I've seen this for the following: One of our services installed
on an NT server accepts incoming requests on a socket. As a response it logs
on the calling user and starts a server process for it and connects the
server and client together via sockets and then steps back for further
requests
Now, the client and server starts chatting (it's something like an X
functionality for our app). At some point the server spawns a shell to
perform some task - and this might go awry due to the desire of the shell to
have access to a desktop/windowstation combination (this concerns some OS
objects). I might be that the shell (or any other app) tries to get hold of
the default desktop/windowstation belonging to the logged on user - however,
due to security, NT denies this (you don't want just anyone to access and
play havov with your desktop while you're working or even start hooks to spy
on messaging activity between windows). So, this fails with this error.
Another scenario is that the logon activity forces the OS to assign a newly
created desktop/windowstation combination to every new logged on user.
However, those combos are a limited resource and when they're gone you'll
see the above error. Default settings usually gives you 12-14 logons before
this is used up. There are registry tweaks to change memory allocation
ratios to increase the available number.The solution for this typically only
applies if you have control over the code: what I did was to specifically
create a desktop/windowstation and explicitly assign all started process to
this given combo - thus all used one single combo and had all the necessary
access to it.
I suggest you search the MS Knowledgebase - you should be able to search on
'initialization failed' or other keywords in the error message for further
suggestions including registry tweaks. Available on the web or through MSDN
subscription if you have it available.
HTH
ken1
> -----Original Message-----
> From: Sharif.Malim@us.wmmercer.com
> [mailto:Sharif.Malim@us.wmmercer.com
> Sent: den 31 januari 2000 21:31
> To: cciug@Rational.Com
> Subject: [cciug] DLL initialization failed error
>
>
>
> Hi all,
>
> Has anyone see the following error on Windows NT 4.0 SP5
> server; Clearcase
> 3.2.1.
>
> DLL initialization failed
> Initialization of the dynamic link library
> c:\winnt\system32\KERNEL32.dll
> failed. The process is terminating abnormally.
>
> Does the fix for this problem require a reinstall of NT on the server?
>
> Any help is appreciated!
>
> Thanks,
> Sharif.
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
> can also
> unsubscribe
>
> http://clearcase.rational.com/cciug/mailing_list.html
>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:22:42 EDT