Technical Support

NamoSoft BV info

-Click here for Licensing support

Emergency:
We are proud to offer the best and fastest service almost around the clock.
-Click here for more instructions
You can also contact us via our email
We will respond promptly!

Technical Support and administration

E-mail: mail@namosoft.nl

To keep you updated with the very high level of our developments and for support to the NamoSoft software we offer a all-in license service.
This license service is available to all NamoSoft customers. Contact our sales department.

Troubleshooting/Errors

Many of the SOSET software error messages that may appear to alert you to a problem or condition are self-explanatory.
Here you find the SOSET error overview
Here are some common occurrences that may arise, along with potential solutions or explanations.

Setup errors:

Message: "SOSET detected a license error #051 or #52; date"
The setup procedures tried to install files and settings, but could not open tables or files exclusively. This indicates that the tables are in use by other users or applications.

Message: "SOSET detected a license error #026; date"
Normally this indicates that your license has been expired; check the date in the NamoKey-program under: File, Software Protection key. Another cause for this error is that the date of your system is not correct and probably changed after or during SOSET operation. This might be caused by an empty system-battery in your system or that the date is set forward or backward after SOSET execution. Contact your hardware supplier to check the battery. The license procedures in the SOSET NamoKey software require correct date and time information.

To continue working immediately you should set the date of your system back to the date as mentioned in the error-message. In that case you need to control the date until the date of the error message is the same as the current date. It is also possible that the system.dbf table and/or some so called *.ini have been damaged.

Please contact NamoSoft if you need further assistance.

Message: "SOSET detected a license error #027 until #041, ; date"
Normally this indicates that your license has been expired; check the date in the NamoKey-program under: File, Software Protection key.

Another cause for this error is that the date of your system is not correct and probably changed after or during SOSET operation. This might be caused by an empty system-battery in your system or that the date is set forward or backward after SOSET execution. This might also indicate serious checksum-problems in various SOSET initializing files. Check your harddisk with the Windows System Agent for data-errors. You also should contact your hardware supplier to check the battery. It is also possible that the system.dbf table and/or some so called *.ini have been damaged. The license procedures in the SOSET NamoKey software require correct date and time information.

Please contact NamoSoft if you need further assistance.

Message: "Internal check error #101: Contact NamoSoft (OrderEntry)"
Message: "Internal check error #111: Contact NamoSoft (Typeset Gold)"
Message: "Internal check error #121: Contact NamoSoft (Typeset Gold M&R)"
Message: "Internal check error #131: Contact NamoSoft (Typeset Silver)"
Message: "Internal check error #141: Contact NamoSoft (Typeset Silver M&R)"
Message: "Internal check error #151: Contact NamoSoft (Typeset Remote)"
Message: "Internal check error #161: Contact NamoSoft (Typeset Quick)"
Message: "Internal check error #171: Contact NamoSoft (Typeset Quick M&R)"
These message indicate a version conflict. Your license is limited to a lower version than the one you have started. An update or upgrade is advisable.

Please contact NamoSoft if you need further assistance.

Message: Internal check error #0: Contact NamoSoft Wrong license-check for SOSET Order-Entry Software
Message: Internal check error #1: Contact NamoSoft Wrong license-check for SOSET Typeset Gold Software
Message: Internal check error #2: Contact NamoSoft Wrong license-check for SOSET Typeset Gold M&R Software
Message: Internal check error #3: Contact NamoSoft Wrong license-check for SOSET Typeset Silver Software
Message: Internal check error #4: Contact NamoSoft Wrong license-check for SOSET Typeset Silver M&R Software
Message: Internal check error #5: Contact NamoSoft Wrong license-check for SOSET Typeset Remote Software
Message: Internal check error #6: Contact NamoSoft Wrong license-check for SOSET Typeset Quick Software
Message: Internal check error #7: Contact NamoSoft Wrong license-check for SOSET Typeset Quick M&R Software
These errors might indicate serious checksum-problems in various SOSET initializing and licensing files. Check your harddisk with the Windows System Agent for data-errors.

Please contact NamoSoft if you need further assistance.

Problems with Pincodes.
In case you have lost all pincodes there is a very drastic but simple solution. Use only if there are no other solutions. Delete in the SOSET-data-directory all USER.* files and run the NamoSys program again. This will set-up the user files again and start with the Supervisor pincode : 0000. Now, you can redefine all users, just as you did after installation.

Problems with User Connections.
In case of an abnormal program termination, e.g. a power outage, or program crash, the following situation can occur. There are still active users according to SOSET, although there are actually no users currently connected. (You can view all active users in the Current connections option from the File Menu in NamoKey.) As a result NamoKey cannot be closed and the SOSET software cannot be exited.

Solution: Use the Clear all-button in the Current connections option from the File menu in NamoKey. SOSET will disconnect all users that were still 'connected', according to the SOSET system.

Software Protection Key Errors.
You need a Software Protection Key to legalize the use of the SOSET software. This key must be connected to one of the parallel ports of your computer in case you have a single user version of the software. A multi-user version of the SOSET software requires (only) one Software Protection Key connected to one of the parallel ports of a network. On that same station you should run (always) the NamoKey software. The NamoKey software is described separately. In case of abnormal program termination, e.g. power problems, licenses may be limited. Use the Clear all-option from the Current Connections File menu option in the NamoKey program to free all licenses and clear all users.

Message: No SOSET license path or No SOSET data path
In the SOSET folder you can view the properties per program. Click the right mouse button and select 'Properties'. Select 'Shortcut' and view the 'target line': from left to right it should read the SOSET program path (drive\DATA\SOSET\programname.EXE), the SOSET DataPath (drive\DATA\SOSET) and the SOSET LicensePath (drive\DATA\LICENSE). You can specify the SOSET DataPath also in the Preferences from the File menu in NamoKey. The SOSET DataPath refers to where the NamoKey software will find license information.

Message: Unable to open license table.
This message refers to the linkage between the license control and the NamoKey software program. You should start NamoKey at the security station and keep it running for as long as you want to work in any SOSET program. Make sure the software protection key is connected to this computer.

Message: No license available.
You have exceeded the total number of licensed users. If you want to log in to the SOSET system, somebody else has to close a SOSET application. Another explanation here is that your license has expired. If that is the case you can check the software protection key option from the File menu in NamoKey. Contact NamoSoft BV for more information.

Message: Installation error.
As a result of an installation error, is it possible that the Typeset button on the toolbar in SOSET OrderEntry does not function properly. If that is the case, you should do the following:

In the Windows directory you search for the file TYPESET.INI. This Windows directory could be, e.g. C:\WINDOWS. You double-click the file to open it. In this file the defaults are summed up. The SOSET ProgramPath should be referring to the directory where the TYPESET.EXE is saved. An example is C:\APPS\SOSET\. You can view the ProgramPath in the Preferences settings from the File menu in SOSET Typeset.

You can see the ProgramPath when you right-click on the Typeset icon in the SOSET folder and select Properties. Then you choose 'Shortcut' and in the Target line you can view the SOSET ProgramPath, the SOSET DataPath and the SOSET LicensePath.

As a result of an installation error the following message can appear on starting Typeset: "isgdi9.DLL not in specified directory." This file is set by default on installing SOSET. Follow the next instructions to solve the problem.

  • You go to the Windows System directory, e.g. \WINDOWS\SYSTEM. There you locate the file, named: ISVB.INI. The last line of this file goes as follows:
    [ImageStream Graphics Filters - Interface]
    Interface=Drive:\APPS\SOSET\FILTERS\isgdi9.dll
  • Check the DataPath. When you have changed something during installation, like the default path, this could mean that the *.DLL file can not be found. You have to locate this isgdi9.DLL file (use the Find file Windows option).
  • Write down the correct path to this file in the last line of the ISVB.INI file in the Windows System directory.
  • Save the changes you have made to the ISVB.INI file.

Novell network error. Message: Codebase Error
Error #: -200
Error #: 83805
File is not a datafile
database corruption detected
drive:\...\...\PAGE.DBF
drive:\...\...\PAGE.DBF
These messages can occur when you work with Windows95 and/or Windows NT in combination with a Novell network. SOSET OrderEntry software only runs in Windows 95 and/or Windows NT environment. Therefore we recommend a Windows NT server with Windows 95 network-stations. If you want to use a Novell-net in combination with Windows 95 then you need to contact Novell-support for a (so-called) "patch". There are some modifications to Novell, in order to let it work together with the 32-bits systems. E.g. long filename-support is not standard Novell SOSET does not offer a usable solution, except for a workaround procedure as follows:

If the error message appears on one of the network-stations all users should exit all SOSET programs. After that the users may re-start SOSET. Wait until all users have SOSET running. Then you can begin to start typesetting or entering orders.

Another (temporary) solution is to quit and restart Namokey at the network-station with the software protection hardware key.

IMPORTANT NEWS: ANOTHER SOLUTION FOR CODEBASE -200 -83805 ERROR
Recent tests have brought a solution in a Novell-Windows network environment:
Create and move the license path from the shared Novell network drive to a shared Windows drive on one of the stations.

ISDI9.DLL error.
As a result of an installation error the following message can appear on starting Typeset: "isgdi9.DLL not in specified directory." This file is set by default on installing SOSET. Follow the next instructions to solve the problem.

  • In the Windows System directory (e.g. \WINDOWS\SYSTEM) you locate the file, named: ISVB.INI. The last line of this file contains the following:
    [ImageStream Graphics Filters - Interface]
    Interface=Drive:\APPS\SOSET\FILTERS\isgdi9.dll
  • Check the datapath. When you have changed something during installation, like the default path, this could mean that the *.DLL file can not be found. You have to locate this isgdi9.DLL file (use the Find file Windows option).
  • Write down the correct path to this file in the last line of the ISVB.INI file in the Windows System directory.
  • Save the changes made to the ISVB.INI file.

Message: Codebase Error -920
Codebase Error 95905
Out of memory
In case this message appears on your screen, you should check the free diskspace on the Server or the Datapath drive.

Message: SOSET detected a fatal error during initializing: Error code.
Message: General Protection Fault Error

These errors should be reported to NamoSoft for further research and solution.

back to the top

 

Software Protection Key Errors

Message: Insert security key in one of the parallel ports
Message: Image Read Error
You need a Software Protection Key per program to legalize the use of the SOSET software. This key must be connected to one of the parallel ports of your computer in case you have a single-user version of the software. A multi-user version of the SOSET software requires just as the single user version only one Software Protection Key per SOSET application connected to the network server in a Windows network. In other words, there is a separate software protection key for each SOSET program. In case of abnormal program termination, e.g. power problems, licenses may be limited. Use the Clear all-option in the Current Connections, File menu in the NamoKey program to free all users/licenses.

All SOSET users should have enough rights to read, write, delete and create directories in the specified directory.

Message: Time synchronization problems.
The Software Protection Key routines are based on a fast synchronization time, so the date and time on your network-server and the stations that will use the SOSET software must be the same or may differ not more than 3 minutes. Problems with the Software Protection Key can also be caused by a too large difference of time between the network-server and the network-stations. Check this by entering first the command time on your network-server. With the same command on your network-station(s) you check or modify the time at your network-station(s).

In most networks the time is automatically synchronized, because of use of global timing. Synchronization is mostly realized within a few seconds after the Software Protection Key driver is loaded. Some networks however need about 10 minutes after the Software Protection Key driver is loaded, before the license is available to the SOSET users.

back to the top

 

Unknown Errors

SOSET detected a fatal error during initializing: Error code.
General Protection Fault Error

These errors should be reported to NamoSoft for further research and solution.

SOSET DOS Import
Unrecognized field.
Unable to add textblock to a NULL textline.
Text
Unable to delete textblock: current and only in textline.
Create font failed.
SOSET detected a divergence error: Error code #004 (004-012).
Drawing
The stamp contains circular textlines: Height and width must be equal.
This textline contains tabulations. Left justification is required.
Height and width must be equal for circular shaped textlines.
Tabulation can only be set in a left-justified textline.
Logo
X or Y position not accepted.
Width, Height not accepted.
Unable to allocate memory for metafile bits of logofile.
Unable to lock memory for metafile bits of logofile.
Unable to set memory for metafile bits of logofile.
Unable to read file header.
Bitmap creation failed.
The logofile is not a placeable windows metafile.
The logofile cannot be opened.
The logo doesn't fit in the stamp. Adjust position and/or size.
Unable to read the first double word of the header of logofile.
Unable to read the placeable metaheader of windows metafile.
Unable to read the metaheader of windows metafile.
Unable to read file header of PCX File

back to the top

 

Contact us in case you have any question or comment via our email