The list of Upload messages below contains just some example.
It is not a complete list of possible messages. Also, it does NOT provide a universal or complete solution or all causes for the messages! Depending on the system setup, there might be other causes and effects. Some messages as well as whether the original source files are moved to the Upload error folder may also depend on the system setup and database server setup itself. For example databases in Access, MS-SQL or Oracle may behave differently, the selected character set of the database can have an impact, or whether the database was setup as case-sensitive or not. Some messages displayed in the Upload log may even be forwarded from the database system itself, e.g. messages containing the term “ORA…” are forwarded from the Oracle database system
|
Code |
Error description |
Possible Solution |
|
-97 |
Data cannot be stored in database. K00xx cannot be written! Field WVxxx is missing |
In the files to be uploaded there are additional data fields which are not activated in the databases. The database options describe how to activate them. Link to: Value Database - Functions and Administration |
|
-93 |
Data cannot be stored in database. K00xx cannot be written! Field WV00xx is too small |
This message can have 2 reasons. 1) In the case of K0009 (Text) or K0005 (Event): The fields were created too small in the database options. As of version 13, these can be enlarged in the database options. Link to: Value Database - Functions and Administration 2) In the case of other additional data fields: In the course of the versions, many fields were updated and field lengths extended, also in the area of additional data. The reason for the error message is then a failure to update the values databases. |
|
-47 |
<UNC> path: Directory not found |
UNC path for gage PC configured in Upload, but network connection or PC is not available |
|
600 |
Error reading file |
The named file is not a DFQ / DFD / DFX - file |
|
709 |
Error reading file |
Data file empty |
|
103 |
Error reading file |
file is locked by another client uploading the same file |
|
-32 -19 |
Exception loading tree Closing database connection |
Result of very many upload errors in sequence |
|
-8 |
Part is locked by <Q-DAS user name> |
A part in the database may only be written to by one system at the time. All Q-DAS products therefore put a lock on the part in the database that is being written to. All other Q-DAS-users –including the Upload - will have “read-only” access to that part while locked. The lock will be removed once the part in the database is properly closed by the current user, and be available for write access, e.g. for the Upload again. |
|
-57 |
Duplicated values found => K00xx = |
in the Upload the setting "Reject duplicates based on "K-field"" is set and the upload reject the files. |
|
-13 |
DBError writing values (Table WERTEVAR) [Execution of WVINSERT failed] => [FireDAC][Phys][ODBC][Microsoft][ODBC Driver xx for SQL Server] [SQL Server] Could not find stored procedure |
Multiple reasons possible: The Upload (Service) has not been restarted after changings on the additional data The stored procedures have been created with another SQL-User and the actual SQL-User is not allowed to use them or to create new |
|
112 |
Error reading file |
Correctly written DFQ files are moved to the upload error directory if the hard disc is full. [Hard disc where the Q-DM application is installed and running] |