OKing Invoice takes ~ 10 sec.
Katrīne Žunna-Veličko
9-26-17
Hi,

One of our customer it takes ~ 10 sec to OK Invoice (SL and PL).
It appears only if computer is connected to wire network. If computer is connected to WiFi - everything works ok.


It started when customer changed version form 8.1 to 8.2 (2016-11-14-1752).
We have also tested on 8.3 (2017-03-27-0500) version - same problem.


What could be the reason?
What need to be checked from their IT side or our?



Thank You!


Giuseppe L.
10-2-17
Hi,
it's very hard to give you reasons why your customer is experiencing this quite uncommon issue. From the description given it appears the issue regards much more the Ethernet setting parameters than Standard ERP...
So I have more question to ask in the aim of having a wider idea of what is happening there:
Does problem appear only when OKing invoices or the ethernet slowness affects other actions also?
Is the server on-premise or in cloud? and how the server is connected to the network?

I would check if there is a VPN or a Proxy running, first. I could say any sort of "unusual" setting that could compromise the data routing on the network, then eventually port forwarding and the server firewall settings. What OS does the server runs?
Any HALcust running?

as many details you will give us as many possibilities we will have to figure out why and how to fix.

Best Regards
Giuseppe
HansaWorld Support
Jarek Jamroszczak
10-2-17
Hello

have you performed Latency tests ?
have you analyzed profiling tests ?

Regards

Jarek
Gatis Luckāns
10-3-17
Hi there,

So they have noticed this issue when opening paste special windows and okaying invoces.

There server is in the cloud, running CentOS 7.3.

And yes they do have halcust, but when running tests without halcust they had the same results.



Here are the results of latency tests they preformed:

RIXRO001#
Type escape sequence to abort.
Sending 1000, 1500-byte ICMP Echos to 94.237.25.94, timeout is 2 seconds:
Packet sent with a source address of 87.246.164.154
...
Success rate is 100 percent (1000/1000), round-trip min/avg/max = 36/40/96 ms
!
TLLRO001#
Type escape sequence to abort.
Sending 1000, 1500-byte ICMP Echos to 94.237.25.94, timeout is 2 seconds:
Packet sent with a source address of 213.219.82.250
...
Success rate is 100 percent (1000/1000), round-trip min/avg/max = 32/35/56 ms
!
VNORO001#ping 94.237.25.94 so 213.197.134.110 re 1000 si 1500
Type escape sequence to abort.
Sending 1000, 1500-byte ICMP Echos to 94.237.25.94, timeout is 2 seconds:
Packet sent with a source address of 213.197.134.110
...
Success rate is 100 percent (1000/1000), round-trip min/avg/max = 32/36/96 ms


Best Regards,
Gatis
Jarek Jamroszczak
10-4-17
Hello

have you used our tools ? (Latency report)
and you tried our profiling tests ?

Regards

Jarek
Katrīne Žunna-Veličko
6-25-19
Created byJarek Jamroszczak13:50 4 Oct 2017
Hello have you used our tools ? (Latency report) and you tried our profiling tests ? Regards Jarek
Hi,

We used everything.
Moved customer to newest 8.5. So far so good.


For now. Closing this question. Hope this will not repeat with newer versions.
Leave Comment
You can subscribe to notifications for this post by selecting the 'star' icon on the top right corner of the post.
Back to the list
Latest Posts
Hi, No changes should have been made that would increase client's HDB file. Please try to delete HANSA.HDB from client folder and reconnect to server and check if it will grow to 30MB again. ...
10:14 30 Apr 2024
Hi Dave, Thank you for the message! Can you please report this as a bug and inform if you get anything in the hansa.log during the flickering. Thank you! Best regards, Rasmus...
09:35 30 Apr 2024