[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::networker

Title:NetWorker
Notice:kits - 12-14, problem reporting - 41.*, basics 1-100
Moderator:DECWET::RANDALL.com::lenox
Created:Thu Oct 10 1996
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:750
Total number of notes:3361

536.0. "Probs. installing Networker 4.3 on Windows NT 4.0" by CSC32::L_DVORAK () Thu Mar 27 1997 14:35

Hi.

I have a customer who has been trying to install Networker 4.0 on an
AlphaServer 2000 running Windows NT 4.0.  He keeps getting the following
error:

  Procedure Entry Point WCSTOK couldn't be located in the dynamic link
  library NTDLL.DLL.

He started getting this error after deleting some files during the first
install.

We had him do the following:

- Verify that NTDLL.DLL is okay (checking it against one on a system
  he was able to install Networker on)
- Delete all refereces to Networker and NSR in registry
- Test Networker cd by installing it on another Alpha with no errors
- Perform Windows NT 4.0 update to replace any files that might be
  corrupt

Any ideas why he's getting this?  Also, can someone list all the Registry
keys that get created when Networker is installed on an NT system (both
4.2A and 4.3 on Windows NT 3.51 and 4.0).

Regards,

Lani Dvorak
Windows NT/Backoffice Support
Multivendor Customer Services
T.RTitleUserPersonal
Name
DateLines
536.1There's services, too. See .3DECWET::KOWALSKITime's not for savingThu Mar 27 1997 15:4220
I have a customer who has been trying to install Networker 4.0 on an
AlphaServer 2000 running Windows NT 4.0.  

>What is the NetWorker version they are installing?  (There is no 4.0)

 He keeps getting the following
error:

  Procedure Entry Point WCSTOK couldn't be located in the dynamic link
  library NTDLL.DLL.

>When is this error occuring? What is being run at the time?

keys that get created when Networker is installed on an NT system (both
4.2A and 4.3 on Windows NT 3.51 and 4.0).

>During running of SETUP, all keys are created under
>HKEY_LOCAL_MACHINE\Software\DigitalEquipmentCorporation\NetWorker
>There are other keys which are created but they are not created during
>installation.
536.2DECWET::KOWALSKITime's not for savingThu Mar 27 1997 15:515
In NetWorker V4.3 for Windows NT Alpha, there is no direct
reference in the product code to the C rtl function
wcstok().

Mark
536.3DECWET::KOWALSKITime's not for savingThu Mar 27 1997 15:545
During setup, there are service entries made in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

At runtime, per user entries are made in
HKEY_CURRENT_USER\Software\DigitalEquipmentCorporation\NetWorker
536.4CSC32::L_DVORAKThu Mar 27 1997 17:0912
Mark,

The customer is trying to install v4.3 (sorry about the typo).  I checked
with the customer and he said the error occurs when the setup files are 
getting copied (right after he runs setup.exe).  It completes 75% and returns 
the error.

Thanks for the registry info.

Regards,

Lani
536.5just a side questionDECWET::LENOXSoon we will all need two brains...Thu Mar 27 1997 17:123
it doesn't sound like the NT 4.0 system has any service
packs on it, true?
536.6DECWET::KOWALSKITime's not for savingThu Mar 27 1997 17:5010
    So, what exactly did you mean by "He started getting this error after
    deleting some files during the first install."?  NetWorker does NOT
    touch NTDLL.DLL (heaven forbid!), so I suspect that the customer has
    a non-standard system configuration.  Where did the customer get their
    NT kit (i.e., is it a 3rd party version of NT?)?  What SP's are
    installed?  There's a way to search a dll for the entry points; Lani,
    have you researched what dll this routine is supposed to be in?
    
    Mark
    
536.7CSC32::L_DVORAKFri Mar 28 1997 12:2213
The customer does not have any NT service packs installed.  I am the
3rd person to work on this call here and am not sure what files he was 
deleting.  I believe they were Networker 4.2A files.  I'm not sure
how to search a dll for entry points.  I searched both our internal
database and TechNet for WCSTOK and only found the article, Win32 Equivalents 
for C Run-Time Functions.

What installer is used to install Networker?  It looks like this is 
what is stumbling over the error.

Regards,

Lani
536.8DECWET::LENOXSoon we will all need two brains...Fri Mar 28 1997 12:578
It uses InstallShield3, but then if it they've messed up
something installshield needs, that will probably mess
up most product installations.  Since this customer has
installed this onto a different alpha (with no problem)
then at worst he may need to go through some type of disaster 
recovery to get back to a workable state, i.e. to the
point before the system became compromised.  Ick.  
536.9DECWET::KOWALSKITime's not for savingFri Mar 28 1997 13:3216
wcstok is in SYSTEM32\CRTDLL.DLL, the C run time library,
	also in system32\msvcrt20.dll
	also in system32\msvcrt40.dll
	also in system32\msvcrt.dll

It is NOT in NTDLL.DLL

They can check if it is there with

dumpbin /exports crtdll.dll | grep -i wcstok

dumpbin comes with msdev

I suspect they have non-standard software on the system.
Check whether msvcrt40.dll is around.
536.10CSC32::L_DVORAKFri Mar 28 1997 17:426
Thanks for the info.  I am going to have the customer try replacing
MSVCRT40.DLL.  The customer doesn't have MSDEV.

Regards,

Lani
536.11Starting to sound like the X FilesDECWET::KOWALSKITime's not for savingFri Mar 28 1997 21:0017
    
    Hmmm.  Although I don't have a kit handy-by at the moment, I'm
    pretty certain our 4.3 kit requires msvcrt40.dll and has it on it.
    However, if the customer's system HAD that dll on it already, it's
    possible that our kit would not overwrite it and would attempt to
    use the existing one.  If that dll was corrupted or non-standard,
    that would explain the problem.
    
    If the kit has this dll plainly available (ie, not in an "invisible",
    compressed state), the customer could cross-check their copy against
    the kit copy (date, size, etc).  Sorry, I'm not at the office right now
    so I can't give you more definitive info.
    
    There might be other factors at work here.  I would appreciate seeing
    a full directory listing of all DLLs in their system32 folder.
    
    Mark
536.12Update on solutionCSC32::L_DVORAKMon May 05 1997 15:508
Hi.

Just wanted to let everyone know that the customer fixed this
by updating Windows NT 4.0 on the Alpha. 

Regards,

Lani