SOSET Error Information
ArtID: 0000000904 TOPIC: Building Codebase library Building the codebase lib and dll generates serveral error, both during compiling and during linking.Codebase dll release version will build fine with the codebase patch. Remarks: Don't forget to link the libs (c4dll.lib, c4lib.lib) into the project ArtID: LIBRARY005 TOPIC: Error message:
Cannot locate the Microsoft Visual Foxpro support library. The Windows version prevents the installation of some parts of the NamoUtil module during setup.
These parts are harmless and essential for the high speed index-searches and matches.
For this issue is a workaround:
Copying all dll's into the startup directory of NamoUtil.exe fixes the compatibility.
NamoUtil9_dll.zip with the missing dll's can be requested via email. ArtID: 0000000079 TOPIC: Codebase erro #-70 Error # 90621
Error code Occurred when:
Changed the Status on one of my runs and I got this error message:
Error #-70
Error # 90621
Reading File
C:\Data\Soset\Stamp.fpt
13181440
file4readALLLOW
Solution:
First reindex the database via Namosys > File menu > reindex all
If this doesn't resolve the problem you need to repair the stamp table with
Namoutil > Soset utils > Clean and repair > repair table.
Next NamoSys, reindex the database after such a repair ArtID: 0000000080 TOPIC: Codebase erro -1210 Error 83801
Code Base Server Transaction Error Error -1210
Error 83801
Transaction Error
Invalid transaction file
Run Recovery
Delete the file server.log or rename it ArtID: 0000000903 TOPIC: codebase error #490 during startup OrderEntry
index problem during start starting OrderEntry generates a codebase error -490, unrecognized value on table ordmain
Also, opening this table in NamoUtil generates an error (var IndexHou not found -> no valid default index) and Namosys hangs during reindex
Ordmain.cdx file is corrupted. The header of the file does not show any tag information whatsoever.
Deleting this file and reindexing in Namoutil does the trick Remarks: Does a regular reindex in namoutil create a new (structural) index, or does it synchronizes existing indexes ?? ArtID: 0000000072 TOPIC: Codebase error - 3
create stamp from web On web preview page:
error 3: unable to create stamp from web input
cause:
Site DOES have access to novell server ( Qjob record is created).
However for creating the preview JPG the sosetwww.exe creates a tmp file in the windows temp dir.
Thus: the webuser needs read, write rights in winnt dir. ArtID: 0000000001 TOPIC: Codebase error -200
Database corruption codebase error #20 unable to backup orm_sh.dbf
dbf had attribute Read-only. ArtID: 0000000046 TOPIC: Codebase error -200
Database corruption After system crash the database stamp.dbf is corrupted.
This will result in the Codebase error message -200.
Open the table exclusive in SOSET Namoutil (File menu > Open table exclusive).
Export the table and give it another name (File menu > Export > Soset > Database table).
After exporting give the corrupted database another name and rename the just created database to the name of the corrupted datatabase.
PAY ATTENTION:If the table contains memo's, also rename the corresponding .fpt file.
Reindex the table in Soset Namosys.
Problem will be fixed then. ArtID: 0000300008 TOPIC: Codebase error -30 or -310 index errors -STOP working, database may be damaged!
-All users log off and close SOSET modules, also namokey!
Check the shotcuts to SOSET modules on all workstations in the network. Shortcuts may only link to the SOSET executable on the network. Delete local SOSET excutables (leave DLL's etc)
Other things to check:
-Any files larger than 250Mb in datadir, need to be verified.
-Check DiskFull
-Delete all CDX-files in data-dir, but NOT system.cdx; NamoSys, Reindex all
-Cut soset_cb.log from data-dir and paste into backup-subdir
-Delete soset_cb.log in data-dir
-Delete all files in license-dir, EXCEPT: namosoft.sos, license.dbf
-Table is corrupt and need to be repaired by NamoSoft
-Verify and check the network, plugs, switches, cables, network cards etc. ArtID: 0000000008 TOPIC: Codebase error -310 Not a Correct index File during archiving
archiving orders During archiving orders in Namosys one gets the messages:
error# -310
Not a correct index File
index file is exclusive, locked or dos read-only. Index file must be corrupt
CUSTDATE
This message can occur at the beginning of archiving or somewhere in the middle because in the middle it may start to write records to another year therefore using another talbe and index
Index of archived tables are corrupt
reindex all archive tables ArtID: 0000000059 TOPIC: Codebase error -490
reindex During startup of Typeset codebase generates error: -490 Unrecognized value
followed by: "Unable to open stamp.dbf"
reindex stamp.dbf ArtID: 0000000010 TOPIC: Codebase error -70 during viewing stamps in PW
Unable to get corrected or entered stamps When getting entered or corrected stamps in Pagewizard a codebase error -70 occurs
Stamp table is corrupt. When browsing through the stamps the info memo dialog display the stamp-def info or history info. Thus this ftp does not belong to this stamp.dbf or the table is generally corrupt.
One can try to save some stamp by finding out at what time in the stamp.dbf this ftp errors occurs. If found delete all following stamps and export the ones that remain. ArtID: 0000000015 TOPIC: Codebase error -970
table update error Codebase error -970
table update error
After starting up Namosys and entering pincode, codebase error -970 pops up.
This occurs after Namosys tries to update the stamp table but fails (propably because of network proplems)
Copy the tables on the local drive and start Namosys on these tabes for updateing the fields. After that copy the tables back.
When Namosys crashes during update also the Namokey has lost connection to the license file. ArtID: 0000000071 TOPIC: codebase error -970
table corruption When printing barcodes for SSS, Namosys generates codebase error: -970 database corruption.
Product table was not up-to-date. "Entered" field was missing ArtID: 0000000009 TOPIC: Codebase error -970 Data Structure Corrupt or not Initialized
Codebase error when starting soset programs After entering Pincode in any of the SOSET programs there is the following codebase error:
-970 Data structure corrupt or not initialized
License files are corrupt.
Close Namokey , delete License.dbf and actuser.dbf and start Namokey again. ArtID: 0000000014 TOPIC: cb error -970 after installing update
ArtID: 0000000177 TOPIC: codebase error on soset_cb.log
codebase error -30 Codebase error
Error -30
Error 90605
Determing File Length
file.....
f:apps\soset\soset-cb.log
soset-cb.log is just a log file and can be deleted (everyone out of Soset). A new one is created automatically. ArtID: 0000000090 TOPIC: Error: -30
90605
determining file length
file4len
F:\Soset\soset_cb.log
Close all Soset programs, incl. Namokey. Delete specified file and restart. Remarks: the cause of the error-message is unknown. ArtID: 0000000017 TOPIC: codebase errors -40, -60 stamp.fpt
ansi import during ansi import codebase errors -40 and -60; -90606 setting file length of stamp.fpt
Remarks: error code -90606 forwarded to Codebase for details ArtID: 0000000057 TOPIC: codebase index error
actuser.dbf I have a proble with my Soset. When I try to go into typeset, I get the
message - Error # -310
Error # 84907
Not a correct index file
unsupported collating sequence
This message comes up when I put in the pin code, my own or 0000 supervisor
code. It make no difference. I cannot get into any other programme. Do you
have any solutions please.
Log off and close all SOSET programs, including Namokey.
Locate the SOSET license directory (usually: ...\data\license)
Delete all files in this directory, EXCEPT: namosoft.sos, remote.sos and if you are using web clicks or order import clicks, license.dbf
Restart SOSET at the station where the hardware key is connected. Remarks: actuser.dbf has index. ArtID: 0000301000 Error exclusive database-tables in SOSET NamoSys
ArtID: 0000301001 Error: new soset in SOSET NamoSys
ArtID: 0000301002 Error: protection key errors in SOSET NamoSys
ArtID: 0000301010 Error: support in SOSET NamoSys
ArtID: 0000301011 Error: troubleshooting/errors in SOSET NamoSys
ArtID: 0000301012 Error: unknown errors in SOSET NamoSys
ArtID: 0000301013 Error-message troubleshooting/errors in SOSET NamoSys
ArtID: 0000301015 Errors new soset in SOSET NamoSys
ArtID: 0000301016 Errors: support in SOSET NamoSys
ArtID: 0000301017 Errors: technical support in SOSET NamoSys
ArtID: 0000301020 Errors: troubleshooting/errors in SOSET NamoSys
ArtID: 0000301022 Errors: unknown errors in SOSET NamoSys
ArtID: 0000301025 Errors: setting software in SOSET Order-Entry
ArtID: 0000301030 Errors#004 unknown errors in SOSET NamoSys
ArtID: 0000301031 Errors#026 troubleshooting/errors in SOSET NamoSys
ArtID: 0000301032 Errors#133 undelete in SOSET TypeSet
ArtID: 0000301035 Errors#141 troubleshooting/errors in SOSET NamoSys
Errors#145 sort in SOSET Quick TypeSet
ArtID: 0000301037 Errors#146 template in SOSET Quick TypeSet
ArtID: 0000301040 Errors#151 troubleshooting/errors in SOSET NamoSys
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.
Contact us in case you have any question or comment via our email