pathwork problem

[Rupert_1]

W2K workstation, when click and drag small files from Openvms server, it copy successfully.
But the file is big (120000 block), it fails with this error message.
connection attempt denied, failed to authenticate a license.
W2K was upgraded from Win98 2 months ago.
License issue ?

[Antoniov.]

Hi,
license problem is not simple to solve ...
on server, with SYSTEM account
$ ADMIN/LICENSE
(this work only with PW V6 or V7)
now type F10 + G (Group license)
and see if your system is client based or server based.

For client based
type F10 + C (Client)
and you can see client licensed (could be SINGAPOR-JGRZV8);
If you don't see license, acquire it running on PC W2K the commmand PNLR32

For server base
you could see any unit avaiable.

Please report the result for furthermore help.

Antonio Vigliotti

[Ian Miller.]

It's curious that increase in filesize leads to licence problem but pwrks is a strange thing :-)

You could run SYS$SYSTEM:PWRK$LR_SHOW_USAGE.EXE
to see what licences you have.

[Rupert_1]

license.bmp

[Rupert_1]

licensesSnap

[Antoniov.]

Hi,
after seen your bmp I understand:
a) You have license for 3 PCs
b) 1 license (CA07.03) is configurated as server mode
c) 2 licenses (CA06.00) are old and they are client mode;
d) You have also WINAT07.01 unused for shared resourse.
e) License server base is alreday in use (your PC?)
f) Client base license (CA07.03) are avaiable for some PC (not yours in use)

For keeping a stable sharing it's better configure your PC as client of license.
On PC:
- Right click on my network
- Click on Property
If you don't see Pathwork license agent(Lan manager) then
-- Click on [Add]
-- Click on [Service]
-- Select Dec or Compaq
-- Select Pathwork license agent
-- Reboot PC
After you have installed License agent or else if you have already in MyNetwork:
- Click on [Start]
- Click on [Run program]
- Type PNLCFG
Now you see a window with client license manager; on right box you need a PWLMDOSCC06.00 license, if not add this on. Click on [OK] and wait for few secons when PC syncronize license with server.
After this configuration, your PC has 1 exclusive license to access on server sharing and you could not meet any other trouble.

Antonio Vigliotti

[Willem Grooters]

Though I'm not familiar with Pathworks/AdvancedServer, just some shots.

I guess:

pwlmxxxca06.00 is a pathworks 6 license
pwlmxxxca07.03 is a pathworks7 (advanced server) license

Does this work? AFAIK, you can have either Pathwork6 OR AS - and accompanied licences.

Some earlier message in this forum suggested that you may have more than one connection open if you have printer access AND share-access. What about License management, will that count for one session?

Still, it's weird that you get a message based on fileSIZE....Or there is a limitation within your license that allow only transfer upto a certain size.

Willem

[Dima Bessonov]

Hi,

Before we dive too deep into the muddy waters of Pathworks: even if/when you've solved the specific problem you described, performance and reliability of such transfer (60MB files) may still be problematic. If the connection breaks and you didn't notice that, you may end up with a corrupt file. So much for M$-born technology (depending on version, Pathworks emulates NT 3.51 - NT 4.0 server).

1)If you want reliability, use NFT, a Windows program from Pathworks client CD. It doesn't need Pathworks on OpenVMS side but it does need DECnet on the PC side. Install DECnet on your PC from the same Pathworks client CD.

2)If you don't want to install additional software on the PC, you can use FTP. I assume you have HP's own TCP/IP Services software installed on your OpenVMS server. You'll need to configure and start FTP server on VMS but that's pretty simple (@SYS$MANAGER:TCPIP$CONFIG.COM will get you there). The performance will be better than Windows/Pathworks click&drag.

Now to the Pathworks. From what I see in your BMP files, it looks like your Pathworks (Advanced Server) server doesn't accept PWXXWINAT licenses at all - probably they're unsuitable for your version of the Advanced Server. I also see that of three accepted licenses, only one license is placed in "Server-based" group and that license was occupied at the moment when you issued the command. If your PC is just plain Windows without HP's Pathworks LAN Manager licensing agent (this is most probably true), it will always try to get a license only from "Server-based" group and won't ever get the license from "Default" group. I guess you started a big (60MB) data transfer and it hung. You tried the copy one more time and your PC tried to open another connection. The first connection was still unreleased so you got the error message.

1) Clean up the hung connections. Use "ADMIN SHOW SESSION" and "ADMIN CLOSE SESSION sessionname" commands to purge them.

2) Stop Pathworks server(@SYS$STARTUP:PWRK$SHUTDOWN), do MCR PWRK$ADMIN_LIC and try to move two remaining licenses from "Default" to "Server-based". Restart Pathworks (@SYS$STARTUP:PWRK$STARTUP). Try copying again. At least you'll have three attempts instead of one.

3) I tend to think you'll still see the same message about license, only slightly later, because actual problem is not license-related, it's performance-related.

4) To improve performance, try the following. Stop Pathworks and run @SYS$UPDATE:PWRK$CONFIG. When asked about server parameters, look for the parameter "Data cache size". By default it should be 2048, I guess. Try something like 32768 instead. Also make sure you permit the server to use sufficient percentage of RAM. Continue configuration, let AUTOGEN run, reboot the machine (if necessary) and restart PATHWORKS.

If all the above doesn't help, check if an ECO or newer version of Pathworks server is available. If that still doesn't solve your problem, read from the beginning ;-) .

Good luck.

[Andy Bustamante]

In addition to all the license admin replies, what client version/transport are you running on the Windows 2000 side. If you're using DECnet check to see what version of Pathworks 32 was installed. The Pathworks 32 7.3 release has problems with file transfer for large files or many files. There was a fix avaialable, which was included into the Pathworks 32 7.4 client which started shipping this year.

[Rupert_1]

Where can I find Pathworks 32 V7.4 release
note ? I have found V7.4 SPD.

[Anton van Ruitenbeek]

KTLAN,

As I'm reading it looks you're using PW32 on youre clients. Why ?
I don't use this for the last years at all. I removed this because it's guiet a problem to manage this if you have a lot of notebooks comming and going. Whe only use AdvancedServer as a big NT (print/filesharing) box. It works very fine whitout the hickups of M$oft.

Only if you're using DECNet or NEEDED the license server you use PW32. If you get the change, get rid of it.
Yes, I'm a VERY happy AdvancedServer user for the last 15 years (PW/AS)

AvR

[Andy Bustamante]

Rupert, Pathworks 32 ships in the quarterly SPL or can be ordered individually.

Anton, I use Pathworks 32 on Windows sytems to capture graphics and store them on Pathworks shares. By not enabling TCPIP on the Windows system, I elminate many of virus propigation paths. No Internet Explorer, no Outlook Express no tcp/ip worms. . . Once configured and licensed these system behave.

[Martin P.J. Zinser]

Hi Ktlan,

a.) Get your server licenses cleaned up.
b.) I concurr with the suggestion to investigate getting rid of the client licenses
at all. If you just want to do file/print serving from Advanced server to W2k client PCs they are not required. If DECnet enters the game this changes...

As for workarounds:

- Is the file compressed? If not Zip it, maybe it shrinks under the limit causing problems.
- Do not Drag'n'Drop but use regular FTP from the commandshell. At least you should get
clear errors that way ;-)

Greetings, Martin

[Dima Bessonov]

Anton, Martin,

I'm under impression that your suggestions slightly mix two different terms (and that may be confusing for the original question's author):

1) Pathworks client software (PW32), which may or may not be installed on the PC side;

2) LAN Manager License _requester_ - part of the above-mentioned Pathworks client. Again, when the client is being installed, a system administrator may or may not install this license requester.

From the license usage standpoint, it doesn't matter for Pathworks server whether PW client (PW32) is installed on a PC or not. What makes the difference is License requester. If it is installed, it always allocates a client-type (dedicated) license for the PC and gets it from the "default" license group. If it is NOT installed, Pathworks server tries to use a free license from the "Server-Based" license group.

Summarizing the above-said: when you want a particular PC to have a guaranteed connection, install license requester on it and use client-based licensing scheme on the server. If you want to maximize server's capacity (limitation by concurrent connections), don't install the license requester on the PCs and use "server-based" licensing scheme. Licenses can be same (if they're PWLMXXXCA type), it all depends on the license group they belong to. Leave them in "default" group and they'll act as client-based licenses. Move them into "Server-Based" group and they'll function as server-based ones. One may also mix these two schemes as he/she wishes.


Cheers,
Dima

[Brad McCusker]

All...

>From the license usage standpoint, it
>doesn't matter for Pathworks server whether
>PW client (PW32) is installed on a PC or
>not. What makes the difference is License
>requester. If it is installed, it always
>allocates a client-type (dedicated) license
>for the PC and gets it from the "default"
>license group. If it is NOT installed,
>Pathworks server tries to use a free
>license from the "Server-Based" license
>group.

This is basically correct, with one missing, but important point. If the PATHWORKS server is not running the License Server, then there will be no client based license allocated. Without the License Server running, you are essentially forcing all the DEFAULT group licenses to be server based.

Brad McCusker