Hello,
I was testing the network scanning functionality with the ESCL driver, and I noticed some strange behavior during the scans, I did several tests in a row trying to simulate the problem.
In this case, NAPS2 reacted in two different ways, in the first it opens the progress screen, but the progress bar does not move, after some time the bar closes, without error, but there was no scanning.
In the second case, the progress bar reaches 100% but it takes a long time to obtain the scanned document.
I attached the log of both computers (server and client) to see if it helps.
In both cases, the scanner starts working again trying a new scan, it just seems like some communication error between server and client.
I would like to take this opportunity again to congratulate your work, NAPS2 is an excellent tool, for me there is no more practical and simple software for operating a scanner. Thank you for your commitment to this project.
I've made a small improvement in 7.3.1 that might help. I've also improved the client logging, so if you can reproduce the client logs in 7.3.1 that would be helpful.
As far as the first scenario, I've seen that myself when the original driver (e.g. TWAIN) would do the same thing, i.e. it's not an issue with the network connection. Might that be the case for you?
For the second scenario, that definitely sounds like a problem, again client logs with 7.3.1 would be helpful.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello
Returning with the results
In the first case, I believe it is not a problem with the driver, it is a Kodak i2600 scanner, directly via USB it is a very stable scanner, it does not usually cause this type of problem.
For the second case, this time I got an unsupported file error.
Two attempts were made, which are recorded in the attached log.
Hello
Ben, I'm starting to suspect that it might be something related to the company's network, even though it works perfectly (when it works).
Anyway, I reran the tests in version 7.4.1 and the problems remain, I recovered the logs from both computers again. I hope I can collaborate.
In time, I believe it was necessary to add content about EsclServerCertificatePath and EsclSecurityPolicy to the documentation page for use in Organizations.
There's definitely an element of network issue to this, but also some problems with NAPS2 as well. I've fixed a couple issues in 7.4.2 that may help. And I also have some plans for the next version that may make it close to fully reliable. I've also updated the doc for those options.
Thanks for all the testing you've done, it's been incredibly helpful.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for your effort; the communication with the scanner has significantly improved. We conducted several tests, and NAPS2 no longer crashes when finishing the scan. However, there is still a minor issue when opening the communication: in the NAPS2 client, the scanning progress bar opens and then closes without actually starting the scan. Nevertheless, this isn't a major inconvenience since simply starting it again allows the scan to proceed normally. If you find it appropriate, I have attached the logs for review.
Hello,
I was testing the network scanning functionality with the ESCL driver, and I noticed some strange behavior during the scans, I did several tests in a row trying to simulate the problem.
In this case, NAPS2 reacted in two different ways, in the first it opens the progress screen, but the progress bar does not move, after some time the bar closes, without error, but there was no scanning.
In the second case, the progress bar reaches 100% but it takes a long time to obtain the scanned document.
I attached the log of both computers (server and client) to see if it helps.
In both cases, the scanner starts working again trying a new scan, it just seems like some communication error between server and client.
I would like to take this opportunity again to congratulate your work, NAPS2 is an excellent tool, for me there is no more practical and simple software for operating a scanner. Thank you for your commitment to this project.
I've made a small improvement in 7.3.1 that might help. I've also improved the client logging, so if you can reproduce the client logs in 7.3.1 that would be helpful.
As far as the first scenario, I've seen that myself when the original driver (e.g. TWAIN) would do the same thing, i.e. it's not an issue with the network connection. Might that be the case for you?
For the second scenario, that definitely sounds like a problem, again client logs with 7.3.1 would be helpful.
Hello
Returning with the results
In the first case, I believe it is not a problem with the driver, it is a Kodak i2600 scanner, directly via USB it is a very stable scanner, it does not usually cause this type of problem.
For the second case, this time I got an unsupported file error.
Two attempts were made, which are recorded in the attached log.
Can you try with NAPS2 7.4.1? I've made several changes that I believe should help.
Hello
Ben, I'm starting to suspect that it might be something related to the company's network, even though it works perfectly (when it works).
Anyway, I reran the tests in version 7.4.1 and the problems remain, I recovered the logs from both computers again. I hope I can collaborate.
In time, I believe it was necessary to add content about EsclServerCertificatePath and EsclSecurityPolicy to the documentation page for use in Organizations.
There's definitely an element of network issue to this, but also some problems with NAPS2 as well. I've fixed a couple issues in 7.4.2 that may help. And I also have some plans for the next version that may make it close to fully reliable. I've also updated the doc for those options.
Thanks for all the testing you've done, it's been incredibly helpful.
hi in my case, the scan will complete but no image will appear.
2024-07-05 06:51:54.3164 664 ESCL setting profile supports formats: application/pdf,image/jpeg,image/png
2024-07-05 06:51:54.3164 664 Creating ESCL job: format image/jpeg, source Platen, mode RGB24
2024-07-05 06:51:54.3164 664 ESCL POST https://[fe80::7961:edee:dd8a:708a%11]:9901/eSCL/ScanJobs
2024-07-05 06:51:54.3304 664 POST OK
2024-07-05 06:51:54.3854 664 ESCL GET https://[fe80::7961:edee:dd8a:708a%11]:9901/eSCL/ScanJobs/59d71a7d-a04d-48d0-bb7a-78b7813be087/NextDocument
2024-07-05 06:52:04.3910 664 ESCL NextDocument error System.Threading.Tasks.TaskCanceledException: The operation was canceled. ---> System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'SslStream'.
at void System.Net.Security.SslState.CheckThrow(bool authSuccessCheck, bool shutdownCheck)
at _SslStream System.Net.Security.SslState.get_SecureStream()
at int System.Net.Security.SslStream.EndRead(IAsyncResult asyncResult)
at Task<int> System.IO.Stream.BeginEndReadAsync(byte[] buffer, int offset, int count)+(Stream stream, IAsyncResult asyncResult) => { }
at void System.Threading.Tasks.TaskFactory<tresult>+FromAsyncTrimPromise<tinstance>.Complete(TInstance thisRef, Func<tinstance, iasyncresult,="" tresult=""> endMethod, IAsyncResult asyncResult, bool requiresSynchronization)
at async Task System.Net.Http.HttpConnection.FillAsync()
at async Task<arraysegment\\<byte>> System.Net.Http.HttpConnection.ReadNextResponseHeaderLineAsync(bool foldedHeadersAllowed)
at async Task<httpresponsemessage> System.Net.Http.HttpConnection.SendAsyncCore(HttpRequestMessage request, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
at async Task<httpresponsemessage> System.Net.Http.HttpConnection.SendAsyncCore(HttpRequestMessage request, CancellationToken cancellationToken)
at async Task<httpresponsemessage> System.Net.Http.HttpConnectionPool.SendWithNtConnectionAuthAsync(HttpConnection connection, HttpRequestMessage request, bool doRequestAuth, CancellationToken cancellationToken)
at async Task<httpresponsemessage> System.Net.Http.HttpConnectionPool.SendWithRetryAsync(HttpRequestMessage request, bool doRequestAuth, CancellationToken cancellationToken)
at async Task<httpresponsemessage> System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
at async Task<httpresponsemessage> System.Net.Http.HttpClient.FinishSendAsyncUnbuffered(Task<httpresponsemessage> sendTask, HttpRequestMessage request, CancellationTokenSource cts, bool disposeCts)
at async Task<t> NAPS2.Escl.Client.EsclClient.WithHttpFallback<t>(Func<string> urlFunc, Func<string, task\\<t="">> func)
at async Task<rawdocument> NAPS2.Escl.Client.EsclClient.NextDocument(EsclJob job, Action<double> pageProgress)
at async Task<rawdocument> NAPS2.Scan.Internal.Escl.EsclScanDriver.GetNextDocumentWithRetries(EsclClient client, EsclJob job, Action<double> progress)
2024-07-05 06:52:04.3910 664 ESCL GET https://[fe80::7961:edee:dd8a:708a%11]:9901/eSCL/ScannerStatus
2024-07-05 06:52:04.6000 664 GET OK
2024-07-05 06:52:04.6000 664 ESCL NextDocument failed, retrying as job state is Processing
2024-07-05 06:52:05.6070 664 ESCL GET https://[fe80::7961:edee:dd8a:708a%11]:9901/eSCL/ScanJobs/59d71a7d-a04d-48d0-bb7a-78b7813be087/NextDocument
2024-07-05 06:52:05.6070 664 GET failed: NotFound </double></rawdocument></double></rawdocument></string,></string></t></t></httpresponsemessage></httpresponsemessage></httpresponsemessage></httpresponsemessage></httpresponsemessage></httpresponsemessage></httpresponsemessage></arraysegment\\<byte></tinstance,></tinstance></tresult></int>
I've made all my intended changes in 7.4.3; that's currently my best effort at improving these reliability issues.
Thank you, Ben!
Last edit: ken ching 2024-07-08
Thank you for your effort; the communication with the scanner has significantly improved. We conducted several tests, and NAPS2 no longer crashes when finishing the scan. However, there is still a minor issue when opening the communication: in the NAPS2 client, the scanning progress bar opens and then closes without actually starting the scan. Nevertheless, this isn't a major inconvenience since simply starting it again allows the scan to proceed normally. If you find it appropriate, I have attached the logs for review.
Yeah, that one I'm not really sure what the issue is, but glad to hear the stability has improved.