Running A Network License – Error Code 6

This article relates to Scan2CAD v9 and below

A small number of users that have installed their network license report that when they attempt to access the license file Scan2CAD on another network PC  they receive ‘error code 6.’

There are two possible causes for this:

1. Restricted privileges

Nominated users of Scan2CAD having restricted read/write access for the license file.

The most common cause of this error is from PCs that are attempting to read the license file but do not have read and write privileges on the license file itself.

To resolve, simply navigate to the license file, (remember it should have been installed in a shared network location) right click it and select properties.

The way you set user-specific file privileges differs from each version of Windows but it should be very self explanatory from there.

Dependent on how your network it set-up there may be global privileges settings that require changing. Please speak to your network administrator to ensure privileges are correctly set.

2. Looking in the wrong location

PC’s running Scan2CAD are NOT seeing the same UNC networked convention for your shared drive(s) and therefore not correctly identifying the path/location of the license file.

We would expect each PC to see the same UNC pathnames.

UNC stands for “Uniform Naming Convention”. It’s a standard way to access network shares in NT and other Microsoft products…

The format of a UNC pathname is simple:
<HOSTNAME> is the network name.
<SHARE-NAME> is what the drive or directory you are accessing is shared as, on <HOSTNAME>.
<directory> Any additional directories below the shared directory.

If you need to determine the UNC path to a drive or directory, here is a simple way to get the path:

Using the windows ‘Command Prompt’ accessory – execute the command “net use” on each of your networked computer(s).

The output from this command will contain the drive letters and their equivalent UNC path/filenames:

Example of Usage:
C:\>net use
New connections will not be remembered.
Status        Local        Remote        Network
OK            F:           \\srv\data    Microsoft Windows-network

The command completed successfully.

As long all machines see the same UNC shared drive convention and all PCs have read/write privileges then there should be no problems.