@Greg Stiles According to the attached list of ProvideX error codes, codes greater than 255 are operating system errors... whatever that means.
------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
"Would you tell me, please, which way I ought to go from here?"
"That depends a good deal on where you want to get to."
Oscar Wilde - Alice in Wonderland
------------------------------
Original Message:
Sent: 12-18-2019 14:12
From: Greg Stiles
Subject: Has anyone run into this error before?
So, what is error 600?
Anyone have access to the code to see what is happening at line 48 in module INSTALL?
------------------------------
Greg Stiles
S & W Microsystems
Torrance CA
310.787.1010
------------------------------
Original Message:
Sent: 12-18-2019 13:42
From: Bob Sosbee
Subject: Has anyone run into this error before?
Nope, error 0 is busy or locked. It will be permissions or AV, most likely permissions. Error 5 would be hardware (almost never see that any more). Error 2 would be end of file or out of disk space to expand.
------------------------------
Bob Sosbee
Senior Developer
Accounting Systems, Inc. (ASI)
Covina CA
803-252-6154 x245
Original Message:
Sent: 12-18-2019 13:35
From: Doug Higgs
Subject: Has anyone run into this error before?
I believe error 0 is a hardware error. Out of disk space?
------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
"Would you tell me, please, which way I ought to go from here?"
"That depends a good deal on where you want to get to."
Oscar Wilde - Alice in Wonderland
Original Message:
Sent: 12-18-2019 13:18
From: Jeff Fiddelman
Subject: Has anyone run into this error before?
Posted too fast - ours is similar but not identical...
Error 0 in method Finalize at line 1496
then unable to create error.txt log file.
Jeff
------------------------------
Jeff Fiddelman
Exeplex, LLC
Original Message:
Sent: 12-18-2019 13:15
From: Jeff Fiddelman
Subject: Has anyone run into this error before?
Hi - getting the same exact error today - going from 2015 to 2019.1
Do you have any more info on this error ?
Thanks
Jeff
------------------------------
Jeff Fiddelman
Exeplex, LLC