Error "Invalid SQL statment..." when sending: Difference between revisions
No edit summary |
|||
| (21 intermediate revisions by 7 users not shown) | |||
| Line 7: | Line 7: | ||
* 2023-03-09 - error seems to be more common when sends are slow; adding some data to send logging to confirm. | * 2023-03-09 - error seems to be more common when sends are slow; adding some data to send logging to confirm. | ||
== Some troubleshooting == | |||
{{Discuss| | |||
* I have a hunch that this error may be related to a send failing for one collector and a second collector then also sending, leading to problems with the lock file. | |||
So, when the error happens, please have a look at {{Regionalserver|/output}} and see if there is a second centralized_data file there with an extension .lccdb. See [[Lccmdb and ldb files]] for details. Please log here about what you find. [[User:Ttenbergen|Ttenbergen]] 10:41, 2024 November 30 (CST) | |||
}} | |||
== One specific cause: [[D_ID]] overflow == | |||
This error will happen if the [[D_ID]] generated by adding the [[Laptop identifier]], [[Service/Location]] and [[Pat_ID]] has a length greater than 18. Example: | |||
* H5_SOH_Geriatrics-11111 length: 24 failed | |||
* H5_SOH_Geri-11111 length 17 ok | |||
== Error Log == | == Error Log == | ||
'''Please include in your log if you were sending from home, and what time, and if this is after another send failed and before a reboot or the pull of a clean version, and other info you might have. '''\ | '''Please include in your log if you were sending from home, and what time, and if this is after another send failed and before a reboot or the pull of a clean version, and other info you might have. '''\ | ||
*2025-11-06- error at 1454hrs, for H4 laptop, received error 3x, and sent through the 4rth time. [[User:malcudia|Allyson Alcudia]] | |||
*2025-07-16- error at 1515hrs, sent for H3 laptop in office at designated time for HSC sending, received error, closed the access and opened it again, resent, and it sent. [[User:malcudia|Allyson Alcudia]] | |||
*2024-4-12- sending from home H5 laptop, after changing serial number for duplicates in LAU project, gave me this error, copied clean version and went the second time [[User:Lkaita|Lisa Kaita]] 07:46, 12 April 2025 (CDT) | |||
*2025-3-16 @0950 from work H5 laptop, tried and right away same error, stopped at checking for duplicates, copied down clean version, still giving same error | |||
** I sent H6laptop right after with no problems [[User:Lkaita|Lisa Kaita]] 09:55, 16 March 2025 (CDT) | |||
* 2025-3-15 @2050 from home H5 laptop, tried 4 times copied down a clean version, no go, this is the laptop with the LAU project on it?? stops at checking for duplicates [[User:Lkaita|Lisa Kaita]] 20:53, 15 March 2025 (CDT) | |||
*2024-11-30 H5 error at 0700 from home using the test CCMDB (for AHC) copy to local didn't work | |||
** I would not expect copy to local to fix this, I am pretty sure it has to do with something being off at the destination or with the connection. [[User:Ttenbergen|Ttenbergen]] 01:32, 2024 December 1 (CST) | |||
*2024-11-21 H7 error at 1535 from office. tried 2x, then pulled a clean copy, still failed, and didn't have time to try rebooting. | |||
*2024-11-21 H4 error at 1454 - sending from office, tried 3x, invalid SQL message kept popping up. Didn't end up sending. | |||
*2024-11-13 H4 error at 1455 - sending from office, second send went through | |||
*2024-11-12 H8 error at 1452 - sending from work, second send went through. | |||
*2024-11-08 S9 error at 07:14 - sending from home, second send went through. | |||
*2023-08-03 S7 error at 08:13 - sending from home, second send went through. | |||
*2023-06-20 S8 started 0644, error message 0645, exit and reenter program, second send went through | |||
*2023-06-07 S5 sending from home, error at 0705, second send went through. | |||
*2023-06-07 S7 sending from home, error at 07:48. Second send went through. | |||
*2023-06-06 S9 sending from the office, error at 07:05, second send went through. Was sending both S7 & S9 at the same time. | |||
*2023-05-15 S9 sending from home, error at 08:04, exited, second send went through | *2023-05-15 S9 sending from home, error at 08:04, exited, second send went through | ||
*2023-05-15 S7 sending from home, error at 07:18, exited, resend went through | *2023-05-15 S7 sending from home, error at 07:18, exited, resend went through | ||
| Line 27: | Line 56: | ||
*2023-03-31 H6 laptop, send from home, error message x2, copy to local.bat third time went through | *2023-03-31 H6 laptop, send from home, error message x2, copy to local.bat third time went through | ||
*2023-03-15 S8 first send at 0657, ended by error at 0658, second send 0701, ended by error at 0708, news and backup, third send at 0712, ended by error at 0713, local to backup, fourth send ended by new error message" not enough space on disc", gave up | *2023-03-15 S8 first send at 0657, ended by error at 0658, second send 0701, ended by error at 0708, news and backup, third send at 0712, ended by error at 0713, local to backup, fourth send ended by new error message" not enough space on disc", gave up | ||
*2023-03-15 S5 first send from home error at 0711, records set to "sent". During second send "network interruption" error. Third send went through. | *2023-03-15 S5 first send from home error at 0711, records set to "sent". During second send "network interruption" error. Third send went through. | ||
*2023-03-10 S5 first send from home around 0705, exited ccmdb, reentered and second send went through | *2023-03-10 S5 first send from home around 0705, exited ccmdb, reentered and second send went through | ||