GTXImage CAD Series Startup Messages

GTX Corporation

GTX Customer Support

Startup Messages

Upon first execution of a new installation of the GTXRaster CAD or GTXImage CAD programs, with an unauthorized license, you will most likely see of one or more of the following messages displayed. Some of these are to be expected and some indicate that additional steps are required to finish the installation.

The following two messages are normally displayed after a successful installation of a licensed Raster CAD prior to completion of the authorization process. Please refer to the Licensing instruction. All HASP licensed GTX products are shipped with limited use HASP key coding. The authorization process converts the coding to unlimited use.

A HASP Device Driver must be installed to enable GTXRaster CAD or GTXImage CAD to access it's license from a HASP key. The following message labeled with error code 15 is commonly displayed if the device driver was not installed.

The GTX software was designed with different levels of licensing:

The GTXRaster CAD Series levels include GTXRaster Tools, GTXRaster CAD, GTXRaster R2V and GTXRaster CAD PLUS.

The GTXImage CAD Series levels include GTXImage CAD and GTXImage CAD Plus.

The following message will be displayed when the license coding of the HASP key does not match the program level of the installed software. The HASPCheck program may be used to determine the license level provided by the coding of the HASP key.

Following any program license failure message the program will start in demonstration mode, as indicated by the following alert.

Connections to floating Networked HASP licenses are governed by the presence of an active HASP License Manager, network protocol rules, and active network connections. Many possibilities exist for faulty connection to a floating license, though the occasion for that is rare. Some of the most typical reasons for error alerts like the following display are lack of a device driver, lack of a License Manager, lack of a connected NetHASP key, or an error in variables of a NETHASP.INI file (where that file is applied).

Aladdin Knowledge Systems has provided a list of error code messages, by number, which may be useful in troubleshooting a floating license failure. Note that these messages cover a broad range of operating systems and network protocol issues and most have never be seen by GTX customers.

The following error codes are returned by the NetHASP system. Error codes below 129 are communication errors. Error codes from 129 and up are returned by the NetHASP License Manager.

Error Code	Description
0	Operation successful.
1	The IPX, NetBIOS or TCP/IP protocols have not been installed properly. Act accordingly.
2	Communication error. Unable to get socket number. Applies to IPX and TCP/IP. Verify that the protocol is installed properly.
3	Communication error. - NetBIOS: Unable to establish session. Verify that the protocol is installed properly. - IPX: Unable to get NetHASP License Manager's immediate address. Verify that the protocol is installed properly. - TCP/IP: Unable to connect to the server. Verify that the server address is correct in the INI file.
4	No NetHASP License Manager was found. Check whether your software has a path and read permission to the address file.
5	Cannot read the NetHASP License Manager address file.
6	Cannot close the NetHASP License Manager address file.
7	Communication error. Failed to send packet. Verify that the protocol is installed properly.
8	No answer from the NetHASP License Manager. IPX - The network is busy or incorrect address files found. In the latter case, delete all copies of the HASPADDR.DAT and NEWHADDR.DAT files. NetBIOS - the network is busy. TCP/IP - If the TCP method is used then the network is busy. If the UDP method is used then the network is busy or there is an incorrect address in the INI file.
10	You called the hasp() routine with one of the services, without first calling the LOGIN service.
11	Communication error. Adapter error. Applies only to NetBIOS. This error can also happen when the NETBIOS protocol is not installed. Verify that the protocol is installed properly.
15	No active NetHASP License Manager was found.
18	Cannot Login because the SET_SERVER_BY_NAME call was not successful.
19	Syntax error in the NetHASP configuration file (LASTSTATUS service returns the line number in which the error occurred in Par2). If LastStatus returns 0 in par2, either there is an environment variable with an illegal setting, or no IP address was found (when working with TCP/IP or UDP to host).
20	Error handling the NetHASP configuration file. A file operation like �open file� or �read file� failed. A possible reason can be that the system has run out of file handles. The LastStatus service returns the OS system error code in Par2.
21	NetHASP did not succeed in allocating memory. This error is unique to NetHASP interfaces for Microsoft Windows applications and DOS extenders. Try to free DOS memory.
22	NetHASP did not succeed in freeing memory. This error is unique to NetHASP interfaces for Microsoft Windows applications and DOS extenders.
23	Invalid NetHASP memory address.
25	Failed to load the DLL (winsock.dll or w32sock.dll). Applies only to TCP/IP or IPX.
26	Failed to unload the DLL (winsock.dll or w32sock.dll). Applies only to TCP/IP or IPX.
28	Winsock.dll startup error. Applies only to TCP/IP.
30	Failed to close the socket. Applies to TCP/IP only.
33	Protocol already set. Returned only when you attempt to set the protocol without having logged out completely from the API.
129	The correct NetHASP key is not connected to the NetHASP License Manager.
130	The Program Number (Prg Num) specified is not in the Program List of the NetHASP memory.
131	Error reading from NetHASP memory.
132	Error writing to NetHASP memory.
133	The current LOGIN request exceeds the number of stations which may run the software concurrently.
134	The current LOGIN request exceeds the number of authorized activations for the software.
135	You called the hasp() routine with the LOGOUT service without first calling the LOGIN service. This can happen when the License Manager was reloaded or you have been logged out from the License Manager.
136	The NetHASP License Manager is busy. This may occur if your NetHASP system is not well adapted to the network.
137	There is no space in the NetHASP user list.
138	Internal NetHASP error. The Number of Authorized Stations is larger than the maximum number designated by the NetHASP model.
139	The NetHASP License Manager crashed and was reactivated, or you called the hasp() routine with one of the services without first calling the LOGIN service.
140	The NetHASP Licence Manager does not serve your station's network.
141	Invalid service, or new version of the HASP API is communicating with an older version of the NetHASP License Manager.
142	Cannot find the NetHASP License Manager matching the name specified in the NetHASP configuration file.
150	No NetHASP License Manager with the assigned name was found (this error is returned by SET_SERVER_BY_NAME).
151	Two or more different NetHASP License Managers with the assigned name were found (this error is returned by SET_SERVER_BY_NAME).
152	The encode operation failed because the service was not supported by the hardware.
153	The decode operation failed because the service was not supported by the hardware.
155	An old version of the License Manager has been found. The API used required a newer version of the License Manager to be installed.

GTX SUPPORT

Authorize
HASP Hardware Lock/Dongle

Software License
Activation Help

Support Navigator

Tutorials

Product FAQ

Download

Request Support

ATTENTION:
HASP driver update

GTX Corporation • 15333 North Pima Road • Suite 116 • Scottsdale, AZ 85260
tel: 480-889-8600 • US toll free: 800-879-8284 • fax: 480-889-8610 • email: info@gtx.com

GTX Europe, Ltd. • 8, Cedarwood • Chineham Park, Crockford Lane • Basingstoke, Hampshire
United Kingdom RG24 8WD • tel: +44 (0)1256.814444 • fax: +44 (0)1256.364887 • email: info@gtx.co.uk
( UK registration information • Company: GTX Europe Ltd. • Registered Number: 2156326 • Place of registration: England
• Registered Office Address: 100 New Bridge Street, London, EC4V 6JA)

r2v raster to vector tiff cals g4 raster to vector paper to cad paper to cad paper to cad tiff view markup redline view markup redline view markup redline vectorization vectorisation vectorization vectorisation vectorization vectorisation R2V GTXRaster CAD GTXRaster Trace GTXRaster CAD Plus GTXRaster R2V GTXImage CAD GTXImage Tools scanclean ScanClean GTXScan Clean Rastercad rastertrace rastercad plus raster r2v v2r rasterization rasterisation rasterization rasterisation rasterization rasterisation Redlining Markup