There are a couple of things here.
First the application (or more specifically the Active X controls) is
looking for w3btrv7.dll specifically.
You mention that there is a wbtrv32.dll which is not the dll being
complained about as missing. I will guess that if one is there the
other is too though.
Does the path include the pvsw\bin folder. If it does and w3btrv7.dll
is not corrupt and there is enough memory to load it (and the other
requester dlls) all should be good. If I had to guess this is a Win9x
client machine that the path did not get updated properly or a Novell
login script overwrites the path at login.
Since the popup mentions ActiveX and w3btrv7.dll I am guessing that it
is returning the status 20 based on not being able to find or load the
dll as the w3btrv7.dll does not return a status 20. The current
version breaks it down into 3000 and 3100 status codes.
Leonard
On 5 Jan 2004 10:52:43 -0800, smm1014 (AT) yahoo (DOT) com (Sue Matlosz) wrote:
Quote:
Upon opening 32 bit app the following messages are received...
W3BTRV7.DLL could not be loaded. Active X may not work as expected.
Application then tries to open but a st20 is returned.
WBTRV32.DLL does reside in PVSW/BIN with correct file size of 42KB. |