#21172 - 2002-05-03 07:24 PM
Failed to Locate KX16.dll ...
|
shogazu
Lurker
Registered: 2002-05-03
Posts: 2
Loc: New Brunswick, Canada
|
Version 4.02
I copy Kix32.exe, KX16.dll, and KX32.dll to C:\Windows
directory on Windows 95 machines. "C:\windows" is in path statement and is %windir% environment variable. Run kix32.exe from command line in c:\windows and I get the error "Failed to locate KX16.dll..."
When I replace Kix32.exe, KX16.dll, KX32.dll with
verison 4.10b1 files error does not happen.
Am trying to upgrade Kix version in our environment to 4.02 or latest when available.
NT machines seem to be OK. I thought copying these files into the %windir% was all that is required...and beta version works??
I would like to get the 4.02 version to work ...any ideas would be appreciated. Is it just my 95 machines? anything in registry?
Thanks
Harry
|
|
Top
|
|
|
|
|
#21173 - 2002-05-03 08:26 PM
Re: Failed to Locate KX16.dll ...
|
BrianTX
Korg Regular
Registered: 2002-04-01
Posts: 895
|
The only thing I can think of is to check your drives for multiple versions of the kix files. Also, make sure the netlogon version is the same as on the PC.
Brian
|
|
Top
|
|
|
|
|
#21174 - 2002-05-04 12:01 AM
Re: Failed to Locate KX16.dll ...
|
Kdyer
KiX Supporter
Registered: 2001-01-03
Posts: 6241
Loc: Tigard, OR
|
shogazu,
Welcome to the board!
Have you applied the DLLs, EXEs to your DCs all from the same Archive? In the past, this has been a problem that when an upgrade is done, the files are not all migrated.
HTH,
- Kent
[ 04 May 2002, 00:01: Message edited by: kdyer ]
|
|
Top
|
|
|
|
#21175 - 2002-05-21 11:17 AM
Re: Failed to Locate KX16.dll ...
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Dear,
Our ideas of possible problems:
- different version of kixtart binairies installed on your client.
please run our script version.kix from root "c:\" to find
the actual versions installed on your client. - we are trying to update the kixtart binaries with actual kixtart version,
which will result in "share violation" sitation and not all files are
updated. by installation of kixtart on clients we are using a prepared
iexpress package which is using his own kixtart binaries for installa-
tion. the installation/update process by calling package will be done
from a BATch file and not from inside a kixtart script.
(see next paragraph about "how to installed kixtart") - system can't installed kixtart binairies in a correct way because
users doesn't have enough right. try to verify those systems with an
user with enough rights.
An easy way of installing kixtart on your clients is by using our iexpress
packages. There are different versions for different Kixtart releases.
At the moment there are five releases:
- kix362update.exe
- kix363update.exe
- kix400update.exe
- kix401update.exe
- kix402update.exe
- kix410update.exe
Each time it will verify the correctness of your release. Incorrect
files will be replaced and missing files will be added. Regardless of
file attributes.
To prevent running more times weare using a control files.
You can easily upgrade it with our iexpress package.
Questions: how?
A way of installing/updating kixtart of your clients: with only one additional statement
For the installation of kixtart at your local workstation we see many version of doing it.
Most statements in your BATch file are using for this duty.
But there is also a way of doing it with a single statement, which doesn't only copy
the required files, but also compare file version information. After completion a logfile
will be created at your local workstation.
Another way of installing/updating kixtart on your clients:
For installing or updating of your clients you can download our packages kix363update.exe,
kix400update.exe or kix401update.exe from our site http:\\home.wanadoo.nl\scripting.
Possible calls in your logon procedure can be:
As first line of your logon procedure you can use one of following formats:
- x:\kixtart\kix402update.exe /q
- %0\..\kix402update.exe /q
- if not exist c:\kix402.ok %0\..\kix402update.exe /q
- \\server\NETLOGON\kix402update.exe /q
Second line can be something like:
- kix32 %0\..\your_script.kix
- kix32 \\server\netlogon\your_script.kix
Results of your BATCH can be:
for network environments (= update package will transfer during each logging on)code:
@echo off
%0\..\kix402update.exe /q
kix32 %0\..\your_script.kix
@echo off
or for dial-up environments (= update package will transfer only once)
code:
@echo off
if not exist c:\kix402.ok %0\..\kix402update.exe /q
kix32 %0\..\your_script.kix
@echo off
After using above programs there will be created a control
file c:\kix363.ok, c:\kix400.ok, c:\kix401.ok, c:\kix401.ok or
c:\kix402.ok. So it isn't necessary to run the installation
process again, but we advise to update (or better: verify)
kixtart files always.
Reason: a security leak for running kixtart from clients.
remarks: SECURITY LEAK for running kixtart from clients
running kix32.exe from a local workstation can have also unwanted effects. An user
can modify or replace your kix32.exe file. f.e. not to run your script but for
reading your script.
For RAS users it is interesting not to download each time the kixtart required files,
but for other users we advise:
always check the kixtart files and update them when necessary before running your KIX scripts.
FIX for SECURITY LEAK:
In our case the first statement of our default logon procedure for network users is always:
%0\..\kix363update.exe /q
and it will guarantee that kix32.exe file will always the correct one.
remarks: performance
- only 150 KBytes will be transfered to your workstation. the package has been compressed.
- always the correct set of kixtart files will be used. during the execution of scripts
the user can already starts working. - during installation or updating kixtart you will not get share violation error or busy file
error. the install.kix scripts runs with his own kixtart version. - for RAS users we create additional authorizations which will run minimum set of script code.
for them the logon procedure containts as statement:
if not exist c:\kix363.ok %0\..\kix363update.exe /q
greetings.
btw: related kixtart topic http://kixtart.org/board/Forum2/HTML/000583.html
btw: be sure no other kix32.exe and DLLs are active on your clients.
|
|
Top
|
|
|
|
#21176 - 2002-05-21 04:34 PM
Re: Failed to Locate KX16.dll ...
|
shogazu
Lurker
Registered: 2002-05-03
Posts: 2
Loc: New Brunswick, Canada
|
BrianTX, kdyer, MCA
Thanks for the help! Older version of dlls found in other directory of some machines seems to be
causing the issue. I greatly appreciate your responses.
Harry
[ 21 May 2002, 16:35: Message edited by: shogazu ]
|
|
Top
|
|
|
|
|
#21177 - 2002-07-02 10:18 PM
Re: Failed to Locate KX16.dll ...
|
MCA
KiX Supporter
Registered: 2000-04-28
Posts: 5152
Loc: Netherlands, EU
|
Dear,
All our iexpress package for updating your clients has been updated.
Issues
- we create the check file also in %windir% directory.
this check file kix???.ok.
the problem was that in some situations the file c:\kix???.ok couldn't
be created. for backwards compatibility we create - try to create - two check
files
- c:\kix???.ok
- %windir%\kix???.ok
btw: we are using "HKLM\Software\Microsoft\Windows\CurrentVersion\Run\Windir" value.
- during the creation of file associations with kix32 we aren't using
the external kixedit.reg file. it is using internal kixtart func-
tions.
- to prevent also problems with the installation of c:\kixedit.ico file,
we move it also to the %windir% directory.
- the control-file is restyled and as kixtart users you can easily read
information from it.
an example:
code:
[KiXtart]
kix32.exe=2002/06/18 20:19:09 -> 2002/05/29 16:59:06 225280 (build 095)
kx16.dll=2002/06/18 20:19:09 -> 2001/08/27 20:17:29 47104
kx32.dll=2002/06/18 20:19:09 -> 2002/03/29 12:38:08 49152
kx95.dll=2002/06/18 20:19:09 -> 2001/11/19 05:00:00 49152
KiXtart=installation completed at 2002/06/18 20:19:09 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
KiXtart release=ME -> kix 4.10 Release Candidate 2
KiXtart mode=registry
btw: the old format was
code:
[Kixtart ME]
kix32.exe 4.10 Beta 1=2002/05/01 17:04:13 -> 2002/04/03 00:00:00 221184 (build 084)
kx16.dll 4.10 Beta 1=2002/05/01 17:04:13 -> 2001/08/27 00:00:00 47104
kx32.dll 4.10 Beta 1=2002/05/01 17:04:13 -> 2002/03/29 00:00:00 49152
kx95.dll 4.10 Beta 1=2002/05/01 17:04:13 -> 2001/11/19 00:00:00 49152
Kixtart 4.10 Beta 1=installation completed at 2002/05/01 17:04:13 (+kix32.exe +kx16.dll +kx32.dll +kx95.dll) to "c:\windows\"
Kixtart 4.10 Beta 1 mode=registry
- we have rename the debugging file from "c:\kixtart.log" to "%tmp%\kixtart.txt".
btw: this file will created when environment variable "kix-debug" exist.
btw: by problem you should mail also this file to us.
an example of it
tuesday 2002/06/18 20:19:09- kixtart 4.10 Release Candidate 2/3.03e script starting.
-
-curdir: c:\windows\temp\ixp000.tmp
-scriptdir: c:\windows\temp\ixp000.tmp
-scriptname: start2.kix
-startdir: c:\windows\temp\ixp000.tmp
-
-userid: -/-
-user priv: guest
-version: inwin=2/dos=4.90/productsuite=/producttype=Windows Me/csd=
-
- start-20:19:09- 0 The operation completed successfully.
- 1-20:19:09- 0 The operation completed successfully.
- 2-20:19:09- 0 The operation completed successfully.
- 3-20:19:09- 0 The operation completed successfully.
- 426-20:19:10- 6 The handle is invalid.
- end-20:19:10- 6 The handle is invalid.
-
-tuesday 2002/06/18 20:19:10- kixtart 4.10 Beta 1/3.03e script ending.
-
-Intel Pentium III (0 Mhz, memory 511 MB)
-
Still the special environment variable exist
- kix-debug
it creates a logfile in your temporary directory. name is %tmp%\kixtart.txt. - kix-show
it shows information about installation progress by some MessageBox's.
Your logon BATch file can be something like:
code:
@echo off
%0\..\kix410update.exe /q
kix32 %\..\your_script.kix
@echo
or
code:
@echo off
%0\..\kixcheck.exe
if errorlevel 1 %0\..\kix410update.exe /q
kix32 \\server\netlogon\your_script.kix
@echo off
or
code:
@echo off
if not exist %windir%\kix410.ok %0\..\kix410update.exe /q
if not exist %windir%\kix410.ok goto net
kix32 \\server\netlogon\your_script.kix
goto end
:net
\\server\netlogon\kix32 \\server\netlogon\your_script.kix
:end
@echo off
We were using our tool kixcheck in above logon BATch files
which return an errorlevel 1 when kixtart binaries aren't installed
in a correct way.
The output of "kixcheck" is:
- for a correct installation:
code:
KixCheck 1.05 (c) scripting@wanadoo.nl 2001
Found as C:\WINDOWS\KIX32.EXE (29-05-2002 16:59:12 225280 bytes)
+ C:\WINDOWS\KX16.DLL (27-08-2001 20:17:58 47104 bytes)
+ C:\WINDOWS\KX32.DLL (29-03-2002 12:38:16 49152 bytes)
+ C:\WINDOWS\KX95.DLL (19-11-2001 05:00:00 49152 bytes)
path c:\windows;c:\windows\command
KiXtart environment: complete.
- for an incomplete the output look like:
code:
KixCheck 1.05 (c) scripting@wanadoo.nl 2001
Found as C:\WINDOWS\KIX32.EXE (29-05-2002 16:59:12 225280 bytes)
+ C:\WINDOWS\KX16.DLL (27-08-2001 20:17:58 47104 bytes)
+ C:\WINDOWS\KX32.DLL (29-03-2002 12:38:16 49152 bytes)
path c:\windows;c:\windows\command
KiXtart environment: incomplete. remove "c:\kix*.ok" files.
by problems: please run above iexpress installation with defined
environment variable kix-debug and return the output of
file %tmp%\kixtart.txt.
greetings.
btw: you shouldn't look for %systemroot% but for %windir%
environment.
|
|
Top
|
|
|
|
Moderator: Jochen, Allen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Arend_, Mart
|
0 registered
and 837 anonymous users online.
|
|
|
