Job Error Messages
Status and error messages are reported through the Job
Client Log and the Status Message dialog in the
main Console display. For example:
Client Name |
Status Message |
\\DEC14\C$ |
%LANSpin32-I-SUCCESS Normal success status |
\\DEC16\C$ |
%LANSpin32-E-INITFAIL Directory tree initialization failed
_%LANSpin32-F-NOSUCHOBJ Node name is invalid, or file server not running, or the remote node is off |
The program that reported the error is shown first. In the example, LANspin's inventory of \\DEC14\C$
was successful, but it failed to access \\DEC16\C$, probably because the PC was switched off.
Vector AM program names are listed in the table below:
Program |
Operation |
LANEnum32 |
Network Enumeration and Database Auto-population |
LANFree32 |
Free Space |
LANHint32 |
Hardware Inventory |
LANSpin32 |
Software Inventory |
In error messages, the names are followed by a status code, where:
E = Error
F = Fatal Error
I = Information
W = Warning
A message indicates whether the operation was successful or not. This may be followed by one or more of
the following error messages:
The Evaluation Kit license has expired, or you have reached the end of a Short Term license. Contact your
dealer for a product upgrade key.
This error can be caused by an attempt to access a file which is protected, or which is already being
used for exclusive access by a local PC user, or by specifying incorrect access control information for
a remote server/resource.
You may get a NOPRIV error when attempting to perform an operation on a resource that has restricted
access. This can happen when you specify the wrong username and/or password, or when Vector AM uses your
logged on account name because you have not specified the username. This sometimes forces you to enter
a password that matches an account of that name on the remote system.
Check you have specified the correct access control information when accessing a remote resource.
An attempt was made to access a resource which did not exist. The resource is not shared by that name
on the remote Client. Check and correct the resource name and repeat the operation.
The remote PC did not respond to a Call request from Vector AM. Check the physical network connection
to the remote Client. Make sure that the PC is switched on and running a supported network transport and
that it is running the Vector AM SERVER program or a Windows file server. Make sure that the file server
is configured to accept enough simultaneous connections.
If you are using DECnet as the network transport, check the entry in the DECnet Known Clients data
using the NCP program, to ensure that the address matches that which is being used by the PC. If you are
using the TCP/IP transport, you may need to perform extra configuration to allow successful connections.
The PC server did not allow access to the remote resource. This error occurs when:an incorrect access
control password is supplied;
the
PC DECnet is in a SHUT state;
the
PC network stack did not have sufficient resources to accept another connection;
a
network router is configured to disable certain connection requests;
the
remote file server already has the maximum number of clients connected.
In these cases, a more specific error message indicates the precise cause of the error.
Make sure that the named resource is available on the remote system. Check the password matches the remote
resource password. Check the PC's network software configuration (the default setup is normally plenty).
Check that any network routers and bridges are forwarding connection requests appropriately. Reconfigure
the file server to accept more simultaneous clients, if necessary. |
The operation completed successfully.