Explanation of the Error 1104 Message in JAS

Explanation of the Error 1104 Message in JAS

Introduction

It can occur where users try to perform a transaction in JAS and receive an Error 1104 message, similar to the following: 

 
Error 1104
Error reading file u:\jas\data1\orderhdr.cdx.
Procedure clap
Line 765
 

Reasons for this message

This error is usually due to a temporary loss of connection to the network. Try closing JAS and going back in. If you are now able to generate that transaction, it was most likely due to a temporary loss of network connection. If you are still receiving this error message contact Jonar.

If this error is happening in EDI, and f restarting the program does not work, you may have to reboot the server completely. If this error remains for EDI, the program that cannot be read may have to be renamed and the one from our EDIPRO folder sent instead,
 

    • Related Articles

    • Explanation of the "Error 1" message in JAS

      Introduction It can occur where users try to receive a purchase order in JAS and receive an "Error 1" message, similar to the following: Error 1 File "t:\jsi6\ap_recv.dbf" does not exist SELECT QUICKDYE Procedure init Line 109     Explanation of this ...

    • Explanation of the Error 1705 message in JAS

      Introduction It can occur where users will receive the following error message in JAS: Error 1705 File access is denied j:\aims\data5\style.dbf. SELECT SREP Procedure init Line 93 Explanation of this error message This error message is due to a ...

    • Resolving the Error Message 1440 in JAS

      Introduction It can occur where the user will receive the following error message when printing invoices in JAS: Error 1440 OLE exception error: Exception code c0000005. OLE object may be corrupt Procedure mainreport Line 334 Called from mainreport ...

    • Explanation of the Error 1705 message in JAS

      Introduction It can occur where users will receive the following error message in JAS: Error 1705 File access is denied j:\aims\data5\style.dbf. SELECT SREP   Procedure init Line 93   Explanation of this error message This error message is due to a ...

    • Resolving the Error 39 message - Running out of UPC Numbers

      Introduction The following wiki contains instructions on how to add or change sequence numbers when all the UPC numbers have been used up. When the system runs out of UPC numbers, the following error message will display: Instructions 1. Delete any ...