We have a VLF_WIN application using RAMP and aXes that is running over at a customer and they are having issues that appear to be communications related. They are reporting issues like having to click the log in button multiple times before the application will actually log in. Sometimes upwards of 10 to 20 or more times. The message they receive is usually "Communications error code 20 received" and "attempt to connect to the server failed". They seem to also be having issues where they click on a button or function key in an aXes screen and the whole application locks up or they get a http 0 message. I was wondering if anyone knew where I can find logs to look at or some other method that might help in diagnosing the problem. The customer did state that these issues are mainly happening at newer compared to older ones that have been using the application longer.
Any help would be appreciated.
Thanks
VLF-WIN Application Communication Errors
Re: VLF-WIN Application Communication Errors
These intermittent connection issues are a nightmare to troubleshoot.
I would focus on any patterns that you can establish.
for example, this line: these issues are mainly happening at newer compared to older ones
You should try to get definite statements...is it definitely only new users? All new users or just some new users? Always the same ones (that are OK and not OK)?
Some other ideas?
- always the same time of the day?
- could something big be running the the AS/400 at these times?
click the log in button multiple times before the application will actually log in. Sometimes upwards of 10 to 20 or more times
That looks like a network issue to me.
Are the new users remote or a different location to the old users, etc.
Can an old user log in OK first time at the same time that the new user is having to click up to 20 times? That would tell you a lot.
You will have to start pinning it down to definite behaviour, not 2nd hand anecdotes.
Sorry, lots of questions but no answers...
HTH
Bark
I would focus on any patterns that you can establish.
for example, this line: these issues are mainly happening at newer compared to older ones
You should try to get definite statements...is it definitely only new users? All new users or just some new users? Always the same ones (that are OK and not OK)?
Some other ideas?
- always the same time of the day?
- could something big be running the the AS/400 at these times?
click the log in button multiple times before the application will actually log in. Sometimes upwards of 10 to 20 or more times
That looks like a network issue to me.
Are the new users remote or a different location to the old users, etc.
Can an old user log in OK first time at the same time that the new user is having to click up to 20 times? That would tell you a lot.
You will have to start pinning it down to definite behaviour, not 2nd hand anecdotes.
Sorry, lots of questions but no answers...
HTH
Bark
Re: VLF-WIN Application Communication Errors
another thing I just though of...
If this is VLF-Win, then its using superserver. perhaps at the same time that one of the users is having issues logging in, you could use the lcoecho on the command line to make a connection and if thats OK, then you could focus on the user and their connection to the box. If lcoecho isn't OK either, then you would consider the network.
I think that http 0 error in aXes would be a dropped VPN connection or unavailable network etc.
If this is VLF-Win, then its using superserver. perhaps at the same time that one of the users is having issues logging in, you could use the lcoecho on the command line to make a connection and if thats OK, then you could focus on the user and their connection to the box. If lcoecho isn't OK either, then you would consider the network.
I think that http 0 error in aXes would be a dropped VPN connection or unavailable network etc.
-
Tim McEntee
- Posts: 57
- Joined: Thu May 26, 2016 8:46 am
Re: VLF-WIN Application Communication Errors
The two most common error numbers when trying to connect are 20 & 6.
20 means that you cannot connect to the server. 6 means there is an issue with the user - disabled, incorrect password etc.
Is this an issue for all users, or just some. Where are the some situated. At home, in the office. Are they connecting via a VPN. Is the VPN still up when they can't connect.
If the users are internal, at the office, and this happens then it is the network. If internal users do not have a problem and external users are then it may be the VPN, some of them are very fragile when overloaded.
When something like this happens you need to ask lots and lots of questions to eliminate what is working, and so you can narrow it down to what is not.
20 means that you cannot connect to the server. 6 means there is an issue with the user - disabled, incorrect password etc.
Is this an issue for all users, or just some. Where are the some situated. At home, in the office. Are they connecting via a VPN. Is the VPN still up when they can't connect.
If the users are internal, at the office, and this happens then it is the network. If internal users do not have a problem and external users are then it may be the VPN, some of them are very fragile when overloaded.
When something like this happens you need to ask lots and lots of questions to eliminate what is working, and so you can narrow it down to what is not.